Using Windows 2008 R2 DNS:
We have a Forward Lookup Zone:
somerealdomain.com us-wil | A | 10.10.0.1 us-chi | A | 10.10.0.2 us-day | A | 10.10.0.3 us-sea | A | 10.10.0.4 us-sf | A | 10.10.0.5 us-ny | A | 10.10.0.6 give | A | 10.10.0.7 me | A | 10.10.0.8 test | A | 10.10.0.9
If I do an
NSLookup for any of those, they obviously get pointed correctly to the internal IP.
Now, if I want any non-existant subdomain to resolve using external DNS as provided by our Forwarders 220.127.116.11, 18.104.22.168 etc. how can I accomplish that? Say, I want to resolve get.somerealdomain.com which is not included in the Forward Lookup Zone, but is resolvable on Public DNS Servers?
I need this so if someone searches a subdomain we haven't included in our Forward Lookup Zone, it will go out the a public DNS server and resolve. I assumed this would happen by default as it does with any other domain we have not written records for, but because we have the somrealdomain.com as a Forward Lookup Zone, any subdomain which does not have a record written just dies instead of asking external DNS. Why? How can I resolve this?