question

N8ldn avatar image
0 Votes"
N8ldn asked ·

Server not registering in DNS - Azure

Help please, I'm unable to register newly created server to DNS, however, newly created server can be added to the domain but does not appear on DNS.

Any suggestion....

ERROR

The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings: Adapter Name : {E9B782ED-71CA-4211-B056-34680423F359} Host Name : GOTO Primary Domain Suffix : domain.co.uk DNS server list : 10.1X.XX.XX, 10.1X.XX.XX, 10.1X.XX.XX Sent update to server : 10.1X.XX.XX:53 IP Address(es) : 10.1X.XX.135 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. If problems still persist, contact your DNS server or network systems administrator. See event details for specific error code information.

azure-ad-domain-services
· 2
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@N8ldn ,

Is this newly created server running as a VM in Azure and you have your domain/domain controllers also running on Azure VMs ?? . There could be three possible reasons that I can think of , one is the DNS zone has some permissions issue which is highly unlikely . If you run DHCP as well on the same domain controller where your DNS zone exists ,then you may see some issues like this. The second could be your Adapter settings on the network adapter of the server which is trying to register its name in DNS. Please check if the Register this connections address in DNS is checked or not . It should be checked.

73406-image.png

The third could be that you may have some DNS zone specific setting on the DNS server. Are you pointing for DNS to the same domain controller which you used for joining the machine to the domain or a different one ?


1/2


0 Votes 0 ·
image.png (159.1 KiB)

Also another thing is you have mentioned the primary domain suffix as domain.co.uk . Is this same as the name of the domain this machine is joined to or is this one different ? If its different then you have this setup on the network adapter properties which can be accessed using Start > Run > ncpa.cpl command which you would need to change as per the picture posted in earlier comment . You need to make sure that the DNS suffixes are correctly set in order.

If all the VMs in this scenario are in the same Virtual Network on azure , then you need to make sure that the first IP in the DNS server section on the VNET associated is your domain controller IP .

Let us know more about your environment and we will help you further on this.

2/2

0 Votes 0 ·

0 Answers