I am administering a system which for reasons beyond my control have a disjoint DNS namespace. I don't like it, but that's how it is, and I have no way of changing this. The reason is that the servers need to co-exist with a pre-existing DNS infrastructure. The Windows Domain is named something like ad.example.com with a NETBIOS name of AD. However, all DNS servers have their primary DNS suffix set either to 'example.com' or to 'sub.example.com', depending on where in the network they are. I have configured the msDS-AllowedDNSSuffixes attribute in the domain, according to the.

The DNS for the ad.example.com domain is run on the two domain controllers in the environment, and the DNS for the example.com and the sub.example.com are run on other non-Microsoft DNS servers. In this environment, DNS is managed manually, rather than relying on Dynamic DNS registration and updates. The environment works fine, except for some annoying warning errors that appear in the event logs, that look like this: The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name: Host Name: Primary Domain Suffix: sub.example. Archetypes Of Wisdom By Douglas Soccio Pdf Files more. com DNS server list: (These are the domain controllers for ad.example.com) Sent update to server: IP Address(es): (This is the IP address of the host in question) The reason the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request. You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt.