I have the following scenario:
- A brand new ADDS domain from a single PDC+DNS.
- The FQDN of the domain matches our public website name (webname.com).
- The gateway dictates the PDC/DNS as the first DNS resolver. The secondary DNS is a public entity like 22.214.171.124 from both gateway and the PDC.
With this we get errors navigating to our website tld.com. This makes sense because the PDC has a forward lookup zone for webname.com and custom A records, etc.
The problem: DNS records like our MX record will not resolve on the internal network now unless created in the PDC/DNS entries. If we do not declare the PDC as the first DNS resolver we have trouble joining domain and resolving hostnames internally.
I could manually clone all the records in place and maintain two copies, but is there a better way? I still need the local PDC/DNS to handle DNS internally for FQDN device names (device.webname.com) but I want all other DNS requests to head out to the web otherwise so that public DNS record changes are recognized internally without manual duplication. Is there an elegant way to do this?
I tried adding secondary name servers on the PDC to point at the public DNS NS but that didn't seem to make any difference. Testing using nslookup from inside the network shows me that I'm not touching the external NS still when looking for an MX record for example.