Re: DHCP, DNS, DDNS Question

You set the behavior of the DHCP server in the DNS tab of the scope
properties. If the clients are not members of the domain you can run into
problems with ownership of the DNS records. You need to make the DHCP server
a member of the DnsUpdateProxy group in AD to ensure that the DHCP server
itself does not become the owner of the DNS record it has registered on
behalf of a client.

Richard Perry wrote:
I thought that might be the case. So then my next question is this. If
setting up the DHCP server to manage both A and PTR records is
possible (and likely the only to accomplish what I am looking for
during this time), why would I NOT want to enable this for now?

It isn't quite as simple as that. This is essentially a security
issue. If the clients are AD members they will probably be regarded
as sufficiently reliable to register their own information. I think
that the default settings only allow domain members to update their
own records.

You can set things up so that DHCP can register both A and PTR
records for clients but it won't happen by default.

Richard Perry wrote:
I am in the middle of a Novell to Windows migration. As part of this
process, I installed AD on Win 2003, and configured DNS at that
time. I just did a typical DNS configuration.

Additionally, I set up DHCP and configured the scopes. For the most
part, I left all the default settings. I also configured WINS at the
same time.

It is my understanding that as client (WinXP) start to take
addresses from DHCP, the DNS name of that system should be
registered in DNS. However, I am not finding these A records or PTR
records listed at all.

The only exception is when I actually join the system to the domain,
then the system is registered with A and PTR records.

All systems are registering with WINS which is allowing me to ping
%computername% and get a response. However, I would like to have DNS
hold A records for the systems (as I assume that this is actually
the preferred configuration).

Am I doing something wrong, or is my understanding of how DDNS
should work faulty?

---
Richard Perry
Systems Administrator/Programmer
Shadow Mountain Ministries
San Diego Christian College
Southern California Seminary
Christian Unified Schools of San Diego


.

Relevant Pages

  • Re: Domain authentication problem
    ... configuration of Dynamic DNS, hence updates now enabled. ... restarting DHCP server restores this as default after I ... modern Windows versions where clients can register their own IP ...
    (microsoft.public.windows.server.networking)
  • Re: Multiple PTR records wont go away in the reverse zone.
    ... What about the DHCP setting "Dynamically update DNS A and PTR records only ... if requested", so clients will specify. ... I do agree with all your DHCP server recommendations (especially entering ... there is no other reason for a client to register in DNS when off ...
    (microsoft.public.windows.server.dns)
  • Re: Multiple PTR records wont go away in the reverse zone.
    ... When scavenging was implemented a few months ago, ... to the DHCP server to clear DNS A and PTR records, ... What we're afraid of is having server DNS entries deleted again. ... if requested", so clients will specify. ...
    (microsoft.public.windows.server.dns)
  • RE: DHCP Server does not update DNS
    ... take a look at the "Register PTR Records" section in the following KB article ... New Group Policies for DNS in Windows Server 2003 WGID:358 ... >the DHCP server by registering RR of its clients. ...
    (microsoft.public.windows.server.networking)
  • Re: Unauthenticated DNS clients
    ... > None of the clients are members of the domain. ... > all clients are authenticating through Netware. ... > register their IP addresses. ... Registers this connection's addresses in DNS must be selected and ...
    (microsoft.public.win2000.dns)
Loading