General discussion

Locked

DNS/DHCP problems with AD domain

By mndthegap1 ·
I have a win2k domain with 2 servers. I have a DHCP scope set up from 10.1.3.20-10.1.3.255 the server is 10.1.3.4 DNS is setup w/ forward zone and reverse zone. The second server is setup as DC as second dns server, everything was copied over fine from the original DC. I have DHCP running on both w/ same scopes, and wins running on both and replicating fine. Here is the problem I can run a nslookup test from the original server 10.1.3.4 and everything is great. It will not work from the second server, both are listed as name server there are soa records, host records for both. BUT i can not create a pointer record in the reverse lookup zone cause its set to 10.1.0.1 says there is no reverse zone for it. In dhcp it wont let me create another zone for 10.1.0.20-10.1.0.255 it says it conflicts with an existing zone. SO how do I add the zone in dhcp so i can create a new forward/reverse zone in dns to add the pointer record.
nslookup error from 10.1.0.1 server -> if i run ls -d mycompany.com its says cant list domain query refused.
also when i just run nslookup it says request timed out unknown domain
sorry so long but i really could use help on this.

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by gregross In reply to DNS/DHCP problems with AD ...

Are both your servers pointing to themselves for DNS? I.E. your 10.1.3.4 server should only have 10.1.3.4 as its only dns server and the second dns server should be pointing to its own IP as well. Make sure you have allow automatic updates set to yes.

Is replication working between the two dcs?

Collapse -

by mndthegap1 In reply to DNS/DHCP problems with AD ...

Yes i have checked both servers Preferred DNS settings point only to themselves. and the Primary DNS server is set to accept dynamic updates. I looked on the DNS log in event viewer and it shows that its updating.

Collapse -

by voldar In reply to DNS/DHCP problems with AD ...

The request time out error is because on the second DNS server you have no reverse zone. Create one, and you should have no problems.

Collapse -

by voldar In reply to

Right click in the DNS window the domain name and choose and then Add Reverse Lookup zone or something like that. I don't remember, and I am not at the server right now, but it is there.
You can create either a AD integrated, primary, or secondary lookup zone.
About the DHCP, you can't setup two scopes with the IP range of the same subnet. I mean you should check your netmask for solving the problem.

For example:
- you can't set up one scope with:
192.168.1.1-155 (255.255.255.0)
and another one with:
192.168.1.156 - 254 (255.255.255.0)
because both are from 192.168.1.0/24

Back to Windows Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums