We have a split brain DNS scenario in our company where we have the same entries pointing towards different IPs.
Example1:
Internal DNS: email.company.net (A) 172.20.1.1
External DNS: email.company.net (A) 22.191.72.18
So email is just one of the few entries that we have to 'split'. We do have alot of other DNS entries in our public DNS zone, that need to remain the same in the internal zone as well. Lets have a look at another example:
Example2:
Internal DNS: video.company.net (A) -not present-
External DNS: video.company.net (A) 22.191.72.49
So when i want to access videoportal.company.net from inside the company, the DNS server reports that it has not found a DNS entry for that query. In order for it to work, i'd have to recreate all the external DNS entries on the internal DNS zone as well and maintain all those records over the time as well. This causes alot of duplicate work. What i'd like to do is following:
Create a zone with some entries in it and assign it a policy that says: "resolve what you can find in there, but forward anything you cannot find to your resolvers/root hints"
Is there something like this that can be done with policies? How is such a functionality even called?
I know that i can create a zone with email.company.net and a empty A record inside. This forwards any somethingelse.company.net record still externally. The reason i ask is much more complicated and i wanted to ask a question as short as possible. So just assume that this solution does not apply here right now. I would appreciate if you could concentrate on the question above.
Edit: So in the end, the internal DNS server should do something like this:
- DNS server gets request from client for email.company.net
- DNS server does a lookup in his internal zone company.net
- DNS server gives back IP 172.20.1.1 to the client
- DNS server gets request from client for video.company.net
- DNS server does a lookup in his internal zone company.net
- DNS server does not find an entry for video.company.net
- DNS server then does a recursive lookup via his root hints
- DNS server ultimately gets the answer and gives back IP 22.191.72.49 to the client