PTR creation via delegated zone to alternative DNS server

Wes 0 Reputation points
2023-06-05T01:58:07.98+00:00

I have a mixed Windows DNS environment, where all systems related to this question are on-site (NOT Azure hosted). OS versions involved range between Windows Server 2012R2 - Server 2019.

AD Integrated DNS servers (the DC's themselves) are a mix of 2012R2 and 2016

Non-AD Integrated DNS is on 2012R2 and 2019, which the 2019 servers also host an internal Root zone. The Internal Root Primary is one of the 2019 servers, the others (2012R2 & 2019) are secondaries of the primary 2019 server with the 2012R2 only hosting a small secondary set of all zones that exist on 2019, although the 2012R2 are "front end gate keepers" for all non-AD integrated DNS queries (they can delegate to AD or to other environments not involved to this question)

I should also note:

  • that Root Hints have been deleted off all DNS servers
  • The AD DNS has default forwarding (recursive enabled) to the Non-AD DNS 2012R2 servers.
  • The Non-AD DNS 2012R2 servers forward all queries they cannot resolve (and where Conditional forwarder or other Delegations do not exist) to the internal Root 2019 servers with recursive enabled
  • The Non-AD DNS 2019 internal Root Secondaries have forwarding to the Primary if the secondaries cannot resolve (also with recursive enabled)
  • The Non-AD integrated DNS Servers ARE member of the same AD domain.

The question itself is in relation to PTR creation, as each environment (AD DNS, Root DNS, and others) currently have their own versions of reverse lookup zones, which I am looking to correct by restructuring everything, and by preference hosting most reverse lookup zones on the Root, with only delegated reverse zones from the root to other DNS environments as required (depending on VLAN/IP range allocations, etc)

Ive noted that if I attempt to create an A record in AD DNS with the PTR to be auto-created, eg PTR IP of 10.1.1.1 (which in AD DNS there is a hosted 10.in-addr.arpa zone with a sub-delegated zone of 1.1.10.in-addr.arpa to the Root Master directly and a respective primary hosted zone on the Root master), the A record is created successfully, but the PTR fails to be created.

Im suspecting that this is a known "by design" matter in Windows DNS where you cannot host the A record on one environment, and redirect the creation of the auto-created PTR to an alternative Windows DNS environment. Would this be correct?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,126 questions
Windows Network
Windows Network
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.Network: A group of devices that communicate either wirelessly or via a physical connection.
648 questions