Comments on: How To Set Caching DNS Server

By: Dharma

Dharma — Mon, 26 Sep 2011 17:59:03 +0000

/etc/resolv.conf first nameserver must be 127.0.0.1 to make it works as dns request cached by localhost

By: Rocky

Rocky — Wed, 15 Sep 2010 06:50:20 +0000

Hi,

For caching dns server dnsmasq is better or bind(named)……………?

Regards,
ROcky

By: commonsense

commonsense — Tue, 06 Apr 2010 09:27:24 +0000

dnsmasq is OK. It sits between the user and the recursor; but it won’t dump the cache for backups (see a program called “pdns”, not PowerDNS, for that).

dnsmasq can read from /etc/hosts which is good. But have a look at a program called nsd.

This is the way it should be done. The recursive lookup and authoritative answer functions should be separate programs. It should have been this way from the beginning. But common sense does not always prevail.

nsd just serves up DNS records. That’s all it does. It’s fast.

It has a utility to convert BIND-style zone files into the binary format that nsd can read. In theory this should speed up performance. nsd is fast. And having an nsd databse of DNS info is nice reassurance.

By: Norman T

Norman T — Fri, 13 Mar 2009 00:10:09 +0000

I had the same question as Binny … how does the local server know to use the dnsmasq service before hitting the upstream servers if you don’t modify /etc/resolv.conf?

I could see this working for other systems on a local network, but for the server running dnsmasq itself, where does the cache come in? Thanks for any help!

By: Binny V A

Binny V A — Mon, 19 Jan 2009 19:10:35 +0000

Fedora 8 – that smile was inserted by WP without my permission ;-)

By: Binny V A

Binny V A — Mon, 19 Jan 2009 19:09:12 +0000

Shouldn’t you add
nameserver 127.0.0.1
to ‘/etc/resolve.conf’ for this to work?

Another thing – yum install dnsmasq works fine(I tested it in Fedora 8)