A little help please with a DNS issue.

New Member Joined: May 26, 2005 Posts: 6

My host had a major melt down 24 or so hours ago.
I haven't had access to my site, no mail, no FTP, no cpanel, nothing for over 12 hours from my location in Dallas, Texas via Verizon.
They say it's up and I have one or two people say that it's up.
I need to enlist anyone and everyone to look at http://dfwforums.net and report back.
Is it up and where are you located?

Thanks in advance. No this is not a shameful plug for my site. I really need some assistance here as I'm at my wits end and my host is telling me to keep waiting for DNS propagation.
Site is 1 year and 7 months old.

Sells PC To Pay For Divorce Joined: Posts: 5661

yeah i know how that feels...dns update can take long or not...depends on the provider.
but i can see your site in the netherlands...

Posted: Sat Jul 09, 2005 2:36 pm

See that just doesn't make any sense.
I'm the only one on this server not seeing his website.
Your in the Netherlands and you can see it. Screwy I tell ya'.
Thanks for the look see.

Posted: Sat Jul 09, 2005 2:40 pm

well to be sure you can realy cleanup your computer to be sure..
even here we dont have a slow dns anymore..

Posted: Sat Jul 09, 2005 2:49 pm

Well, it took a while to load on my T-1 and on my 3MB broadband (comcast business), but it did come up. I must admit, I've never seen a 23 second page generation time before. Wow.

If you still can't acccess it, I would suggest that you drop your Client IP address and renew it. That might be why you can't see it yet.

If you aren't using a router, (as this won't work in a router scenario, where the router is the device actually holding the client IP address)

In windows click START, RUN
Type CMD and hit enter

First let's test what your Client is seeing for DNS information, type:
tracert dfwforums.net

(the last two octets should be 32.111)

If not, you are seeing your old IP address. In that case, expire your IP and renew it by doing the following:

Type:
IPCONFIG /release

Then Type:
IPCONFIG /renew

Then try the tracert again and see what you get.

If you have a router, Unplug it and your Verizon modem, Wait 30 seconds and plug them back in. After they come up and the lights stop flashing (you get a solid connect light) reboot your PC and try it again.

Hope this helps.

Posted: Sat Jul 09, 2005 3:16 pm

You are great to reply.
I've done everything I know to do, including your suggestions and flushing my dns cache on top of that.
I've rebooted everything. I've used different browsers. I've turned off all security. I've repeatedly pinged 147.202.32.111, which is the server addy.
Traceroute to aruba.cclservers.com (147.202.32.111)
1 L100.DSL-08.DLLSTX.verizon-gni.net (71.96.0.1) 22 ms 22 ms 22 ms
2 P2-3.LCR-01.DLLSTX.verizon-gni.net (130.81.34.72) 22 ms 22 ms 22 ms
3 so-6-0-0-0.PEER-RTR1.DFW80.verizon-gni.net (130.81.17.173) 24 ms 24 ms 24 ms
4 so-5-1-0-0.gar2.Dallas1.Level3.net (4.78.234.1) 24 ms 24 ms 26 ms
5 ae-1-53.bbr1.Dallas1.Level3.net (4.68.122.65) 24 ms 26 ms 24 ms
6 ae-0-0.bbr2.Chicago1.Level3.net (64.159.1.34) 120 ms 68 ms 66 ms
7 ge-9-0.ipcolo1.Chicago1.Level3.net (4.68.101.10) 66 ms 140 ms 82 ms
8 unknown.Level3.net (209.247.34.166) 56 ms 56 ms 54 ms
9 border3.ge2-0-bbnet1.chg.pnap.net (64.94.32.7) 54 ms 56 ms 54 ms
10 teamtech-2.border3.chg.pnap.net (64.94.34.146) 58 ms 56 ms 58 ms
11 bb1.coreswb.cf.teamnet.net (147.202.0.141) 58 ms 56 ms 58 ms
12 ge6-0.gsr12008.cf.fastservers.net (147.202.6.53) 74 ms 58 ms 60 ms
13 * (*) * ms * ms * ms
14 * (*) * ms * ms * ms
That last successful hop is in Iowa and that's as far as I can get.
http://www.whois.sc/147.202.6.53

Posted: Sat Jul 09, 2005 3:40 pm

You are actually making it onto your hosts backbone. You just aren't getting to the server so your route is taking you through a server at your host that hasn't propagated yet OR you have some other issue.

14 60 ms 60 ms 58 ms teamtech-2.border3.chg.pnap.net [64.94.34.146]
15 62 ms 62 ms 70 ms bb2.coreswa.cf.teamnet.net [147.202.1.140]
16 46 ms 46 ms 45 ms ge1-0.gsr12008.cf.fastservers.net [147.202.6.49]
17 62 ms 68 ms 61 ms dfwforums.net [147.202.32.111]

Trace complete.

You might want to send them an email and ask them to set TTL to 1 minute in your DNS records on your new server AS WELL AS TTL to 1 minute on the name servers and leave it that way for 15 minutes. This will force a DNS refresh on their backbone servers with a broadcast throughout the backbone.

Additionally, you should send them these tracert reports. Maybe something is awry with that ge6-0. server.

Posted: Sat Jul 09, 2005 3:49 pm

Done that too.
I am here because it was their suggestion to have others check out the site for me.
All I'm getting is, "You'll just have to wait."

Posted: Sat Jul 09, 2005 4:56 pm

Well, I'm finally able to see and access my site in every way.
I want to thank the both of you for helping me. Especially helping me by having a place to see new ideas and to vent a little.
I lurk here often.
Thanks again and have a good weekend.

Stephen in Texas

Posted: Sat Jul 09, 2005 9:50 pm

Your not going to believe this but I must vent it.
I asked my host if my IP or DNS had been blocked some how. They said "No".
One hour later I was told that YES my IP had been blocked because it was pinging the server and it was wrongfully blocked because they thought a DoS attack was coming from that address.
If only you could hear me scream. Thank God for Xanax.

Worker Joined: Feb 06, 2004 Posts: 147

I need help.... I am experimenting the same problems. I renewed the domain name yesterday and today in the Afternoon I was able to access the site from a friend's location. At home, I was brieffly successful, but now I can't connect.
Can anyone tell me if they can connect to http://www.ouaganet.com/ ? I have cleared my cache and history but no success ... I also confirmed that the domain was renewed.

Thanks

Posted: Sun Jul 10, 2005 4:44 am

well i can view it in the netherlands also..

Posted: Sun Jul 10, 2005 8:46 am

I disconnected my cable modem for about 20 minutes and reconnected it. After that, I was able to access my site. This forces a renewal of the IP address.