Maybe do something with a split-brain deployment.
https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/split-brain-dns-deployment
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi there,
Hope there is someone can help me on this case.
I am facing a problem when create a CNAME in forward zone on our internal DNS.
Our primary domain is abc.com and have a developing domain abc-dev.com.
Both domain are existing in external DNS server, but abc.com only existing on internal DNS server.
Our developer is requesting to have a CNAME, uat.abc-dev.com, and can only be resolved internally.
I tried to create a new zone in internal DNS server which is abc-dev.com and added a CNAME uat. in there.
But this caused all other existing abc-dev.com URLs cannot be resolved internally.
Because CNAME cannot be the record as parent, I cannot create a forward zone named as uat.abc-dev.com.
I tried to add a forwarder, but it still does not work for resolving other abc-dev.com URLs.
Could you please let me know if there is a way to solve this problem?
Thank you.
Maybe do something with a split-brain deployment.
https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/split-brain-dns-deployment
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
Some ideas here.
https://serverfault.com/questions/118290/cname-record-alias-in-windows-hosts-file
--please don't forget to upvote
and Accept as answer
if the reply is helpful--