Browsing Microsoft Websites on a Server 2003 Domain Controller
In news:uhFHZvyuDHA.1596@TK2MSFTNGP10.phx.gbl,
News Group <news.paradoxa@btopenworld.com> posted their thoughts, then I
offered mine
Well, well, well, that is a classic issue with AD if you WANT to use your
router as a DNS address. You are SURELY guaranteeing numerous errors if you
do so. My paycheck is on that one. Reason is AD stores all of it's resource
locations in DNS as SRV (service locator records). If you enlist an external
DNS server (such as an ISP's or your router) you will create numerous
problems because services, DCs, clients, etc, when the want to perform a
directory service function, maybe such as something as simple as loggin in,
it asks DNS where is the DC for my domain, and it fetches that from the
SRVs. If it were to ask the router, can it provide that information?
The recommedation is:
1. Point ALL internal machines to your internal DNS ONLY.
2. Set a forwarder on your internal DNS (in properties, Forwarding tab) to
forward to the ISP. Don't use the router here, otherwise you're introducing
an extra hop, which is a waste).
Make sense?
If you read back thru the many postings in the DNS and AD group, you will
find your configuration is a common configuration error and is problematic
and the responses are pretty much cookie cutters like I posted in how to fix
it. The other groups you posted to wouldn't be able to help out with this
issue.
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================
|