DNS & multiple IP addresses on Server 2019

Question

On our site we have our network infrastucture (switches / access points / etc) in a management vlan. Many of these devices require a time server. I have created a virtual adapter on our Server 2019 DC for this purpose, and it works well except after a while the DNS service resolves the server hostname to the IP of that management vlan interface, and not its "official" interface in the office vlan & subnet. This is an issue because the management vlan is (of course) heavily restricted and has no access to the internet, unlike the office vlan. How can I tell the DNS service to always or only resolve the server hostname to the office vlan IP, and never to the management vlan IP?

Hope this makes sense. Any pointers appreciated!

Answer 1

Multi-homing a domain controller will always cause no end to grief for active directory DNS.

Some general info

• All domain members should use NT5DS domain time.
• Desktops and member servers sync with any domain controller.
• Domain controllers sync with PDC emulator (one per domain)
• PDC emulator in child domain can sync with any domain controller in parent domain.
• PDC emulator in parent domain syncs with either a hardware clock or possibly an external source.
  https://blogs.technet.microsoft.com/nepapfe/2013/03/01/its-simple-time-configuration-in-active-directory/

--please don't forget to upvote and Accept as answer if the reply is helpful--