Bug 12258 - Dynamic update ptr (reverse DNS) not working
Summary: Dynamic update ptr (reverse DNS) not working
Status: RESOLVED DUPLICATE of bug 10876
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: DNS server (internal) (show other bugs)
Version: 4.5.0
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Kai Blin
QA Contact: Samba QA Contact
Depends on:
Reported: 2016-09-13 05:39 UTC by Kelvin Yip
Modified: 2020-12-21 11:38 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Kelvin Yip 2016-09-13 05:39:06 UTC

I am using internal DNS from samba 4.5.0. The workstation are able to update their dns record in forward zone, but not reverse lookup zones. 

The following group policy is already configured:
1. Use this connection’s DNS suffix in DNS registration
2. Register DNS records with connection-specific DNS suffix

When I execute ipconfig /registerdns, the event viewer shows the following message:

The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings:

           Adapter Name : {7331AFE3-CAB9-4427-AF55-4D3252C2DA57}
           Host Name : WIN-WIN7
           Primary Domain Suffix : mydomain.com
           DNS server list :
           Sent update to server : <?>
           IP Address(es) :

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.
Comment 1 Björn Jacke 2020-12-21 11:38:27 UTC
mostprobably a dup of bug 10876

*** This bug has been marked as a duplicate of bug 10876 ***