"noobtech" <(E-Mail Removed)> wrote in message
news:227EFCD5-5E88-4731-9A29-(E-Mail Removed)...
> Okay, I got it now based on your explanation from the above. I was reading
some book and I could have sworn that they said the Preferred DNS was the
actual server IP. Maybe I miss read it when it said back to itself.
You could also use the regular IP of the machine, but it is safer to use
127.0.0.1 because that will always be there even if the Nic or the patch
cable has a failure. Active Directory Requires DNS to run and if during
bootup (or anytime) Active Directory can't find the DNS there is trouble,
having it access DNS by the loopback is more dependable.
> In the above You have the DNS + DC on one machine, what would the
configuration be like if the DNS was on a member server and the DC was just
the DC? Can you show me what the DC configuration would be like? I assume
the DNS configuration stays the same.
Active Directory isn't my specialty, I focus on Topology, Routing, and
Firewalls/Proxys, but to my knowledge it will always be on the DC. Active
Directory (the Domain) requires DNS to run, therefore DSN will always be on
the DC and all clients, in order to participate in Active Directory must use
the DNS that Active Directory is tied to. Even if there is DNS running on
something else, there will still be the primary one on the DC(s).
> Do you know of any good through + easy to read books about windows DNS?
I don't know of any books, this link goes to a page with a series of other
links all devoted to the subject.
DNS Server Top Support Articles - Microsoft Service Providers
http://www.microsoft.com/serviceprov...upport/dns.asp
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com