default local DNS caching name server
Bruno Wolff III
bruno at wolff.to
Fri Apr 11 20:47:26 UTC 2014
On Fri, Apr 11, 2014 at 15:33:48 -0500,
Chris Adams <linux at cmadams.net> wrote:
>Once upon a time, Bruno Wolff III <bruno at wolff.to> said:
>> If you are running a caching resolver you don't need the DNS
>> information from DCHP (except except for the hotspot issue) at all.
>Unless you have a specific reason not to, you should use the DNS server
>from DHCP. That may be the only DNS server that will work, there may be
>private DNS info not available anywhere else, etc.
Split horizon should still work with a caching recursive resolver (since
that is based on the IP address of where the request is coming from). It
won't work if network dnsserver provides alternative data out side of its
bailiwick. But if these outside of bailiwick domains are known to you, you
can tell your resolver where to look for them.
If the network operator is just outright breaking things so that you can
only connect to their dns server, well then you're going to need to do
something about that. But even if it is switch to their server, you might
want to know that that kind of thing is going on.
The advantage of using your dns server is that you know what you're getting.
Some large ISPs are known to do interesting things with dns information
(such as rewrite ttl information) that can cause problems that are avoided
by using your own server.
More information about the devel