DNS lookup fails connecting to server on same network

Top Page
Attachments:
Message as email
+ (text/plain)
+ signature.asc (application/pgp-signature)
+ (text/plain)
Delete this message
Reply to this message
Author: Ryan Rix
Date:  
To: Main PLUG discussion list
Subject: DNS lookup fails connecting to server on same network
Hi,

I have recently configured a new Debian GNU/Linux server and migrated the
settings and stuffs from my old laptopserver.

Everything works shiningly, except for one thing: when I try to access the
server via its fqdn, my laptop returns a DNS error, unknown host.

I know that somewhere in the bowels of my laptop, only while connected to the
same network as the server behind a dlink G router, it's becoming corrupted
because:

maylay:~# nslookup wanton.dyndns.org 205.171.2.65
Server:         205.171.2.65
Address:        205.171.2.65#53


Non-authoritative answer:
Name: wanton.dyndns.org
Address: 204.193.219.193

where 205.11.2.65 is the primary dns reported by the router. The address it
pulls is valid, indeed.

maylay:~# nslookup wanton.dyndns.org
Server:         192.168.0.1
Address:        192.168.0.1#53


Non-authoritative answer:
Name: wanton.dyndns.org
Address: 204.193.219.193

using the router for DNS reports the same IP address, leading me to believe
the laptop is corrupting or doing *SOMETHING* to prevent a connection.

My hosts file is clean:
127.0.0.1 localhost

I think that would be the only thing prohibiting a connection on the laptop,
so I honestly am at a loss of what to do.

Any ideas are much appreciated.
~Ryan


--
Thanks and best regards,
Ryan Rix
TamsPalm - The PalmOS Blog

"See, he's more dangerous during the off season"




---------------------------------------------------
PLUG-discuss mailing list -
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss