/etc/resolv.conf SuSEconfig
search localhost mynetmax.net
nameserver 207.91.5.20 # ISP's nameserver
--- D E Hammond
On 29 Sep, TRBishop wrote:
First, thanks for the replies jb & Don. /etc/hosts 127.0.0.1 localhost 192.168.0.1 mynetmax.net netmax #Internet server 192.168.0.3 linuxbox.net linuxbox #SuSE 7.0 Samba 192.168.0.8 bizibox2.net bizibox2 #Win98
Looks fine.
/etc/resolv.conf
search mynetmax.net navix.net nameserver 192.168.0.1 nameserver 207.91.5.20 #this is my dial-up ISP
/etc/resolv.conf SuSEconfig
search localhost mynetmax.net navix.net linuxbox.net nameserver 127.0.0.1 nameserver 192.168.0.1 nameserver 207.91.5.20 nameserver 192.168.0.3
The first one is the one in place, right? Because I'd eliminate localhost from the search line if you're using the second. I don't think it's your problem, but it's going to slow down every lookup that makes it as far as the searchlist because each of these will be appended in turn to whatever name is being resolved. e.g. 'telnet somehost', if "somehost" does not resolve, the resolver will try somehost.localhost, then somehost.mynetmax.net, and so on. localhost seems like a waste here, but I'm not a dns expert.
Let me repeat: I'm not a dns expert, but I don't list localhost as a nameserver. I run primary and secondary dns servers for my internal namespace, and use the IP (as you've done in the second line). This is true of all boxes on the LAN, including the two running named (IOW, they each list their own IP address). Again, I don't think this hurts anything. You should be able to communicate with yourself on lo, but since 'localhost' seems to be the problem, it'd be worth a try eliminating it from the mix.
I mentioned in my first response that if you're running your own dns (which we see now you are), it should be authoritative for the 127.0.0.0 network. So your zone file should include an A resource record for localhost, mapped to 127.0.0.1 just like the rest of the nodes. And the named.boot (or whatever your conf file is) should be primary for address to name (reverse or ptr) mapping of that IP, with a corresponding db file for that network. I don't know how the 'www.' and '.com' could be appended to localhost even if this is missing (did I say I'm not an expert <g>), so this still might not be your problem. But it's all I can think of besides a misbehaved browser that's doing it automatically.
- Don
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/support/faq
__________________________________________________ Do You Yahoo!? Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free! http://photos.yahoo.com/ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq