This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 60%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
We are planning to migrate from a DNS appliance that handles internal and external DNS resolution to Active Directory and Azure DNS. We have started testing the migration of internal records from this appliance to AD integrated zones. We are looking to start work on migrating the external zones next. The challenge is that the DNS appliance handles internal and external name resolution for a few of the zones. Is our only option to split the zones and host them on AD DNS (internal Test.com) and Azure DNS (external Test.com) or is there some Azure DNS feature that we can leverage to minimize the administrative overhead of maintaining two zones?
If you are looking to resolve DNS names from on-premise, you will there is not an Azure solution which will work for your scenario. You can review the various name resolution scenarios here.
Azure Private DNS is close to what you are looking for, but will not fully fit your scenario.