none
Recreating AD DNS records on server 2008 R2

    Question

  • Hi,

    How can I recreated active directory records in server 2008.

    All srv records are missing. Thus computer cannot join domain and other weird stuff is happening.

    I tried recreating zones and reinstalling dns. Also I tried running dcdiag /fix and ipconfig /registerdns.

    I searched internet couldn't find anything, that works.

    Can anyone help me???

     

    Thanks

    Thursday, November 25, 2010 7:12 PM

Answers

  • I have also seen this issue where DNS records were not published because the NIC on the DC had the "Register this connection's addresses in DNS" checkbox cleared. 
    Alexei
    • Marked as answer by FirefoxPL Saturday, November 27, 2010 3:20 PM
    Thursday, November 25, 2010 10:59 PM

All replies

  • Make sure that the DC points to the DNS server hosting AD integrated zone.

    Restart Netlogon service

    hth
    Marcin

    Thursday, November 25, 2010 7:20 PM
  • To add: You can use nltest /dsregdns command to register the SRV records.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Thursday, November 25, 2010 8:23 PM
  • I have also seen this issue where DNS records were not published because the NIC on the DC had the "Register this connection's addresses in DNS" checkbox cleared. 
    Alexei
    • Marked as answer by FirefoxPL Saturday, November 27, 2010 3:20 PM
    Thursday, November 25, 2010 10:59 PM
  • Hello,

    please stick to your other thread:

    http://social.technet.microsoft.com/Forums/en/winservergen/thread/d392c907-623e-47c5-aaa8-5889a0563243


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Friday, November 26, 2010 7:20 AM
  • How many DCs do you have?  Please post the IPCONFIG/ALL from your DC.  Did you try to restart the Netlogon service on the DC?


    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX

    Blogs - http://blogs.sivarajan.com/
    Articles - http://www.sivarajan.com/publications.html
    Twitter: @santhosh_sivara - http://twitter.com/santhosh_sivara

    This posting is provided AS IS with no warranties, and confers no rights.
    Saturday, November 27, 2010 2:15 AM
    Moderator
  • Yes, that was part of the problem.
    Saturday, November 27, 2010 3:21 PM
  • The other thread was accidental, technet site didn't showed that thread was created
    Saturday, November 27, 2010 3:22 PM
  • I have also seen this issue where DNS records were not published because the NIC on the DC had the "Register this connection's addresses in DNS" checkbox cleared. 
    Alexei

    This Fixed Everything for me!

    After Verifying that the NIC on the DC had the "Register this connection's addresses in DNS" setting enabled, 

    I ran DcDiag /fix and it worked

    Thank you!


    • Proposed as answer by Andrea Papotti Thursday, November 14, 2013 8:29 PM
    Friday, April 12, 2013 8:17 PM
  • The registry setting HKLM/SYSTEM/SERVICES/DNS/PARAMETERS/PublishAddress <ip address>, is extremely helpful when the server is a VPN server also. When you are using the server as a VPN server, every VPN connection gets recorded in the DNS as the server's address. With this registry key in place, the server only lists the one address.

    The deleting the registry key did not fix the problem for me. My issue was caused by me listing the dns server's address as 127.0.0.1 instead of the server's assigned address. Once I changed the adapter's dns address my problem went away.

    Monday, April 29, 2013 8:41 PM
  • THAKS YOU!!! IT WORK!

    Thursday, November 14, 2013 8:29 PM
  • JGEProgrammer; When I added a new DC to my network, it completely corrupted my DNS.  I went through all the steps I could find online, and I will tell you, that I was about to delete AD, and start from scratch when I found your 127.0.0.1 resolution.  I just wanted to say thank you as I spent the last few hours on this and it was something so simple.  My steps laid out below.

    I was getting complete replication failure events in my forest.  Nothing would replicate.

    1. Made sure DNS was pointed at my server IP, and not 127.0.0.1 (Localhost)
    2. Followed the instructions here to delete forest zones from AD: http://cbfive.com/are-your-dns-application-partitions-corrupt/
    3. Restarted Netlogon service
    4. Manually recreated the zones _msdcs.<forestname> and <forestname>
    5. followed steps here to reset netlogon, and flushdns and register DNS: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_27325754.html
    • Proposed as answer by Muong Tuesday, November 28, 2017 9:52 AM
    Saturday, February 28, 2015 1:27 AM
  • Well, that's what was causing my issues. That's what I get for taking 2 weeks off and having someone else manage the servers.
    Friday, April 28, 2017 7:04 PM