Re: Should DC's with DNS point to self first?

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

Hi Joe
First of all, let me say that the answer is based in common configuration, Gonzo didn't specify any specific configuration, so I think it's fair to give a common DNS configuration for a common scenario.

No it doesn't. In fact in some situations it absolutely should not.

IMO: Yes it does, if not why you should Run DNS on that server, if you don't plan to take advantage of DNS don't install it on the DC. If my DNS server is updated why should I query another one when I have everything I need locally? Of course when you introduce a new DC/DNS on the domain, during dcpromo you should use another updated DNS server in the primary DNS NIC configuration, but after everything is replicated you should point the server again to it self. There're other specific types of configuration that you can take advantage of querying other DNS server than locally, but again this is a common scenario not specific, or maybe I miss something in Gonzo's post.

I am really not sure where you came up with this. If you got it from MSFT docs, point me at them so I can get them removed/corrected.

LOL. I think I shouldn't even bother to respond this one obviously. I don't think so.

Pointing at another DC is not definitely a wrong configuration. It could be, but isn't necessarily. Depends on the DNS configuration.

According with general/normal configuration, IMO it is. So again: . If my DNS server is updated why should I query another one when I have everything I need locally?

It is possible the local records are wrong. Incorrect records are worse than no records because incorrect records do not cause a secondary lookup.

Agree, you should correct that, but after correction made, point the server to it self again.
--

I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE

"Joe Richards [MVP]" <humorexpress@xxxxxxxxxxx> wrote in message news:Oct%23wl2UHHA.3652@xxxxxxxxxxxxxxxxxxxxxxx
> The DC/DNS Always must point to itself in preferred DNS.

No it doesn't. In fact in some situations it absolutely should not.

> DCs weren't made to be rebooted

I am really not sure where you came up with this. If you got it from MSFT docs, point me at them so I can get them removed/corrected.


> I don't see ANY reason to do a wrong configuration just
> because you need a reboot from time to time.

Pointing at another DC is not definitely a wrong configuration. It could be, but isn't necessarily. Depends on the DNS configuration.


> Why should the DC look for DNS queries in
> another DNS when that DC has the DNS locally? No sense.

It is possible the local records are wrong. Incorrect records are worse than no records because incorrect records do not cause a secondary lookup.


joe


--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm


Jorge Silva wrote:
Hi
The DC/DNS Always must point to itself in preferred DNS. Place the secondary DNS server pointing to an existing one, so when the DC starts up, if the DNS service starts later then AD, the server can look for the secondary DNS.
BTW: DCs weren't made to be rebooted, however sometimes is needed, but I don't see ANY reason to do a wrong configuration just because you need a reboot from time to time. Why should the DC look for DNS queries in another DNS when that DC has the DNS locally? No sense.

.

Relevant Pages

  • Re: NTDS Inbound neighbos removal
    ... The DSA operation is unable to proceed because of a DNS lookup ... Gathering NetBT configuration information. ... Owner of the binding path: ... Upper Component: NWLink SPX/SPXII Protocol ...
    (microsoft.public.windows.server.active_directory)
  • Re: Should DCs with DNS point to self first?
    ... If you've problems then that's another situation, but the poster is asking for where should the DNS pointing to ... No. There's no reason to use other DNS server when you have all locally, by doing so IMO you're wasting server resources and network traffic just for fun ... It depends entirely on the configuration and DESIRES of the administrators. ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Configuration
    ... SRV3 also a Primary DNS server for ... I am not able to understand the configuration of DNS server did by ... xyz.abc.com has two domain controller and both has Primary Zone for ...
    (microsoft.public.windows.server.dns)
  • Re: DCDIAG DNS Failure
    ... I have looked at most of the articles you sited and I have configured DNS ... The DNS server lists only itself as the preferred server with no ... Best practices for DNS client settings in Windows 2000 Server and in Windows ... -Exchange configuration. ...
    (microsoft.public.windows.server.dns)
  • Re: setting up and configuring dns server on my windows 2000 box
    ... >don't we start with a brief description of your DNS ... Windows 2000 IP Configuration ... >where the DNS server is physically joined to). ... I just cannot seem to get things to resolve ...
    (microsoft.public.win2000.dns)