Re: DNS Server settings HELP!!!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Herb Martin (news_at_LearnQuick.com)
Date: 01/19/05 

Date: Wed, 19 Jan 2005 13:24:35 -0600

"Invictus" <someone@microsoft.com> wrote in message
news:OoxIJfl$EHA.3424@TK2MSFTNGP11.phx.gbl...
> I've got 2 DC's DC1& DC2
>
> I currently have on DC1, the pri DNS pointing to DC2 and secondary
pointing
> to itself.

IF anything that is backwards (or just point each at itself.)

The key is you are trying to ensure that they BOTH REGISTER
which can only happen physically at the primary.

In theory, a registration of a client using a seconary will
be referred to the Primary but by pointing them both there
you eliminate any doubt -- after everything is fully replicated
and working correctly pointing each at itself and as alternate
to the other DNS server works just fine.

> On DC2, the pri DNS is DC1 and secondary is itself. I can get

The terms are actually Preffered and Alternate -- using these
terms prevent confusion between which DNS Server is the
Primary for the zone and which is Secondary (for the zone)

> to all internet sites except 1. What's wrong? FYI...I can access the
> "unreachable" site if I change the DNS entries on the workstation to point
> directly to the NS of my web host.

The problem is NOT where the DC-DNS are themselves
pointing but rather that they cannot either recurse the Internet
physically or (BETTER) forward to a DNS server which
can resolve on the Internet.

Set the FORWARDER on both DNS servers to your Web-DNS
server, or to your ISP (many people set these to a caching only
DNS server on their firewall whether this is a web server or
not.)

Relevant Pages

  • Re: Slow logon because of "Applying computer settings..."
    ... Check if the client is pointing to the correct DNS server, GPO settings, maybe some GPO is tring to apply some software or running some script, search for event errrors, logon scripts.... ... It seems to be related to computer policies but I can't figure out ... Many people are pointing to DNS to be the problem but I've checked it ... Clients are using DHCP and their local DC as DNS server ...
    (microsoft.public.windows.server.active_directory)
  • Re: Operations Masters
    ... My point was to force a valid and updated DNS server, by pointing all to the ... configuration to DC1, then clear local cache DNS cache, etc... ... If this DC won't be back working again, you may transfer fsmo roles ...
    (microsoft.public.windows.server.active_directory)
  • RE: joining domain
    ... The client that is trying to join is probably not pointing to the correct DNS server ... ID: 237675 Setting Up the Domain Name System for Active Directory WGID:325 ... Microsoft Windows Networking ...
    (microsoft.public.win2000.networking)
  • Re: Preferred DNS now needs to be configured on every client!!!
    ... the the DNS settings to each client through DHCP ... (pointing the client to the intended DNS server)? ... DNS server is configured or not. ...
    (microsoft.public.windows.server.dns)
  • Re: PCs of domain slower than when they where in workgroup
    ... DNS server, that might be the problem if anything is pointing to an ISP's ... > users have problems because the conection to this PC is slower. ... PC is into the old workgroup. ...
    (microsoft.public.windows.server.active_directory)