Installed AD then DNS, now have problems

[mjgsxr750]

A customer installed Active Directory and then DNS server. None of the required AD server records are in DNS. This causes some XP Pro workstation not to find the domain controller. Tried ipconfig /registerdns - nothing. Tried netdiag /fix - nothing. Made sure Dynamic updates were enabled. How do I get the necessary AD records in DNS so W2K and XP Pro workstations will find a controller?

Thanks,
Mike

 

[dmandell]

If your environment is fairly simple, you can add all of the RR records manually.

Here is a good MS article that may help you to fix the issue. MS 260371

http://support.microsoft.com/default.aspx?scid=kb;en-us;260371

Good luck,
Dana

 

[mjgsxr750]

Is there a document on how to do this? Do I just need to add the entries in the netlogon.dns file? How do I create the folder structure? I don't see the option to create a folder such as _msdsc .....

Thanks in advance!
Mike

 

[dmandell]

Did you create the forward and reverse lookup zones first and then try to "Repair the Active Directory DNS record registration" according to the instructions?

BTW, are you running AD integrated DNS or "Standard Primary"?

If you are running "Standard Primary" you can edit the "domainname".dns file but it's a lot of work, and prone to typos.

 

[mjgsxr750]

Yes I created the Forward and Reverse lookup zones. I tried the Netdiag /Fix and the ipconfig /registerdns then restarted the Netlogon Service and nothing seemed to add entries into DNS. I appears that the DNS server will not accept Dynamic Updates even though it is enabled. That is why I am wondering how to do it manually if possible. I am trying to run it in AD Integrated but that doesn't give me a way to import information from the netlogon.dns file.

If I create a new zone and reference the netlogon.dns file will that work? Or are there any other suggestions?

Thank you!
Mike

 

[dmandell]

Is it possible that the client set up this server as a "standalone DNS server"? and then made it a domain controller? If so, it would probably be fastest to take any other Domain controller, and make it a DNS server, you can always take DNS off of it later once you have the correct info in AD by creating the DNS server the right way.

If you can't do this, if you change your DNS server to a "standard Primary" you can then add the correct entries to your "domainname".DNS file. It's a pain in the ass, but it can be done.

I can give you some of the key items to add that could get you going if you want. Let me know,
Dana

 

[mjgsxr750]

I think that is what happened. It is a single server environment so adding another domain controller is not possible. Good thought though!

I think that is what I will have to do but I am not sure of the entried needed in the .dns file. Any assistance you can provide would be greatly appreciated! Could it be a simple as copying one from a different domain and making some IP and domain name related changes?

Thanks!
Mike

 

[dmandell]

There is a "sample" .dns file already on your DNS server in the sample directory. But having a "real world" example is much easier. I'll forward you some stuff it you like, although, in my book, it still would probably be faster and easier to find any old computer, (borrow one for a day if you need to) and build another domain controller, put DNS on it, integrate it with AD, and your problem is fixed. Then then take it off line, and go with the original.

Dana

 

[dmandell]

After you have changed to a "Standard Primary" DNS
add the following to the begining of you .dns file.

(Filling in all of the items that apply)
For "your_Domain.com" put in your domain name
For "your DNS_server" put in your DNS server
In youre this will be the same computer)

Oh, and make sure you have a backup before you start editing the DNS file.

This should be enough to get you started.
Dana


;
; Database file your_domain.com.dns for your_domain.com zone.
; Zone version: 1 (change this number to anything greater than your current version)
;

@ IN SOA your_DNS_Server.your_domain.com. admin_mail_address.your_domain.com. (
1 ; serial number
3600 ; refresh
1800 ; retry
864000 ; expire
43200 ; minimum TTL

;
; Zone NS records
;


@ NS Your_DNS_Server.your_domain.com.

;
; WINS lookup record
;

@ WINS LOCAL L2 C900 ( Wins Server IP address here with ( ) )

;
; Zone records
;

@ 600 A you_DC_IP_here
@ MX 10 your_mail_Server.your_domain.com.

_kerberos._tcp.your_site_name._sites.dc._msdcs 600 SRV 0 100 88 Your_DC_Name.your_domain.com.
600 SRV 0 100 88 Your_DC_Name.your_domain.com.
_ldap._tcp.your_site_name._sites.dc._msdcs 600 SRV 0 100 389 Your_DC_Name.your_domain.com.
_kerberos._tcp.dc._msdcs 600 SRV 0 100 88 Your_DC_Name.your_domain.com.
_ldap._tcp.dc._msdcs 600 SRV 0 100 389 Your_DC_Name.your_domain.com.

gc._msdcs 600 A 192.168.7.144
_ldap._tcp.your_site_name._sites.gc._msdcs 600 SRV 0 100 3268 Your_DC_Name.your_domain.com.
_ldap._tcp.gc._msdcs 600 SRV 0 100 3268 Your_DC_Name.your_domain.com.
_ldap._tcp.pdc._msdcs 600 SRV 0 100 389 Your_DC_Name.your_domain.com.

_gc._tcp.your_site_name._sites 600 SRV 0 100 3268 Your_DC_Name.your_domain.com.
_kerberos._tcp.your_site_name._sites 600 SRV 0 100 88 Your_DC_Name.your_domain.com.

_ldap._tcp.your_site_name._sites 600 SRV 0 100 389 Your_DC_Name.your_domain.com.


_gc._tcp 600 SRV 0 100 3268 Your_DC_Name.your_domain.com.
_kerberos._tcp 600 SRV 0 100 88 Your_DC_Name.your_domain.com.


_kpasswd._tcp 600 SRV 0 100 464 Your_DC_Name.your_domain.com.


_ldap._tcp 600 SRV 0 100 389 Your_DC_Name.your_domain.com.


_kerberos._udp 600 SRV 0 100 88 Your_DC_Name.your_domain.com.


_kpasswd._udp 600 SRV 0 100 464 Your_DC_Name.your_domain.com.

 

[dmandell]

opps! I made a mistake.
substitute "domain controller IP" for 192.168.7.144 in the following line.

gc._msdcs 600 A 192.168.7.144

Dana

 

[mjgsxr750]

I will give this a shot. I will let you know how it goes. Thanks a bunch!!

-Mike

 

[mjgsxr750]

Well, the DNS file didn't work for some reason. As far as the other option, how does the DNS info for AD get written to the original DNS server?

A=original server
B=temporary server

I understand that I would introduce another domain controller with B. Would I point then point it to the server A for DNS or put DNS on server B initially? If it is pointed to A and the DNS info for server B is in correct, how would that correct the problem with server A? Or would it create all the DNS info for the zone including server A and B so when you take server B offline, server A's info is correct within DNS?

thanks,
Mike

 

[dmandell]

Mike, I noticed the text I sent all got "word wrapped" for some reason. This could cause an issue. do you want me to just email you the file and try again?

 

[BobCobb]

dmandell,
I am having the same problems, could you please email the dns file to me also?
Thanks
b_kingston@yahoo.com.au