Networking question....

[GeoffS]

I've got a few sites that I've moved from my server to a hosted service (Dreamhost). For the most part, they are working fine. I just moved one a few days ago (www.kamikazelatinamerica.com). I originally had the DNS through DNSMadeEasy.com pointing to my server at home, but deleted the records from there and used the DNS from Dreamhost.

From work, I can hit the site... everything does and doesn't work as expected (most of the pages load, but I haven't hooked up the database yet, so the product pages don't load).

From home, I get host not found or host cannot be resolved errors. Now, I know that DNS replication can take a while, but it's been a couple of days now. I'm with Adelphia here in Vermont, and the guy that I built the website for is with Verizon (also in Vermont), and he couldn't hit the site yesterday either. I tried flushing my DNS Resolver cache, and that did nothing.

Any hints from the gurus?

Update 2/09 @ 1030 - The guy going through Verizon tells me he can hit the site today... maybe the propegation was just really really slow or something... seems odd though. I'll check my access from home again tonight.

More info - As of last night (2 days after the DNS change), I couldn't hit the site through a browser (host not found I think), I couldn't tracert it from a command line, nor could I FTP to the site.

Thanks!
Geoff

 

[dmcowen674]

Originally posted by: GeoffS
I've got a few sites that I've moved from my server to a hosted service (Dreamhost). For the most part, they are working fine. I just moved one a few days ago (www.kamikazelatinamerica.com). I originally had the DNS through DNSMadeEasy.com pointing to my server at home, but deleted the records from there and used the DNS from Dreamhost.

From work, I can hit the site... everything does and doesn't work as expected (most of the pages load, but I haven't hooked up the database yet, so the product pages don't load).

From home, I get host not found or host cannot be resolved errors. Now, I know that DNS replication can take a while, but it's been a couple of days now. I'm with Adelphia here in Vermont, and the guy that I built the website for is with Verizon (also in Vermont), and he couldn't hit the site yesterday either. I tried flushing my DNS Resolver cache, and that did nothing.

Any hints from the gurus?

Thanks!
Geoff

Check for a dead cookie from your old server on your PC and delete it.

Also check to see if there is a host file on your PC with the old server entry.

 

[GeoffS]

Okay... I'll check that tonight... my site doesn't use cookies, so I don't think that's it... and I can't remember if I mucked with my hosts file, but I'm pretty sure the guy I built this site for couldn't find his hosts file if his life depended on it and as of yesterday, he couldn't hit the site either. Odd... Thanks Dave and good to see you again!

 

[RaySun2Be]

Geoffs, you might try running ipconfig /flushdns then ipconfig /registerdns at the command line. Assuming Windows2k or XP.

This will purge the DNS cache on the PC and re-register DNS.

 

[GeoffS]

Okay... I did the flush... didn't to the register. I think I tried changing the DNS servers in the router configuration (by default, they are supplied to me by the ISP), but I don't think that worked either... but I'll try that again...

 

[Freewolf]

it came right up for me Geoff

 

[Wiz]

Geoffs, works good from here.
Possibly a cache problem on your local machines?
Have you tried a different web browser? - If you normally use FireFox then try IE or the other way round.

 

[GeoffS]

Thanks Jim....

Wiz - I'll give that a try tonight, however I couldn't FTP into it from a command line either... nor could I tracert it...

 

[shmapty]

since you're troubleshooting a network issue, don't use a high-level browser.

nslookup -type=ns kamikazelatinamerica.com.
nslookup -type=ns kamikazelatinamerica.com. a.gtld-servers.net.

this confirms that network-solutions (who manages com. and net.) is delegating
your domain to dreamhost.com. and that their ns glue exists as well (authoritative
answers section)

nslookup -type=ns kamikazelatinamerica.com. ns1.dreamhost.com.
nslookup -type=ns kamikazelatinamerica.com. ns2.dreamhost.com.
nslookup -type=ns kamikazelatinamerica.com. ns3.dreamhost.com.

confirms that ns2 and ns3 return an A record pointing to 64.111.117.137. ns1
though is unreachable.

that's most likely your problem. contact your registrar, have them remove the
delegation to ns1.dreamhost.com. for your domain.

then contact dreamhost and have them remove the ns record for your domain
that point to ns1.dreamhost.com.

 

[shmapty]

oops.

the second set of nslookups want to be:

nslookup -type=a kamikazelatinamerica.com. ns1.dreamhost.com.
nslookup -type=a kamikazelatinamerica.com. ns2.dreamhost.com.
nslookup -type=a kamikazelatinamerica.com. ns3.dreamhost.com.

damn you cut & paste!

 

[mondobyte]

I've found the utilities at http://www.DNSSTUFF.COM to be very useful at troubleshooting DNS, Mail, and similar problems.

Also (you can get there from http://www.DNSSTUFF.COM)

http://www.dnsreport.com/tools/dnsreport.ch?domain=kamikazelatinamerica.com

A problem that I frequently encounter is that ISP's sometimes cache DNS information and completely ignore TTL. This can lead to "stale" DNS records.

Thanks

mondo

 

[TAandy]

I got through to www.kamikazelatinamerica.com

 

[GeoffS]

Originally posted by: shmapty
since you're troubleshooting a network issue, don't use a high-level browser.

nslookup -type=ns kamikazelatinamerica.com.
nslookup -type=ns kamikazelatinamerica.com. a.gtld-servers.net.

this confirms that network-solutions (who manages com. and net.) is delegating
your domain to dreamhost.com. and that their ns glue exists as well (authoritative
answers section)

nslookup -type=ns kamikazelatinamerica.com. ns1.dreamhost.com.
nslookup -type=ns kamikazelatinamerica.com. ns2.dreamhost.com.
nslookup -type=ns kamikazelatinamerica.com. ns3.dreamhost.com.

confirms that ns2 and ns3 return an A record pointing to 64.111.117.137. ns1
though is unreachable.

that's most likely your problem. contact your registrar, have them remove the
delegation to ns1.dreamhost.com. for your domain.

then contact dreamhost and have them remove the ns record for your domain
that point to ns1.dreamhost.com.

Awesome! I can manage that through godaddy.... can I just move ns1 further down the list? I assume at some point in time it will come back up...

Interesting, though.... the NS records for kamikazelatinamerica.com are

NS ns1.dreamhost.com.
NS ns2.dreamhost.com.
NS ns3.dreamhost.com.

and at the registrar I have

NS1.DREAMHOST.COM
NS2.DREAMHOST.COM
NS3.DREAMHOST.COM

The NS records for jkavt.com are

NS ns1.dreamhost.com.
NS ns2.dreamhost.com.
NS ns3.dreamhost.com.

and at the registrar I have

NS1.DREAMHOST.COM
NS2.DREAMHOST.COM
NS3.DREAMHOST.COM

Last night I was able to hit the jkavt.com site (browser and ftp) with no problems, but not the kamikaze site... go figure...

Thanks!
Geoff

 

[GeoffS]

Originally posted by: mondobyte
I've found the utilities at http://www.DNSSTUFF.COM to be very useful at troubleshooting DNS, Mail, and similar problems.

Also (you can get there from http://www.DNSSTUFF.COM)

http://www.dnsreport.com/tools/dnsreport.ch?domain=kamikazelatinamerica.com

A problem that I frequently encounter is that ISP's sometimes cache DNS information and completely ignore TTL. This can lead to "stale" DNS records.

Thanks

mondo

Great tools! Thanks mondo!

Geoff

 

[networkman]

Yeah, thanks mondobyte. That DNSStuff site is pretty nifty!

 

[Spacehead]

If it's any help, i can get the jkavt.com site in both FF & IE but can't get to www.kamikazelatinamerica.com in either browser. I just get the following:

Site Temporarily Unavailable
We apologize for the inconvenience. Please contact the webmaster/ tech support immediately to have them rectify this.

error id: "bad_httpd_conf"

I can however ping & tracert www.kamikazelatinamerica.com

 

[GeoffS]

Alright... I feel like I'm getting out of my league here...

My home network is running behind a Netgear ProSave VPN Firewall. It's IP is 192.168.0.1. It appears to be running just fine as I'm here posting! lol... Here is the result of ipconfig /all on my home PC.

Windows IP Configuration

Host Name . . . . . . . . . . . . : PC1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : sbtnvt.adelphia.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sbtnvt.adelphia.net
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connect
ion
Physical Address. . . . . . . . . : 00-0B-DB-59-65-E0
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Thursday, February 09, 2006 5:35:38 PM
Lease Expires . . . . . . . . . . : Sunday, February 12, 2006 5:35:38 PM


Here's what I get when I do the first nslookup for kamikazelatinamerica.com:

C:\>nslookup -type=ns kamikazelatinamerica.com.
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1

*** UnKnown can't find kamikazelatinamerica.com.: Server failed


Here's what I get when I try it for jkavt.com (same hosting service...)

C:\>nslookup -type=ns jkavt.com.
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1

Non-authoritative answer:
jkavt.com nameserver = ns1.dreamhost.com
jkavt.com nameserver = ns2.dreamhost.com
jkavt.com nameserver = ns3.dreamhost.com

ns1.dreamhost.com internet address = 66.33.206.206
ns2.dreamhost.com internet address = 66.201.54.66



The 2nd nslookup yields information that I thought the first one would...

C:\>nslookup -type=ns kamikazelatinamerica.com. a.gtld-servers.net.
(root) nameserver = l.root-servers.net
(root) nameserver = e.root-servers.net
(root) nameserver = k.root-servers.net
(root) nameserver = b.root-servers.net
(root) nameserver = g.root-servers.net
(root) nameserver = d.root-servers.net
(root) nameserver = c.root-servers.net
(root) nameserver = j.root-servers.net
(root) nameserver = h.root-servers.net
(root) nameserver = i.root-servers.net
(root) nameserver = m.root-servers.net
(root) nameserver = f.root-servers.net
(root) nameserver = a.root-servers.net
l.root-servers.net internet address = 198.32.64.12
e.root-servers.net internet address = 192.203.230.10
k.root-servers.net internet address = 193.0.14.129
b.root-servers.net internet address = 192.228.79.201
g.root-servers.net internet address = 192.112.36.4
d.root-servers.net internet address = 128.8.10.90
c.root-servers.net internet address = 192.33.4.12
j.root-servers.net internet address = 192.58.128.30
h.root-servers.net internet address = 128.63.2.53
i.root-servers.net internet address = 192.36.148.17
m.root-servers.net internet address = 202.12.27.33
f.root-servers.net internet address = 192.5.5.241
a.root-servers.net internet address = 198.41.0.4
*** Can't find server name for address 192.5.6.30: No information
Server: UnKnown
Address: 192.5.6.30

Non-authoritative answer:
kamikazelatinamerica.com nameserver = ns1.dreamhost.com
kamikazelatinamerica.com nameserver = ns2.dreamhost.com
kamikazelatinamerica.com nameserver = ns3.dreamhost.com

ns1.dreamhost.com internet address = 66.33.206.206
ns2.dreamhost.com internet address = 66.201.54.66
ns3.dreamhost.com internet address = 66.33.216.216


Here are the results of the nslookups on the A records:

C:\>nslookup -type=a kamikazelatinamerica.com. ns1.dreamhost.com.
Server: ns1.dreamhost.com
Address: 66.33.206.206

Name: kamikazelatinamerica.com
Address: 208.97.134.115


C:\>nslookup -type=a kamikazelatinamerica.com. ns2.dreamhost.com.
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 66.201.54.66: Timed out
Server: UnKnown
Address: 66.201.54.66

DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out


C:\>nslookup -type=a kamikazelatinamerica.com. ns3.dreamhost.com.
Server: ns3.dreamhost.com
Address: 66.33.216.216

Name: kamikazelatinamerica.com
Address: 64.111.117.137


Any further direction would be greatly appreciated!

 

[TAandy]

Originally posted by: GeoffS
Alright... I feel like I'm getting out of my league here...

My home network is running behind a Netgear ProSave VPN Firewall. It's IP is 192.168.0.1. It appears to be running just fine as I'm here posting! lol... Here is the result of ipconfig /all on my home PC.

Windows IP Configuration

Host Name . . . . . . . . . . . . : PC1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : sbtnvt.adelphia.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sbtnvt.adelphia.net
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connect
ion
Physical Address. . . . . . . . . : 00-0B-DB-59-65-E0
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Thursday, February 09, 2006 5:35:38 PM
Lease Expires . . . . . . . . . . : Sunday, February 12, 2006 5:35:38 PM


Here's what I get when I do the first nslookup for kamikazelatinamerica.com:

C:\>nslookup -type=ns kamikazelatinamerica.com.
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1

*** UnKnown can't find kamikazelatinamerica.com.: Server failed


Here's what I get when I try it for jkavt.com (same hosting service...)

C:\>nslookup -type=ns jkavt.com.
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1

Non-authoritative answer:
jkavt.com nameserver = ns1.dreamhost.com
jkavt.com nameserver = ns2.dreamhost.com
jkavt.com nameserver = ns3.dreamhost.com

ns1.dreamhost.com internet address = 66.33.206.206
ns2.dreamhost.com internet address = 66.201.54.66



The 2nd nslookup yields information that I thought the first one would...

C:\>nslookup -type=ns kamikazelatinamerica.com. a.gtld-servers.net.
(root) nameserver = l.root-servers.net
(root) nameserver = e.root-servers.net
(root) nameserver = k.root-servers.net
(root) nameserver = b.root-servers.net
(root) nameserver = g.root-servers.net
(root) nameserver = d.root-servers.net
(root) nameserver = c.root-servers.net
(root) nameserver = j.root-servers.net
(root) nameserver = h.root-servers.net
(root) nameserver = i.root-servers.net
(root) nameserver = m.root-servers.net
(root) nameserver = f.root-servers.net
(root) nameserver = a.root-servers.net
l.root-servers.net internet address = 198.32.64.12
e.root-servers.net internet address = 192.203.230.10
k.root-servers.net internet address = 193.0.14.129
b.root-servers.net internet address = 192.228.79.201
g.root-servers.net internet address = 192.112.36.4
d.root-servers.net internet address = 128.8.10.90
c.root-servers.net internet address = 192.33.4.12
j.root-servers.net internet address = 192.58.128.30
h.root-servers.net internet address = 128.63.2.53
i.root-servers.net internet address = 192.36.148.17
m.root-servers.net internet address = 202.12.27.33
f.root-servers.net internet address = 192.5.5.241
a.root-servers.net internet address = 198.41.0.4
*** Can't find server name for address 192.5.6.30: No information
Server: UnKnown
Address: 192.5.6.30

Non-authoritative answer:
kamikazelatinamerica.com nameserver = ns1.dreamhost.com
kamikazelatinamerica.com nameserver = ns2.dreamhost.com
kamikazelatinamerica.com nameserver = ns3.dreamhost.com

ns1.dreamhost.com internet address = 66.33.206.206
ns2.dreamhost.com internet address = 66.201.54.66
ns3.dreamhost.com internet address = 66.33.216.216


Here are the results of the nslookups on the A records:

C:\>nslookup -type=a kamikazelatinamerica.com. ns1.dreamhost.com.
Server: ns1.dreamhost.com
Address: 66.33.206.206

Name: kamikazelatinamerica.com
Address: 208.97.134.115


C:\>nslookup -type=a kamikazelatinamerica.com. ns2.dreamhost.com.
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 66.201.54.66: Timed out
Server: UnKnown
Address: 66.201.54.66

DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out


C:\>nslookup -type=a kamikazelatinamerica.com. ns3.dreamhost.com.
Server: ns3.dreamhost.com
Address: 66.33.216.216

Name: kamikazelatinamerica.com
Address: 64.111.117.137


Any further direction would be greatly appreciated!

Out your front door and round to the nearest pub/bar

Crying out loud Geoff, what was all that??

 

[GeoffS]

Originally posted by: Spacehead
If it's any help, i can get the jkavt.com site in both FF & IE but can't get to www.kamikazelatinamerica.com in either browser. I just get the following:

Site Temporarily Unavailable
We apologize for the inconvenience. Please contact the webmaster/ tech support immediately to have them rectify this.

error id: "bad_httpd_conf"

I can however ping & tracert www.kamikazelatinamerica.com

If I try to tracert it I get "Unable to resolve target system name kamikazelatinamerica.com"

 

[TAandy]

Originally posted by: GeoffS

Originally posted by: Spacehead
If it's any help, i can get the jkavt.com site in both FF & IE but can't get to www.kamikazelatinamerica.com in either browser. I just get the following:

Site Temporarily Unavailable
We apologize for the inconvenience. Please contact the webmaster/ tech support immediately to have them rectify this.

error id: "bad_httpd_conf"

I can however ping & tracert www.kamikazelatinamerica.com

If I try to tracert it I get "Unable to resolve target system name kamikazelatinamerica.com"

I'm on the other side of the Atlantic, gimme something to traceroute!!!

 

[EvilWobbles]

It sure looks like you've got DNS caching somewhere internally on your home network.

Does the ProSafe have any caching capabilities? Since your IPCONFIG shows it is acting as your DNS server, I would start there.

 

[GeoffS]

I've rebooted it a couple of times... I'll dig a bit more...

 

[GeoffS]

The ProSafe shows this for the DNS entries:

Domain Name Server
68.168.96.162
68.168.96.165

which come from my isp... I don't see anything about caching... *sigh*

 

[dmcowen674]

Your protocol stack may be out of order.

Turn of DHCP and put the 168.1.0.2 addy in and then after a re-boot go ahead and out it back to DHCP, that should fix the stack automatically for you.

 

[Spacehead]

Tracing route to www.kamikazelatinamerica.com [64.111.117.137]
over a maximum of 30 hops:

1 215 ms 192 ms 214 ms mead-max1.surferie.net [162.39.31.135]
2 243 ms 190 ms 208 ms meadrtr1.surferie.net [162.39.31.129]
3 236 ms 183 ms 255 ms h28.9.213.151.ip.alltel.net [151.213.9.28]
4 253 ms 198 ms 216 ms mdvlpa-3640-1.alltel.net [166.102.103.225]
5 271 ms 208 ms 239 ms h66.16.213.151.ip.alltel.net [151.213.16.66]
6 268 ms 241 ms 214 ms h250.33.213.151.ip.alltel.net [151.213.33.250]
7 284 ms 210 ms 227 ms so-7-0.hsa2.Cleveland1.Level3.net [4.78.59.33]
8 248 ms 223 ms 216 ms ge-6-1-5.hsa1.Cleveland1.Level3.net [209.244.22.105]
9 294 ms 231 ms 222 ms ge-7-0-0.mpls1.Cleveland1.Level3.net [209.244.22.97]
10 300 ms 288 ms 270 ms as-1-0.bbr2.LosAngeles1.Level3.net [64.159.0.246]
11 311 ms 315 ms 294 ms ge-9-0.ipcolo2.LosAngeles1.Level3.net [4.68.102.43]
12 317 ms 294 ms 271 ms 4.78.195.170
13 310 ms 343 ms 384 ms basic-hok.sepulveda.dreamhost.com [64.111.117.137]

Trace complete.