We have a situation where we have domain controllers across the world which have their own child DNS domains:
Ex. sitea.mycompany.com , siteb.mycompany.com, etc
These sites all have their own internet connectivity as well as MPLS back to the company's data center.
Currently the remote DNS servers all have forwarders which point to DNS servers in the data center. The data center DNS servers then have forwarders which go out to the internet to resolve outside DNS queries.
This solution works, but a side effect we have noticed is related to websites that utilize Akamai. Since all outside DNS queries are being sourced from the data center DNS servers, Akamai is returning IP addresses which are closest to the data center in the US, and not the remote sites spread out across the world.
In order to fix this we need the local DNS servers to go out the local internet connection and resolve their own external DNS queries. Akamai will then see a source IP local to the site and return an IP which is much closer to the site than the US.
The data center DNS servers have DNS zones which can be expanded at any time:
Ex. mycompany.com, domain-today.com, lookhere1.local, etc. domain-tomorrow.com can be added next month.
New domains could be added a month from now and it isn't practical to touch each remote DNS server to add a new stub domain.
My idea is to have the Data Center DNS servers listed as the top forwarder servers. The Data Center DNS servers will then be configured to not be recursive, so if the zone does not live on it then it will not forward it to an internet DNS server. Will the remote DNS server then go down it's forwarder list and send a request to the next server (which we would configure to be an internet DNS server)?
If this isn't a viable solution does anyone have any other suggestions?