DNS + DHCP Dynamic Updates

[James Heathcote]

According to an article, DCs should not have themselves
configured as 1st DNS in their network interface IP
configuration but one central "virtual" DNS master, e.g.
xxx-DC-1.

If DHCP is installed on a DC with DNS server also, On
which DNS server is a DHCP server making its dynamic
updates? The server with DHCP and DNS installed, or the
central "virtual" dns master.

Kind Regards


James

 

[Kevin D. Goodknecht [MVP]]

In

According to an article, DCs should not have themselves
configured as 1st DNS in their network interface IP
configuration but one central "virtual" DNS master, e.g.
xxx-DC-1.

This applies to DCs beyond the first DC in a domain.

If DHCP is installed on a DC with DNS server also, On
which DNS server is a DHCP server making its dynamic
updates? The server with DHCP and DNS installed, or the
central "virtual" dns master.

On the DNS server(s) listed in its scope(s) that are authoritative for the
Domain name in option 015 and accept Dynamic updates.

 

[James Heathcote]

Thank you for your reply.

I am still a little unclear.

Basically:

Where does Microsoft DHCP register DNS Dynamic Updates

Is it the DNS server configured as the DHCP's server
Primary DNS server in the TCP/IP properties located in
Networking Properties

or

Is it the DNS server specified in the scope of the server
within DHCP.

Sorry for my confussion, but we are looking at setting up
a global domain with some 50 sites.

Regards


James

 

[Kevin D. Goodknecht [MVP]]

In

Thank you for your reply.

I am still a little unclear.

Basically:

Where does Microsoft DHCP register DNS Dynamic Updates

Is it the DNS server configured as the DHCP's server
Primary DNS server in the TCP/IP properties located in
Networking Properties

Clients that support DDNS will use the DNS server(s) defined in TCP/IP
properties. The posistion it is in is not relevant, if the DNS server
supports DDNS then the client will attempt to register. If the DNS server
does not support DDNS then the client will log a failure in the event log.
If you have your ISP's DNS in TCP/IP properties, which is an incorrect
configuration, then the client will try to register if possible in the
public domain zone for the name listed as Primary and Connection DNS suffix.
You should not use an external DNS server in clients' TCP/IP properties in
any posistion.

Is it the DNS server specified in the scope of the server
within DHCP.

If the client is also a DHCP client, DHCP will attempt to register for the
client, depending on how DHCP option 081 (the DNS tab in DHCP) is
configured, in the DNS server(s) listed in the scope and in the zone for the
zone name listed in option 015.