5 replies
by ananymouse Accepted solution
by churdoo Accepted solution
by ananymouse Accepted solution
by churdoo Accepted solution
DNS is one of the major differences between NT4 domains and Active Directory; Active Directory depends on AD-integrated DNS. period.
That's why your logons are so slow. With AD, the first method of resolution as your workstations are looking for a logon server is DNS, and only after DNS times out unsuccessfully, do the workstations resort to NETBIOS broadcasts to find the logon server. This is precisely the reason for your delays in processing client logons.
Ideally, your internal AD FQDN should not be the same as your public domain for email and www, i.e. mycompany.local for AD versus mycompany.com for your public domain (email, www, etc.). You do not register your DC as your public DNS host; it's only used internally. Your internal clients should look to your DC as their primary DNS, and your DC should have FORWARDS set up in its DNS server to query your ISP DNS resolvers for all external lookups. So you're really not hosting your public DNS, rather channeling internal DNS resolution through a single source (or multiple/redundant paths if you have a second DC). In reality, this actually makes DNS-related issues easier to manage.
Even if you made your internal AD FQDN the same as your public domain, it's not that big of a deal because with Domino, your internal clients don't use MX records to figure out email delivery, so the only extra step is that you have to add a manual A record for your www. Again, you do not register your internal DC as your public DNS host, so your AD-integrated DNS server is used solely for internal name resolution and active-directory lookups.
Hope this helps.
--C
by ananymouse Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending