On 18/10/12 12:36, Matthew J. Roth wrote:
Bob Goodwin wrote:
> [bobg@box9 ~]$ wget 204.14.213.188
> --2012-10-18 12:13:39--
http://204.14.213.188/
> Connecting to 204.14.213.188:80... connected.
> HTTP request sent, awaiting response... 302 Found
> Location:
http://www.newegg.com/Index.aspx [following]
> --2012-10-18 12:13:40--
http://www.newegg.com/Index.aspx
> Resolving
www.newegg.com... 208.91.197.27
Newegg responded with a 302 redirect with "www.newegg.com" in the
location and that was resolved to 208.91.197.27. Something is
definitely wrong with your DNS resolution, but it doesn't seem to be
specific to your computer since your daughter is having similar
problems.
What is the output of the following commands?
$ dig @8.8.8.8 +short
www.newegg.com
$ dig @208.67.220.220 +short
www.newegg.com
$ dig @12.189.32.61 +short
www.newegg.com
For reference, I get:
$ dig @8.8.8.8 +short
www.newegg.com
216.52.208.185
$ dig @208.67.220.220 +short
www.newegg.com
216.52.208.185
$ dig @12.189.32.61 +short
www.newegg.com
;; connection timed out; no servers could be reached
Regards,
Matthew Roth
InterMedia Marketing Solutions
Software Engineer and Systems Developer
I get [using the opendns name servers again]:
[bobg@box9 ~]$ dig @8.8.8.8 +short
208.91.197.27
Perhaps they respond differently as a function of the inquiring address?
--