- « Previous
- Next »
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Up again Monday morning 21 Nov:
Tracing route to landzdown.com [74.55.178.36]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.1.1
2 41 ms 33 ms 33 ms 10.32.187.1
3 42 ms 35 ms 34 ms 130.81.136.220
4 42 ms 36 ms 36 ms so-5-3-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.28.154]
5 42 ms 36 ms 37 ms 0.xe-3-0-0.BR3.NYC4.ALTER.NET [152.63.2.241]
6 42 ms 36 ms 35 ms 204.255.169.234
7 43 ms 36 ms 36 ms ae-3.r05.nycmny01.us.bb.gin.ntt.net [129.250.4.204]
8 42 ms 36 ms 35 ms xe-1-0-0.bbr01.tl01.nyc01.networklayer.com [165.254.16.2]
9 55 ms 48 ms 48 ms ae7.bbr02.tl01.nyc01.networklayer.com [173.192.18.177]
10 68 ms 61 ms 61 ms ae1.bbr01.eq01.chi01.networklayer.com [173.192.18.132]
11 93 ms 87 ms 87 ms ae20.bbr01.eq01.dal03.networklayer.com [173.192.18.136]
12 97 ms 90 ms 89 ms ae5.bbr01.sr02.hou02.networklayer.com [173.192.18.219]
13 98 ms 92 ms 92 ms po31.dsr02.hstntx2.networklayer.com [173.192.18.235]
14 98 ms 90 ms 92 ms po16.dsr01.hstntx1.networklayer.com [70.87.253.106]
15 98 ms 91 ms 90 ms po1.car05.hstntx1.networklayer.com [207.218.223.18]
16 98 ms 90 ms 90 ms ns1.manageyourpc.com [74.55.178.36]
Trace complete.
EDIT: I see this is to the NEW IP address 74.55.178.36
the old one was 74.55.178.34
from which I'm assuming the server/hardware changes have been implemented.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Let's hope moving the site to a different IP address solved the problem.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like the new IP did the trick. The old one must've gotten stuck in some sort of black hole, lol!
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\>tracert landzdown.com
Tracing route to landzdown.com [74.55.178.36]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.3.1
2 80 ms 57 ms 93 ms 10.15.3.1
3 97 ms 80 ms 80 ms so-1-1-0-0.BUFF-CORE-RTR2.verizon-gni.net [130.81.13.77]
4 114 ms 91 ms 93 ms as4-0.NY5030-BB-RTR1.verizon-gni.net [130.81.20.106]
5 125 ms 93 ms 92 ms 0.ae5.BR3.NYC4.ALTER.NET [152.63.16.9]
6 102 ms 137 ms 137 ms 204.255.169.234
7 116 ms 91 ms 91 ms ae-3.r05.nycmny01.us.bb.gin.ntt.net [129.250.4.204]
8 170 ms 137 ms 137 ms xe-1-0-0.bbr01.tl01.nyc01.networklayer.com [165.254.16.2]
9 * 119 ms 93 ms ae7.bbr02.tl01.nyc01.networklayer.com [173.192.18.177]
10 154 ms 92 ms 93 ms ae1.bbr01.eq01.chi01.networklayer.com [173.192.18.132]
11 112 ms 128 ms 116 ms ae20.bbr01.eq01.dal03.networklayer.com [173.192.18.136]
12 145 ms 137 ms 137 ms ae5.bbr01.sr02.hou02.networklayer.com [173.192.18.219]
13 170 ms 183 ms 126 ms po31.dsr01.hstntx2.networklayer.com [173.192.18.233]
14 110 ms 138 ms 155 ms po16.dsr02.hstntx1.networklayer.com [70.87.253.102]
15 121 ms 142 ms 117 ms po2.car05.hstntx1.networklayer.com [207.218.245.18]
16 148 ms 126 ms 138 ms ns1.manageyourpc.com [74.55.178.36]
Trace complete.
C:\Users\>
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello everyone,
I'm Aaron, and I'm the server administrator for the box that hosts Landzdown.com. I thought I'd update the thread with what I'm hoping will be the final update on things.
But first, I want to thank Corrine for helping me with gathering user reports, logs and other info through this. My actual work is something other than web servers (I host this box for my own personal email and website, along with free hosting for friends' sites, my mom's sole proprietorship, and a non-profit group I volunteer at), and her help allowed me to keep proper focus at work, and look into the web server after coming home for the day.
Also, thank you to the Verizon network engineers that looked into things on their end. They researched things with due diligence and came back with useful information and guidance for me to back to the hosting company with. I very much appreciate their taking time to try and help solve this issue.
And, my apologies to everyone trying to reach the site for how long this took to resolve. I appreciate everyone's patience while this was being worked on, and for your working to help provide logs and other information. It's difficult to troubleshoot things when not directly on site where the problem's happening at, and your logs were instrumental in helping me understand what was happening. Thank you for all you did to help.
As you noticed, I switched the site's IP address to try and get things online while I looked for a more permanent solution. (For the curious, I only changed the assigned IP address the site lived on - it was the same server, same firewall, same routing table, and the same physical network port on the box, and nothing changed at the hosting company.) I did have a ticket open with the hosting company to try and resolve things, and I supplied them with your logs and other info, but I did not receive the level of support I needed. And, while the issue was impacting both here and another ISP initially, a new issue came up regarding reaching an antispam data source - the packets were not routing correctly. I needed to get off of this server.
On Friday night into Saturday morning, I moved everything over to a new server at another hosting company, which I believe will bring this to a final resolution. (Hopefully everything I did minimized any downtime for you while DNS updates propagated, and you're still able to reach the site right now without issue.) And, from setting it up, it already appears things will be better. I had to open a ticket for reverse DNS updates, which I opened around 4:30am Central Time Saturday morning (time zone for the hosting company - it was 2:30am for me), and in the minute and a half between opening the ticket and checking my email for the acknowledgement, they had already made the changes and resolved the ticket. This hosting company was recommended to me by a good friend of mine that has worked with several hosting companies, and it would seem his recommendation is spot on.
I strongly believe things will be set for the long term, and if a new issue does come up later (hopefully never, but if it must, i hope it's much, much later), that things are in a position to more quickly drive the issue to resolution. Again, I very much appreciate your patience and your help towards resolving this. You all did what the previous hosting company did not - you went the extra mile. Thank you.
Regards,
Aaron Hulett
(The views and opinions expressed in my post are my own, and do not reflect the views and opinions of Microsoft. Microsoft is a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries.)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Anyways, the site is still reachable on my end, but it should be since DNS here tends to update the moment a domain's records change.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You're welcome, Aaron. I was happy to help.
- « Previous
- Next »