In this section I list some of the most frequently asked questions related to DNS and this HOWTO. And the answers :-) Please read this section before mailing me.
A couple of hints: `forwarders', `slave', and have a look in the literature list at the end of this HOWTO.
Make several A records for www.busy.site and use bind 4.9.3 or later. Then bind will round-robin the answers. It will not work with earlier versions of bind.
You drop the cache file and just do zone files. That also means you don't have to get new cache files all the time.
Your system then has an old, somewhat obsolete, bind installed.
If security is important to you: upgrade bind at once. If not, you
can live with it. And instead of running ndc start
you run
named
. ndc reload
becomes named.reload
and ndc
restart
becomes named.restart
. All of those programs are most
likely in /usr/sbin
.
If the primary server has address 127.0.0.1 you put a line like this in the named.boot file of your secondary:
secondary linux.bogus 127.0.0.1 sz/linux.bogus
I have received this mail from Ian Clark <ic@deakin.edu.au> where he explains his way of doing this:
I run named on my 'Masquerading' machine here. I have
two root.cache files, one called root.cache.real which contains
the real root server names and the other called root.cache.fake
which contains...
--------------
; root.cache.fake
; this file contains no information
--------------
When I go off line I copy the root.cache.fake file to root.cache and
restart named.
When I go online I copy root.cache.real to root.cache and restart
named.
This is done from ip-down & ip-up respectively.
The first time I do a query off line on a domain name named doesn't
have details for it puts an entry like this in messages..
Jan 28 20:10:11 hazchem named[10147]: No root nameserver for class IN
which I can live with.
It certainly seems to work for me. I can use the nameserver for
local machines while off the 'net without the timeout delay for
external domain names and I while on the 'net queries for external
domains work normally
The cache is completely stored in memory, it is not written to disk at any time. Every time you kill named the cache is lost. The cache is not controllable in any way. named manages it according to some simple rules and that is it. You cannot control the cache or the cache size in any way for any reason. If you want to you can ``fix'' this by hacking named. This is however not recommended.
No, named does not save the cache when it dies. That means that the cache must be built anew each time you kill and restart named. There is no way to make named save the cache in a file. If you want you can ``fix'' this by hacking named. This is however not recommended.