dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2193
share rss forum feed


tschmidt
Premium,MVM
join:2000-11-12
Milford, NH
kudos:9
Reviews:
·G4 Communications
·Fairpoint Commun..
·Hollis Hosting

1 edit

Unable to access web site

My hosting service upgraded my physical web server and gave my site a different IP address. Since that occurred I am no longer able to access the site from FairPoint but it works fine from Comcast.

The old IP address was 67.220.209.137 the new one is 173.231.1.94. Upgrade occurred the beginning of the week so DNS should have long since flushed the old IP. From home FairPoint DNS is returning the new IP address but I cannot access the server.

Please try to Ping the web site tschmidt.com and let me know what IP address is returned and if site responds to Ping.

I've posted Traceroutes to both old and new addresses. Even though both are within Webnx there is no response from new server.

Tracing route to server30.verygoodserver.com [67.220.209.137]over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2    22 ms    22 ms    22 ms  10.20.6.1
  3    22 ms    22 ms    22 ms  64.222.166.165
  4    27 ms    27 ms    27 ms  pool-64-222-213-132.port.east.myfairpoint.net [64.222.213.132]
  5    27 ms    27 ms    26 ms  pool-64-222-213-129.port.east.myfairpoint.net [64.222.213.129]
  6   209 ms   203 ms   209 ms  te8-5.ccr02.alb02.atlas.cogentco.com [38.104.52.5]
  7    84 ms   207 ms   207 ms  te8-1.ccr01.alb02.atlas.cogentco.com [154.54.81.97]
  8   207 ms   202 ms   210 ms  te9-7.ccr01.jfk01.atlas.cogentco.com [154.54.43.6]
  9    38 ms    38 ms    38 ms  te0-2-0-0.mpd22.jfk02.atlas.cogentco.com [154.54.40.30]
 10    45 ms    44 ms    45 ms  te0-0-0-6.mpd22.dca01.atlas.cogentco.com [154.54.26.173]
 11    56 ms    55 ms    56 ms  te0-0-0-6.mpd22.atl01.atlas.cogentco.com [154.54.3.65]
 12    70 ms    70 ms    70 ms  te0-0-0-1.mpd22.iah01.atlas.cogentco.com [154.54.29.10]
 13   106 ms   106 ms   106 ms  te0-3-0-6.mpd22.lax01.atlas.cogentco.com [154.54.0.253]
 14   106 ms   106 ms   106 ms  154.54.88.5
 15   106 ms   106 ms   106 ms  38.122.146.26
 16   107 ms   107 ms   106 ms  100-42-223-158.static.webnx.com [100.42.223.158]
 17   106 ms   106 ms   106 ms  100-42-223-170.static.webnx.com [100.42.223.170]
 18   106 ms   106 ms   106 ms  server30.verygoodserver.com [67.220.209.137]
 
Trace complete.
*********************************************
Tracing route to server54.verygoodserver.com [173.231.1.94]over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2    22 ms    22 ms    22 ms  10.20.6.1
  3    24 ms    23 ms    23 ms  64.222.166.167
  4    28 ms    28 ms    29 ms  burl-lnk-70-109-168-138.ngn.east.myfairpoint.net [70.109.168.138]
  5   227 ms   202 ms   203 ms  te7-5.ccr01.alb02.atlas.cogentco.com [38.104.52.21]
  6   129 ms   207 ms   224 ms  te9-7.ccr01.jfk01.atlas.cogentco.com [154.54.43.6]
  7    37 ms    37 ms    37 ms  te0-2-0-0.mpd22.jfk02.atlas.cogentco.com [154.54.40.30]
  8    44 ms    44 ms    43 ms  te0-1-0-3.mpd22.dca01.atlas.cogentco.com [154.54.6.5]
  9    55 ms    54 ms    55 ms  te0-1-0-2.mpd22.atl01.atlas.cogentco.com [154.54.28.194]
 10    69 ms    68 ms    69 ms  te0-2-0-1.mpd22.iah01.atlas.cogentco.com [154.54.2.34]
 11   105 ms   105 ms   105 ms  te0-1-0-6.mpd22.lax01.atlas.cogentco.com [154.54.0.245]
 12   105 ms   105 ms   105 ms  te0-6-0-1.ccr21.lax04.atlas.cogentco.com [154.54.44.2]
 13   105 ms   105 ms   105 ms  38.122.146.26
 14   105 ms   105 ms   105 ms  100-42-223-158.static.webnx.com [100.42.223.158]
 15   105 ms   105 ms   105 ms  100-42-223-170.static.webnx.com [100.42.223.170]
 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:\Documents and Settings\Tschmidt>
 

/Tom

ajeff

join:2007-07-30
Orleans, VT

1 recommendation

Returned 173.231.1.94 RT 90ms

I have FP DSL


modem_reset

join:2010-05-27
Reviews:
·ObiVoice
reply to tschmidt

Non-authoritative answer:
Name: server54.verygoodserver.com
Address: 173.231.1.94

Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. DD-WRT 0.0% 13 12.6 3.7 1.3 12.6 2.8
2. dsl-216-227-0-132.pivot.net 0.0% 13 177.2 128.3 41.3 186.0 47.4
3. dsl-216-227-0-49.pivot.net 0.0% 13 146.6 130.4 44.4 191.7 52.6
4. dsl-216-227-0-5.pivot.net 7.7% 13 257.9 127.1 43.4 257.9 67.9
5. static-ptld-mse-71-161-104-57.ng 0.0% 13 211.8 139.2 55.8 211.8 56.4
6. pool-64-222-213-33.port.east.myf 7.7% 13 163.9 117.2 47.8 198.6 47.5
7. pool-64-222-213-142.port.east.my 0.0% 13 96.9 109.7 45.1 205.5 53.3
8. te8-5.ccr02.alb02.atlas.cogentco 33.3% 13 96.3 125.0 57.4 200.9 55.4
9. te4-4.ccr02.jfk01.atlas.cogentco 0.0% 13 135.3 169.6 62.2 381.3 98.0
10. te0-1-0-6.ccr21.jfk02.atlas.coge 0.0% 12 94.0 123.5 53.9 235.2 54.6
11. te0-0-0-6.mpd21.jfk02.atlas.coge 0.0% 12 62.7 126.6 57.6 229.4 57.1
12. te0-3-0-6.mpd21.dca01.atlas.coge 8.3% 12 88.0 131.3 69.7 240.6 52.0
te0-3-0-7.mpd21.dca01.atlas.cogentco.com
te0-0-0-2.mpd21.dca01.atlas.cogentco.com
te0-3-0-3.mpd21.dca01.atlas.cogentco.com
te0-1-0-3.mpd21.dca01.atlas.cogentco.com
te0-0-0-6.mpd21.dca01.atlas.cogentco.com
te0-2-0-2.mpd21.dca01.atlas.cogentco.com
13. te0-2-0-3.mpd21.atl01.atlas.coge 0.0% 12 200.8 170.9 80.9 255.3 60.7
14. te0-2-0-7.mpd21.iah01.atlas.coge 0.0% 12 174.9 180.9 92.8 258.9 63.6
15. te0-3-0-6.mpd21.lax01.atlas.coge 0.0% 12 311.9 219.3 128.6 311.9 65.7
16. te0-1-0-0.ccr21.lax04.atlas.coge 0.0% 12 261.4 209.4 126.2 299.1 60.3
17. 38.122.146.26 0.0% 12 211.0 203.8 120.5 294.8 54.8
18. 100-42-223-158.static.webnx.com 0.0% 12 183.3 204.8 142.0 279.6 47.1
19. 100-42-223-170.static.webnx.com 0.0% 12 333.5 232.4 139.7 333.5 59.1
20. server54.verygoodserver.com 0.0% 12 295.8 209.0 124.1 295.8 53.8

what is your fqdn?

I have a splash page when i do the IP..

If you feel you have reached this page in error, please contact the web site owner:

webmaster@173.231.1.94
It may be possible to restore access to this site by following these instructions for clearing your dns cach



tschmidt
Premium,MVM
join:2000-11-12
Milford, NH
kudos:9
Reviews:
·G4 Communications
·Fairpoint Commun..
·Hollis Hosting

Thanks.

said by modem_reset:

what is your fqdn?

tschmidt.com

You get the splash page when accessing site by IP because it is a virtual server hosting multiple web sites.

/tom


tschmidt
Premium,MVM
join:2000-11-12
Milford, NH
kudos:9
reply to tschmidt

Well everything seems to be working fine now.

Have no idea what the root cause was. Keeping my fingers crossed it does not happen again.

Thanks to all those who replied.

/tom


modem_reset

join:2010-05-27
reply to tschmidt

sorry to take so long in replying...but glad it is resolved...odd question i had a similar issue a while ago on sites hosted via aws...imgur, tumblr, etc...did you have any other sites not load?



tschmidt
Premium,MVM
join:2000-11-12
Milford, NH
kudos:9
Reviews:
·G4 Communications
·Fairpoint Commun..
·Hollis Hosting

said by modem_reset:

did you have any other sites not load?

Not as far as I can tell. But I mostly use a handful of preferred sites.

This appears to have been a FP a routing problem. I tried other addresses in the block and the difference between ones that worked and failed was the peering location. Curious, if you do an location look-up that IP shows as in the UK. Even though other addresses within the /18 show up on the West Coast as expected.

I assume, but am no routing expert, the IP was split off and was recently reassigned. Why it only affected FairPoint I have no idea. I was able to get to the site by using Comcast at the town library. I'm not convinced it really was a routing problem since it stayed broken so long. If it was routing I would have expected it to self correct within a few days at most.

I'm extremely happy it self resolved. Imagine trying to explain to FP residential tech support that even though they are able to get to my web site I cannot and I think it is their problem.

/tom