8 replies
by magetower
by andrewl
by drdon
In addition to the the answer in 1,also check the DNS server's address. In the TCPIP configuration for the clients, point to that DNS server IP address.
Next, be sure to authorize the update of the DNS by the client.
Any appenditures needed should be set there too.
Hope this helps
by andrewl
by riskyoz
I've spent some time doing the same things.
1-st let's agree on terminology.
There are AD domains, DNS domains, and DNS zones.
The order of steps I use is as follows.
-Set up dns server on member server.
-Put future needed DNS domains and zonesin place. Check it works. Make server authoritaive for all necessary zones. Check for dynamic updates
- Put this DNS server as primary on to-be AD controller. Run DCPROMO and setup AD domain
- Install W2K on remote comp., put it in parent domain. Put 1-st DNS as primary
- install 2nd DNS on the remote comp and delegate to it child DNS domain, check it as above
- Run DCPromo on to-be-child DC. It will register all records in corresponding zone
- Let replications and KCC run overnight in order to do all intgernal work.
- Check all trusts and event viewer on both DC. COrrect problems as needed
by riskyoz
P.S.It is obvious that all necessary forward and reverse DNS zones should be in place on both servers and replication of DNS zones should work. You can use nslookup utility to check how your DNS servers work.
- Make 2nd DNS forwarder to 1st so allunresolved requests would be forwarded upstream.
- You cannot replicate AD-integrated zones between parent and child domains. Use standard primary and secondary instead.
by andrewl
by andrewl
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending