daveamour
asked on
Group Policy/DNS
I have a problem with Group policy not working and soemone suggested that I might have a DNS problem on my domain controller so here I am.
When I try nslookup using my DC it times out.
Can anyone help check if my dns is set up ok?
Thanks
Dave
When I try nslookup using my DC it times out.
Can anyone help check if my dns is set up ok?
Thanks
Dave
ASKER
Hi
1 server
I have a forward lookup zone but no reverse lookup zone
I dont use the server as the DNS. I have a router with DHCP and I use that. Tried useing the server as DNS but didn't work.
Dynamic updates, secure only, is enabled in the forward lookup zone.
I browse the web fine using the router as DNS. Using nslookup with the server timesout though.
1 server
I have a forward lookup zone but no reverse lookup zone
I dont use the server as the DNS. I have a router with DHCP and I use that. Tried useing the server as DNS but didn't work.
Dynamic updates, secure only, is enabled in the forward lookup zone.
I browse the web fine using the router as DNS. Using nslookup with the server timesout though.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
One update to the above. You can use another device or server as DNS, however there are requirements for Active Directory:
1. The DNS must support Service Records
2. The DNS should ideally support Dynamic Updates
It's possible to make it work with only 1, however, you'd have to manually add all the Service Records for the Domain (these are used to locate the Domain Controller for things like Kerberos authentication (logon servers), Directory updates and other services) - generally not fun so 2 becomes more of a requirement.
ASKER
Hi
I got a technical friend to have a look at this and he did some messing around and managed to get things working. Not sure what he did but I did do the ipconfig /registerdns prior to him having a look and then we did a reboot and everythings working. He said the ipconfig /registerdns probably was the key.
Thanks very much for your help.
Dave
I got a technical friend to have a look at this and he did some messing around and managed to get things working. Not sure what he did but I did do the ipconfig /registerdns prior to him having a look and then we did a reboot and everythings working. He said the ipconfig /registerdns probably was the key.
Thanks very much for your help.
Dave
Pleasure, glad it's working :)
Just a few basics first then...
Do you only have one Server?
If so...
In DNS Manager on your server do you have a Forward Lookup Zone for your domain?
In Revese Lookup Zones, do you have a zone for your IP Range?
In your IP Configuration (for both the Server and any PCs), do you use the Server as the Primary DNS?
In the properties for your Zone, is Dynamic Updates enabled and set to Secure Updates only?
Do you have any problems getting external address (for browsing the web and such)?