How do I move from using a conditional forwarder to a forward lookup zone for a limited number of host records?

How do I move from using a conditional forwarder to a forward lookup zone for a limited number of host records?

To expand, I host AD integrated DNS for our domain (, but we also need to lookup addresses for our parent company ( I currently have a conditional forwarder for them pointing to their internal DNS servers, which works fine. They now need me to add a A record for a service that has both an internal and external IP address (i.e. internal and external). When my users resolve the address, they get the internal IP address of the server, but we want them to connect to the external IP address.

I was thinking of just deleting the conditional forwarder reference and adding a forward lookup zone for, and then adding the A record for that server with the external address, but I am concerned that it will stop all other resolution for other services (due to the loss of the conditional forwarders pointing to their internal DNS server). Do I resolve this problem by adding their internal DNS server to the Forward lookup zone>Properties>Name Servers tab?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
You can't do what you want. If you create a forward lookup zone for, your DNS server will believe it is authoritative snf. Even with forward records, won't work.. Your DNS server will believe there is no record. For anything that doesn't match a record in its zone and therefore won't bother to forward at all.

What you *can* do is create a zone for with the only A record beong rotlot (*or @) with the IP address you desire.

Yesxl that means for every A record that they want you to do, you need to create an entire zone, not just records in an existing zone l. But that means Tha lookups for other records in will continue to use your conditional forwarder.

With that said, if this is a partner or parent company then the RIGHT way to fix this is to fix it on their end. BIND has long since had the concept of "views" that can return the proper address based on a variety of criteria. Windows, though late to the game, added this functionality under the name "DNS Policies" in server 2016.  

It is a generally accepted best practice that whoever controls DNS for a resource should be the one addressing the address returned. While workarounds can be done in a pinch, and I've suggested one, the entity that controls should be the ones making sure their DNS returns the address they want using the tools available to do so.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Pete LongTechnical ConsultantCommented:
If you have a Cisco ASA firewall you can re-write the DNS reply to change it to the internal IP (DNS Doctoring)

Cliff's answer is what I would propose also.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.