On Tue, 2006-02-28 at 16:11 +0100, Ralph.Grothe@xxxxxxxxxxxxxx wrote: > Needless to say that neither nslookup, nor host, nor dig > care about the content of nsswitch.conf but instead straight away > seem to query the first nameserver from /etc/resolv.conf. NB: There's also an /etc/host.conf file There's any number of things which don't pay attention to the hosts file (e.g. I found Squid didn't), some of which makes sense (e.g. mail servers wanting MX records), other's not. The host, nslookup and dig tools are meant for querying name servers (according to the manuals), which the hosts file isn't (and it can only provide some of the functionality that a real name server would provide), so I'm not too put out by them not using the hosts file. Most other things, e.g. the ping command, the X server, don't seem to mind using the hosts file, though. I run a small LAN, so I decided it was in my interest to run a local DNS server, for several reasons. My hosts files only contain the loopback addresses, and each machine's own addresses (so they can run disconnected from the network without problems). I don't think that you're finding anything unusual (i.e. it's not something peculiar to your own system). -- (Currently running FC4, in case that's important to the thread) Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
