Shannon Roddy <[EMAIL PROTECTED]> writes: > On Apr 8, 2004, at 9:21 AM, James Kuhns wrote: >> >> >> After ActiveDirectory install on the 2K server I just blindly >> grabbed the netlogon.dns file the install generated and included it >> in my existing bind zone file for my local domain.? Was having >> problems with an XP machine: domain logon was taking like 3-5 mins >> and it would ?lose? the network after a while (would not be able to >> browse machines/shares on the network).? After a while I finally >> took a closer look at the netlogon.dns file and found some weird >> stuff: 1) the A record was 2Kmachine.mydomain.com (was giving me >> some weird results ? 2Kmachine.mydomain.com and >> 2Kmachine.mydomain.com.mydomain.com both resolved to 2Kmachine?s ip >> address), 2) all the SRV records had >> 2Kmachine.2Kmachine.mydomain.com (which doesn?t exist).? I changed >> the A record to be just 2Kmachine and that cleared up the weird >> resolve issue, I also changed all of the SRV records to be >> 2Kmachine.mydomain.com. >> > > I just had a go around with a version of bind 8. Seems to me that I > remember something about not having a trailing dot somewhere could > cause the mydomain.com.mydomain.com problem. I will have to look > later today in one of the books I used as a reference. I am also not > a bind expert and surprisingly our DNS server had been running fine > for >3 years without anything but the occasional security patch, > therefore my bind knowledge is not that great.
Yes, you need a trailing dot for the A records in the zone file. Here's a webpage that talks more about it: <URL:http://www.tech-recipes.com/modules.php?name=Recipes&rx_id=306>. Hope this helps, Kevin
