Hello All,
We were discussing DNS caching and the bind configuration. However, bind is a DNS server whereas we only want a DNS cache that updates itself automatically. Maybe I understood it wrong but on the net I found this link for DNS caching. It uses a package called dnsmasq. It works on my system. First time I do dig google.com it takes 42 ms. second time 2 sec.
http://ubuntu.wordpress.com/2006/08/02/local-dns-cache-for-faster-browsing/
On Sun, 2007-08-26 at 21:57 +0530, Rony wrote:
Hello All,
We were discussing DNS caching and the bind configuration. However, bind is a DNS server whereas we only want a DNS cache that updates itself automatically. Maybe I understood it wrong but on the net I found this link for DNS caching. It uses a package called dnsmasq. It works on my system. First time I do dig google.com it takes 42 ms. second time 2 sec.
http://ubuntu.wordpress.com/2006/08/02/local-dns-cache-for-faster-browsing/
Ronny is right. BIND is waay too heavy if you want just a caching DNS server. There are lots of smaller, less resource intensive servers for Linux.
On 28-Aug-07, at 11:02 PM, Dinesh Joshi wrote:
We were discussing DNS caching and the bind configuration. However, bind is a DNS server whereas we only want a DNS cache that updates itself automatically. Maybe I understood it wrong but on the net I found this link for DNS caching. It uses a package called dnsmasq. It works on my system. First time I do dig google.com it takes 42 ms. second time 2 sec.
http://ubuntu.wordpress.com/2006/08/02/local-dns-cache-for-faster- browsing/
Ronny is right. BIND is waay too heavy if you want just a caching DNS server. There are lots of smaller, less resource intensive servers for Linux.
the BIND caching only nameserver comes by default on most distros, and is a one-click install that works out of the box - the only thing you need to do is put 127.0.0.1 in /etc/resolv.conf
Kenneth Gonsalves wrote:
the BIND caching only nameserver comes by default on most distros, and is a one-click install that works out of the box - the only thing you need to do is put 127.0.0.1 in /etc/resolv.conf
Oh it was that simple. I did not know. Thanks for the info.
On 29-Aug-07, at 1:04 PM, Rony wrote:
the BIND caching only nameserver comes by default on most distros, and is a one-click install that works out of the box - the only thing you need to do is put 127.0.0.1 in /etc/resolv.conf
Oh it was that simple. I did not know. Thanks for the info.
oops, also put it as the nameserver on all the ethernet interfaces on the box, or it will be overrwritten on the next boot on most distros
On 8/28/07, Dinesh Joshi dinesh.a.joshi@gmail.com wrote:
Ronny is right. BIND is waay too heavy if you want just a caching DNS server. There are lots of smaller, less resource intensive servers for Linux.
One of the options to look at is djbdns - http://cr.yp.to/djbdns.html
On 8/26/07, Rony ronbillypop@yahoo.co.uk wrote:
We were discussing DNS caching and the bind configuration. However, bind is a DNS server whereas we only want a DNS cache that updates itself automatically. Maybe I understood it wrong but on the net I found this link for DNS caching. It uses a package called dnsmasq. It works on my system. First time I do dig google.com it takes 42 ms. second time 2 sec.
http://ubuntu.wordpress.com/2006/08/02/local-dns-cache-for-faster-browsing/
I think the issue is more of routing to google.com than DNS. I've been using OpenDNS for a few days now and the difference between Sify and MTNL when it comes to loading google.com is still immense with Sify being the better of the two.
Too bad we can't have Open routing as well :)
-
Dinesh Joshi -
Kenneth Gonsalves -
mehul -
Rony -
Siddhesh Poyarekar