NS record for 127.0.0.1?

Jim Reid jim at rfc1035.com
Mon Dec 11 11:07:24 UTC 2000


>>>>> "Bob" == Bob Proulx <bob at torment.proulx.com> writes:

    Bob> Summary: What should the NS record be for 127.0.0.1?  Can I
    Bob> use "localhost."?

Why do you have a 127.0.0.1 zone? Maybe you meant to ask what NS
records would be suitable for the 0.0.127.in-addr.arpa and localhost
zones? If you did, the answer is you can use whatever you like, within
reason.

It's a good idea to make each of your name servers authoritative for
these zones. You might as well make each server master for them and
have just one NS record pointing at localhost.  That way, the servers
can answer for these zones without consulting any other servers. The
single NS record in each zone pointing at localhost is OK because the
local server answers for the zone. This saves having to set up slave
servers for them. The contents of both zones will probably never
change, so each server might as well be configured as master for
them. It also prevents pointless NOTIFY messages and spares the name
server from resolving some other hostname(s) for the zone's NS
record(s). In essence the NS record for the 0.0.127.in-addr.arpa and
localhost zones is just to shut the name server up because it demands
each zone has at least one of them.



More information about the bind-users mailing list