 |
 |
That's interesting, I just did the same lookup using 35.8.98.43 and got back the correct response. Perhaps ACNS is currently working on this issue? -Jim Willson -----Original Message----- From: MSU Network Administrators Group [mailto:[log in to unmask]] On Behalf Of Rob Keena Sent: Thursday, August 04, 2005 2:01 PM To: [log in to unmask] Subject: Re: [MSUNAG] .org strangeness I noticed something similar on one of my Linux machines last week. It appears to be a DNS issue as shown below: A dig for debian.org against the MSU DNS server returns no answer. rob@netserver:~$ dig @35.8.98.43 debian.org ;; ANSWER SECTION: ;debian.org. IN A But against an external DNS server (4.2.2.2) it returns the proper result. rob@netserver:~$ dig @4.2.2.2 debian.org ;; ANSWER SECTION: ;debian.org. 3600 IN A 192.25.206.10 What DNS servers do you have assigned for your static machines? Perhaps they are different than the ones the dynamic machines are querying. -Rob Keena Missy Koos wrote: >We were noticing the same DHCP problem in the student services >building. We checked to make sure it wasn't a browser specific thing. >But IE, FireFox, Safari and Opera all had the same problems. Static IP >users though don't encounter it. > >Really Strange! > >:) >Missy > > >On 8/4/05 1:30 PM, "Bryan Murphy" <[log in to unmask]> wrote: > > > >>Is anyone noticing any problems communicating with .org domains from >>dhcp machines? >> >>I have noticed a number of .org's simply not working when attempting >>to browse to them with firefox. Ping, traceroute and dig also return >>host unreachable errors and the like. >> >>I have confirmed that this only happens with machines configured to >>use dhcp, the static ones seem fine. I have also noticed that a >>select few .org sites work and are pingable, slashdot for example >>(although after a reboot I see that it stopped working). >> >>I have no idea why it would effect only one tld. >> >> > > >