• The TMF is sponsored by Clips4sale - By supporting them, you're supporting us.
  • >>> If you cannot get into your account email me at [email protected] <<<
    Don't forget to include your username

The TMF is sponsored by:

Clips4Sale Banner

'ticklingforum.com' vs 'tmfbackup.com'

bobo304

Registered User
Joined
Jun 16, 2004
Messages
38
Points
0
I'm probably missing something here, but I'm only able to access TMF through 'tmfbackup.com.' Whenever I try to use 'ticklingforum.com' I get a "site can't be reached" message. I've flushed my DNS cache & cleared my browser's cache, no luck. Any ideas?

Thanks,
-BB
 
See what a traceroute tells us. I assume you use Windows, but the Mac version is not that different (just get a terminal window up and use traceroute instead of tracert), and if you have Linux I think it is identical to Max.

Go to Start, find Run, and type CMD (or search Command Prompt)
In the new prompt window, type "tracert ticklingforum.com" and take a screenshot/copy the text. Do the same for tmfbackup.com (they should be identical)

We can review what it shows once you do
 
See what a traceroute tells us. I assume you use Windows, but the Mac version is not that different (just get a terminal window up and use traceroute instead of tracert), and if you have Linux I think it is identical to Max.

Go to Start, find Run, and type CMD (or search Command Prompt)
In the new prompt window, type "tracert ticklingforum.com" and take a screenshot/copy the text. Do the same for tmfbackup.com (they should be identical)

We can review what it shows once you do

Not even close to identical. Also did an nslookup for both domains & those did match. Don't know why the tracert would go to a different address. Here're the results:

Code:
Microsoft Windows [Version 10.0.18363.1082]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\windows\system32>tracert tmfbackup.com

Tracing route to tmfbackup.com [184.154.25.18]
over a maximum of 30 hops:

  1     1 ms    <1 ms     3 ms  192.168.1.2
  2     2 ms     1 ms     1 ms  192.168.10.1
  3     *        *        *     Request timed out.
  4    48 ms    50 ms    48 ms  173-219-218-90.shin-bbrc01.suddenlink.net [173.219.218.90]
  5    20 ms    20 ms    13 ms  173-219-218-162.suddenlink.net [173.219.218.162]
  6    16 ms    24 ms    23 ms  173-219-232-212.suddenlink.net [173.219.232.212]
  7    33 ms    32 ms    29 ms  173-219-218-154.suddenlink.net [173.219.218.154]
  8   106 ms    91 ms    67 ms  ash-b1-link.telia.net [213.248.72.162]
  9    78 ms   167 ms    48 ms  ash-bb2-link.telia.net [62.115.123.124]
 10     *        *        *     Request timed out.
 11    51 ms    50 ms     *     chi-b23-link.telia.net [62.115.137.59]
 12    58 ms    52 ms    58 ms  chi-b2-link.telia.net [62.115.122.195]
 13    84 ms    92 ms    84 ms  serverhub-ic-324864-chi-b2.c.telia.net [62.115.154.247]
 14   124 ms    97 ms   145 ms  agg1.c13.r04.s101.chi03.singlehop.net [67.212.190.210]
 15    57 ms    71 ms    58 ms  aswg1.c12.r10.s101.chi03.singlehop.net [96.127.188.79]
 16    53 ms    53 ms    52 ms  server2.ticklingforum.com [184.154.25.18]

Trace complete.

C:\windows\system32>tracert ticklingforum.com

Tracing route to ticklingforum.com [184.154.208.218]
over a maximum of 30 hops:

  1     6 ms     2 ms     2 ms  192.168.1.2
  2     1 ms     1 ms     1 ms  192.168.10.1
  3     *        *        *     Request timed out.
  4    21 ms    16 ms    13 ms  173-219-218-90.shin-bbrc01.suddenlink.net [173.219.218.90]
  5    15 ms    14 ms    15 ms  173-219-218-162.suddenlink.net [173.219.218.162]
  6    35 ms    39 ms    49 ms  173-219-232-212.suddenlink.net [173.219.232.212]
  7    34 ms    29 ms    32 ms  173-219-218-154.suddenlink.net [173.219.218.154]
  8    38 ms    30 ms    31 ms  ash-b1-link.telia.net [213.248.72.162]
  9    30 ms    29 ms    30 ms  ash-bb2-link.telia.net [62.115.123.124]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12    50 ms    49 ms    48 ms  chi-b2-link.telia.net [62.115.122.195]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\windows\system32>nslookup tmfbackup.com
Server:  rdns01.suddenlink.net
Address:  208.180.42.68

Non-authoritative answer:
Name:    tmfbackup.com
Address:  184.154.25.18


C:\windows\system32>nslookup ticklingforum.com
Server:  rdns01.suddenlink.net
Address:  208.180.42.68

Non-authoritative answer:
Name:    ticklingforum.com
Address:  184.154.25.18


C:\windows\system32>

Thoughts?
 
That is strange indeed. The IP address that your DNS lookup provides is the correct one. It is not your system, given that the request bounces to a Telia router before dying.

I could not tell you why it is dying there unless Telia has a very stale DNS record from before we switched servers, but then you should be showing the old IP when you do an NS lookup. You could try temporarily using Google's DNS (https://developers.google.com/speed/public-dns) and see if that changes it, although I don't understand why it would. I think the blame falls on someone between you and the TMF, unfortunately.
 
That is strange indeed. The IP address that your DNS lookup provides is the correct one. It is not your system, given that the request bounces to a Telia router before dying.

I could not tell you why it is dying there unless Telia has a very stale DNS record from before we switched servers, but then you should be showing the old IP when you do an NS lookup. You could try temporarily using Google's DNS (https://developers.google.com/speed/public-dns) and see if that changes it, although I don't understand why it would. I think the blame falls on someone between you and the TMF, unfortunately.

I tried Google DNS, no change. (Figured it was a longshot, but stranger things have happened.) Thanks for the effort and input. I'll keep trying things from time to time & let you know if anything worked.
 
One other potential thing to try is to manually specify the TMF's IP in your computer's hosts file (on Windows; I do not recall the Mac and Linux equivalent) so that DNS is totally bypassed. I think you would still have the issue of the path to get to that IP being disrupted, but since the tmfbackup and ticklingforum domains point to the same IP, theoretically if you tell your computer to ignore DNS and just go to that IP it should work.
 
One other potential thing to try is to manually specify the TMF's IP in your computer's hosts file (on Windows; I do not recall the Mac and Linux equivalent) so that DNS is totally bypassed. I think you would still have the issue of the path to get to that IP being disrupted, but since the tmfbackup and ticklingforum domains point to the same IP, theoretically if you tell your computer to ignore DNS and just go to that IP it should work.

I figured out what my problem was, and it was PEBCAK. Some time ago, I'd put ticklingforum.com into my hosts file. When the server IP addy changed, I'd forgot I'd done that. You can see where problems might arise. :/

Anyway, I took it out and everything is working now. Thanks for the help, and sorry for wasting your time.
 
I figured out what my problem was, and it was PEBCAK. Some time ago, I'd put ticklingforum.com into my hosts file. When the server IP addy changed, I'd forgot I'd done that. You can see where problems might arise. :/

Anyway, I took it out and everything is working now. Thanks for the help, and sorry for wasting your time.

Not a waste, glad it was solved. And I am glad it was solved in a way that makes sense, as I had no idea how this particular conundrum was possible technologically.
 
What's New

3/29/2024
The TMF Gathering forums keep you up to date on where and when folk are meeting up.
Tickle Experiment
Door 44
NEST 2024
Register here
The world's largest online clip store
Live Camgirls!
Live Camgirls
Streaming Videos
Pic of the Week
Pic of the Week
Congratulations to
*** brad1701 ***
The winner of our weekly Trivia, held every Sunday night at 11PM EST in our Chat Room
Back
Top