Question

Locked

Redundant Domain Controllers and DNS settings

By huskaluva ·
Have redundant DC's and was curious of the correct DNS settings. I have searched and possibly overlooked but have not found proper settings.

Servers config'd at AD, DNS and both are global catalog.

DC1:
Primary DNS address: DC1
Secondary: DC2

DC2:
Primary DNS: DC1
Secondary: DC2

client machines:
Primary DNS: DC1
Secondary: DC2

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

correct DNS setting is the DNS server that is authoritative for the zone

by CG IT In reply to Redundant Domain Controll ...

.

please restate the question to include whether the domain controllers are also DNS servers.

Domain controllers do not have to be DNS servers. DNS servers can provide name resolution to multiple domains, therefore to point a domain controller to the correct DNS server, you need to point it to the DNS server that is authoritative for the DNS zone of the domain.

Collapse -

Restated

by huskaluva In reply to correct DNS setting is th ...

yes, both servers are DNS servers too

Collapse -

for " redundancy" key word redundancy, if your DC/DNS server 1 goes down

by CG IT In reply to Redundant Domain Controll ...

you want hosts to look for DC/DNS server 2.

DC 1 and DC2 should keep Active Directory up to date with each other because they are peers,with each other. Domain controllers for the same domain in the same forest.

Redundancy for Domain Name Servers requires each domain name server to share DNS updates of the zone for the domain with each other. DNS zone updates should be Active Directory intergrated.

As far as what DNS servers you should list on the network card of each of the DC/DNS servers, I'll ask the question, what do you think it should be based upon what DNS does ?

Collapse -

thoughts on question

by huskaluva In reply to for " redundancy" key wor ...

based upon DNS and AD-integrated (both servers) then

DC1:
DNS - DC1

DC2:
DNS - DC2

no alternate DNS on the servers

-- or --

DC1:
DNS: DC1
DNS: DC2

DC2:
DNS: DC2
DNS: DC1

clients:
DC1
DC2
(in the event server 1 fails)

Collapse -

well why would a domain controller that also is a DNS server

by CG IT In reply to thoughts on question

edited: need to send queries it can't resolve to another DNS server that has the same DNS zone, for resolution?

Collapse -

then must be stuck on this "redundancy" word

by huskaluva In reply to well why would a domain c ...

niether then needs to point but just to itself

Collapse -

redundancy in IT means if one "resource"isn't available

by CG IT In reply to then must be stuck on thi ...

then there is another exact same resource that is.

How these devices share information with each other to ensure that they have the exact same "information, in the case of DNS servers and Domain Controllers, is how a DNS or Domain Controllers works.

The network card simply provides network connectivity to other hosts [servers or workstations] on the local network, access to the default gateway out of the network, and where to send name to address queries.

So to determine how to configure the network card DNS settings on a DNS server/domain controller really boils down to understanding how queries a DNS server can not resolve are sent out of the local network to other servers on another network for resolution.

Note: in most cases, an Active Directory based DNS server only knows about resources of the domain it belongs to and resources on the local network.

another note/question: how does the default gateway know where to send traffic that is sent to it by a DNS server, such as an unresolved DNS query?

Back to Software Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums