I have a TLD with a series of subdomains that are public, say *.example.com
. I also have a private server which is used as a SVN repository, which I would like to have available at svn.example.com
, but only on the private network. Currently I've achieved that by creating the zone file svn.example.com.zone
and using this declaration:
zone "svn.example.com" IN {
type master;
file "/etc/named/svn.example.com.zone";
};
And in the zone file:
@ IN NS svn.example.com.
svn.example.com. IN A 10.200.1.1
All other domains are forwarded to the public nameserver. This works, but it's not ideal because it requires creating a whole new zone if I want to add a new private subdomain. If I make this zone the master record for the whole example.com
TLD, then I assume requests to the currently public *.example.com
will no longer work for clients using the private DNS (unless they are duplicated in the private DNS's zone file).
Is there a way for me provide a zone file that specifies one or more private subdomains, but still forwards requests it can't resolve to the public name server? I tried using the forward
zone type, but then I can't specify my own zone file, it only forwards.
Update
DNS for Rocket Scientists Chapter 6 gives an example DNS configuration of a stealth DNS server on an internal network. This seems to match up with what I want to achieve reasonably well, and specifically suggests duplicating the public DNS records in the private DNS zone. Obviously though the problem I want to solve is the duplication of records, so this is more a workaround.