It seems like all the examples I see on the net for zone files always presume a range of servers on the same subnet. The modern situation on the cloud is many servers, all on the same domain, but with completely independent subnets. I am trying to setup NSD. My example config: nameservers: ns1.example.com 128.56.78.234 ns2.example.com 212.200.120.34 web servers: host1.example.com 135.87.23.45 host2.example.com 78.45.23.10 host3.example.com 99.55.22.33 All the addresses are fictional of course. what are the proper forward and reverse files? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20140409/12abaf28/attachment.htm>
Stephane Bortzmeyer
2014-Apr-10 08:45 UTC
[nsd-users] Newbie [and not NSD-specific] question
On Wed, Apr 09, 2014 at 06:40:37AM -0400, Bob James <mebobj at gmail.com> wrote a message of 64 lines which said:> It seems like all the examples I see on the net for zone files > always presume a range of servers on the same subnet.I'm suprised because it is certainly not what I see. Anyway, the content of the resource records changes nothing to the server's configuration.> what are the proper forwardhost1 IN A 135.87.23.45 host2 IN A 78.45.23.10 host3 IN A 99.55.22.33 There is nothing special or magic in the right-hand side of the A records. They can be in very different prefixes.> and reverse files?If you mean the in-addr.arpa zones, it is more complicated. You do not always have a DNS delegation from the operator on these zones. Some providers allow you to configure a PTR record. Talk to your Web hoster.