On 2/26/06, Andrew Cady <d@jerkface.net> wrote:
Running a local caching dns server is just fine, and can improve
performance. If you are serving dhcp on a network, it is more or less
required. This is quite distinct from running an authoritative DNS
server which serves requests to the internet; that should not be done on
a home PC, unless you know what you're doing. But probably only people
who do would even try.
resolv.conf(5) contains an interesting comment:
On a normally configured system this file should not be necessary.
The only name server to be queried will be on the local machine; the
domain name is determined from the host name and the domain search
path is constructed from the domain name.
No doubt this is a holdover from ancient unix tradition: a "normal"
modern system is far less likely to run a local DNS server. However, it
still doesn't hurt.
I have a system in which router attached to a cable modem rewrites
/etc/resolve.conf whenever connection takes place. To the router 3 or
4 machines are connected and someitmes a machine with two interfaces
ie eth0 and wlan0 are connected. How to go about caching dns in such a
case?