2

I have a public domain, say test.com. The DNS records are stored somewhere in the cloud. However, on my Windows Server 2008 DNS servers, I want to add some internal subdomains such as sub1.test.com.

When my internal DNS server receives a request for sub1.test.com, I want it to use the record I've created, but when it receives a request for other records such as test.com and sub2.test.com, for which I have not locally created records, I want it to forward those on to an external DNS server for lookup.

I know there is a very ugly way to do this by creating a new primary dns zone for each subdomain, but that really clutters up my forward lookup zones very quickly (I'd easily have over 200 entries).

I also know that I can create a primary zone for test.com, and manually specify every single entry (this is what we do today), but that requires double work (once on the public dns, once on the internal) and is "fragile" since changes to the external dns entries don't automatically update the internal records.

Is is possible to perform this partial domain forwarding?

Ashley Reid
  • 123
  • 2
  • 1
    You've answered your own question - `I know there is a very ugly way to do this by creating a new primary dns zone for each subdomain` – joeqwerty Mar 26 '14 at 15:34

2 Answers2

1

I think the "ugly" way of creating primary DNS zones is the only way to achieve this. We do this internally as well, and I'm not aware of any other approach.

MichelZ
  • 11,008
  • 4
  • 30
  • 58
1

The only workaround you haven't already mentioned in your OP would be to simply put the records into your public DNS with private IPs.

See here: Private IP address in public DNS for a detailed discussion on pros/cons of doing so, but it is doable.

TheCleaner
  • 32,352
  • 26
  • 126
  • 188
  • Thanks. I like the idea of only needing to update one place, although having to wait for DNS propagation may not be acceptable form a developer perspective... I'll definitely give this some thought. – Ashley Reid Mar 27 '14 at 16:35