-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Normally at a motel you would obtain both the IP and the DNS from their
dhcp server.  In this case the /etc/resolve.conf file is written when
you acquire your address (in fact the first line says "; generated by
/sbin/dhclient-script" ).  Is it possible this tripped you up?  Most
systems out of the box avoid running their own name services and use
only this plus the hosts table to resolve network addresses.

Keith Lofstrom wrote:
> This weekend at a motel with free wifi, the nameserver was broken
> and spewing some incorrect IP addresses ( wikipedia = 1.0.0.0
> for example ).  Traffic to numeric IP addresses flowed normally.
> 
> I attempted a workaround by putting known-good nameservers in
> /etc/resolv.conf .  Unfortunately, I still saw a lot of borked
> DNS resolution, and surfing and pinging sites that I had attempted
> before the fix resulted in the same errors.  The errors persisted
> over a reboot.
> 
> I recently converted from RH9 2.4.22 to SL4.4 2.6.9 , and I don't
> know how the new system does DNS resolution (it appears to be in
> the kernel instead of a separate program like named) and how SELINUX
> affects the mix.  Is there a cache file like /var/named/named.ca on
> the old system?  If so, how do I zero it out?  Or is SELINUX
> preventing the kernel from seeing my changed /etc/resolv.conf file?  
> 
> I am no longer at the motel, but if I get a useful solution I would
> like to test it against a intentionally incorrect nameserver and
> make sure the solution works for me.  Are there any intentionally
> incorrect nameservers (as opposed to all the intermittently incorrect
> ones) out there to test with?
> 
> Keith
> 

- --
Robert E. Blair, Room E277, Building 362
Argonne National Laboratory (High Energy Physics Division)
9700 South Cass Avenue, Argonne, IL 60439, USA
Phone: (630)-252-7545  FAX: (630)-252-5782
GnuPG Public Key: http://www.hep.anl.gov/reb/key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFF9dK1CDBz0lN+7YcRAgC8AKCWwatN1zUcsRsKvwMJVHAQeXjDYgCgkgKS
tIj5nwa5cUgpgBB3/cButCQ=
=bN04
-----END PGP SIGNATURE-----