Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.
Hi
Ensure that this option "Register this connection's addresses in DNS" checkbox is not cleared, to check this:
- Right click on the network adpater of your DC and select propeties
- Double click on the TCP/IP V4
- Click Advanced
- Click DNS Tab, you will see this option at the bottom of this tab.
If the above steps not helped you than surely you have incorrectly configured your TCP/IP settings of your DC or DNS servers
HTH
Best Regards,
1. Well firstly i'd use the command line tools :
Netdiag and dcdiag to understand if there is a break.
Check DNS pointing as in if the DNS server is pointing to itself as Preferred and the other DC as secondary.
Check physical connectivity between the two.
3rd party firewalls might block, but the best way to test is to run either "netmon" or "wireshark" and look at network traces while reproducing the issue. You will almost certainly get an idea of what's happening.
Restart both netlogon and DNS services using the start and stop commands via command line (even from services console should work).
2. If you are having an Active Directory Integrated DNS zone, check replication between the2 DNS/DC servers.
Checking dynamic updates.
3. If you are not using ADI zones, check port TCP53 (transfers) and UDP53 (name updates)
Please check your DNS secure update and as well as Firewall option, beacuse it also block connections.
Possibly DNS wont register the local computer srv records of its own where it is running.
Well I find this is a Very good Question.
And the answer is:
This behavior occurs when the following conditions exist:
The DNS server is configured as a Dynamic Host Configuration Protocol (DHCP) client.
The DNS zone has a name other than your Active Directory domain name.
The zone is not enabled to allow dynamic updates.
--------------------------------------------------------------------------------------------
To resolve this issue, verify that all of the following conditions exist:
Configure your DNS server to use a static Internet Protocol (IP) address.
Create a forward lookup zone named after your Active Directory.
Enable your domain zone to allow dynamic updates.
NOTE: If all of these conditions exist and you still do not see your SRV records, stop and start the Netlogon service. This action forces the domain controller to re-register the appropriate SRV records.
Using the DCdiag /fix command on the domain controller will verify that all SRV records that are in the Netlogon.dns file are registered on the primary DNS server.
Also i think you should restart the Netlogn service
i thisk its windows firewall . turnoff firewall
Registration of SRV records may not work if the following conditions exist:
Accroding to me only two possiblity1. might be make mistaks in creating record during AD configuration or simply restart requierd.
This possiblity for intranet network not internet..
Registration of SRV records may not work if the following conditions exist:
May be you not enter corrent DNS Address or Netbios name.
I think its Windows Firewall . need to turnoff it or except DNS Services