Create Active Directory integrated zone in DNS

[Brruno]

This is probably a difficult task!! So thought that posting here would help, since got many help from here. Everyone knows that the replication of the DC (domain controller), an AD (Active Directory) integrated DNS server is required. However, if I create such a welcome, the required subdirectories (Ldap, tcp ...) not created. Even after a reboot does not change that. Meanwhile, I built a third DC. But now I have a real problem because I can not this do with DCPROMO, because DNS is not available. Of course, the server on which to run the DNS itself specified as a DNS (TCP / IP). It does, however, everything is nothing. It simply no longer creates the subdirectories. Because someone has an idea? The Internet is a lot of replication and that requires AD-DNS, but there is no help if it can not be created correctly.

[Joko]

DNS server has updated its own host (A). To ensure that its DS-integrated peer DNS servers are able to replicate with the server was trying to update them with the new records through dynamic update. It is an error. The data is the error code. If the replication partners of the Active Directory for this DNS server is not the correct IP address for that server, they can not replicate with it. Follow these steps to make sure that replication is carried out properly:

1. Look for the replication partners of the Active Directory for this server, run the DNS server.
2. Open the DNS Manager and connect in turn to each of the replication partners.
3. Check for each of the servers that host (A record) registration for THIS server.
4. Delete any A records that do NOT correspond to IP addresses for that server.
5. If no A records for this server, you must add at least one A record corresponding to an address on this server, which can address the replication partners. (In other words, if there multiple IP addresses for this server, add at least one that is in the same network as the DNS server's Active Directory, you want to update.)
6. It is not necessary to update EVERY replication partner. It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server, the new data (through replication) is replaced.

[Rixwel]

The previous stages of a DC for DNS Unavailable force you can use dcpromo / force removal. Then find the relegation place in any event and the entries of the downgraded by force DC must be deleted manually. The latter is indeed the hour of absence DNS not your biggest problem. Request of the two DCs entries such warnings and error Event Viewer post here .... Application, system, DNS, directory service.

[Brruno]

Because of repeated network problems, the time service to locate a domain controller to synchronize. The time service will wait 960 minutes before trying again (n) to reduce network traffic. During this time interval will be no synchronization, even if network connectivity is restored. May cause certain network operations to fail due to time errors. Run "w32tm / s" from the command line To tell the time service to restore the network connections so that the re-synchronization is performed.

ID: 5722 (system log)

The session setup from computer "WZB" failed to authenticate. The account name in the security database is WZB $. The following error occurred:
Access denied

failed with the following status:

The DSA operation is unable to proceed because of a DNS lookup failure.

The data is the status code. The process is repeated.