Ptr updating setup files
If your DHCP server is also a domain controller, then you are probably fine, if not, then you may want to see if the DHCP server is a member of the "Dns Update Proxy" group in AD.
Then check the Security tab on the Reverse Zone and make sure that group is authorized to create all child objects (DNS records) 2) If your statically-configured hosts are not updating the reverse zone, make sure their NICs are configured to register their IP in DNS (Windows hosts are enabled for this by default).
The configuration files for bind9 are cryptic and not particularly intuitive.
It is very easy to break a working setup, let alone fail to get it working, by missing off a single semi-colon or full stop.
I'm very interested in the user-space RCU (read-copy-update), and trying to simulate one via tr1::shared_ptr, here is the code, while I'm really a newbie in concurrent programming, would some experts help me to review?
3) If the issue is that your reverse zones are mismatched between domain controllers (meaning a host was able to register with one of the DCs, but the registration did not get replicated to the others) it could mean the zones themselves aren't replicating between domain controllers.
writer calls get_updating_copy() to gain a copy of the G1 (let's say it's G2), and only one writer is allowed to enter the critical section.
After the updating is done, writer calls update() to do a swap, and make the m_data_ptr pointing to the G2 data.
The forward DNS entries ("A" records) for windows machines on the domain are populated automatically.
However, the reverse DNS entries ("PTR" Records) are not.On the DNS tab enable DNS dynamic updates and set to "Always dynamically update..." Also enable Dynamic Update for clients that do not request updates.