On Wed, Dec 18, 2002 at 02:35:35PM -0500, Mark L. Kahnt wrote: > That was the first reboot in five weeks, and when the system came back, > it couldn't find "localhost". It could find hosehead.dyndns.org and its > various morphs (hosehead.dyndns.ws and mlkahnt.dyndns.org,) and it had > no problem with 127.0.0.1, 192.168.1.1 (eth1) and 192.168.1.3 (eth0), > either. /etc/hosts was unchanged, but /etc/resolv.conf had been reduced > to just two entries - my ISPs nameservers, each preceded by a blank > line, leaving me to believe that some program is doing the rewrite on > bringing up the network link (I suspect the culprit is "usepeerdns" in > /etc/ppp/peers/dsl-provider, although that has been there for over seven > months.)
This may be a silly thing to ask, but do you get the right answers when you nslookup localhost and 127.0.0.1? And if not, do you have them defined in your zone files (you should)? -- Michael Heironimus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
