Windows 2000 DHCP - forcing DNS registration

  • Thread starter Thread starter ctvader
  • Start date Start date
C

ctvader

Guest
Is there a way to tell the Microsoft DHCP server to force DNS
registration? We have a Windows 2000 DHCP server that has the
computer with a pen icon next to all the addresses, which is telling
me that DDNS updates are pending. We have other DHCP servers that
register the clients fine. Is there a way to tell the DHCP server to
use a specific DNS server?

Thanks.
 
Re: Windows 2000 DHCP - forcing DNS registration

hello,

That may be a problem with the ownership of the dns entry. You may delete
one to check.

About which dns server uses the dhcp server:
http://technet2.microsoft.com/windo...c368-46c2-b017-caf25ae150ec1033.mspx?mfr=true

The DHCP server might be configured in one of the following ways:

The DHCP server registers and updates client information with the
authoritative DNS server of the zone in which the DHCP server is located
according to the DHCP client request.
This is the default configuration for DHCP servers running Windows Server
2003 and DHCP clients running Windows 2000, Windows XP, or a Windows Server
2003 operating system. In this mode, the DHCP client can request the way in
which the DHCP server performs updates of its host (A) and pointer (PTR)
resource records. If possible, the DHCP server accommodates the client
request for handling updates to its name and IP address information in DNS.

To modify this setting, select the Dynamically update DNS A and PTR records
only if requested by the DHCP clients check box, which is located in
Properties on the DNS tab on the applicable DHCP server or on one of its
scopes.


The DHCP server always registers and updates client information in DNS.

This is a modified configuration supported for DHCP servers running Windows
Server 2003 and DHCP clients running Windows 2000, Windows XP, or a Windows
Server 2003 operating system. In this mode, the DHCP server always performs
updates of the client's FQDN, leased IP address information, and both its
host (A) and pointer (PTR) resource records, regardless of whether the
client has requested to perform its own updates.

To modify this setting, select the Enable DNS dynamic updates according to
the settings below check box and click Always dynamically update DNS A and
PTR records, which is located in Properties on the DNS tab on the applicable
DHCP server or on one of its scopes.

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"ctvader" <jeff.swift@gmail.com> wrote in message
news:1187884254.259782.158770@e9g2000prf.googlegroups.com...
> Is there a way to tell the Microsoft DHCP server to force DNS
> registration? We have a Windows 2000 DHCP server that has the
> computer with a pen icon next to all the addresses, which is telling
> me that DDNS updates are pending. We have other DHCP servers that
> register the clients fine. Is there a way to tell the DHCP server to
> use a specific DNS server?
>
> Thanks.
>
 
Re: Windows 2000 DHCP - forcing DNS registration

Thanks Mathieu.

I'll have to test if its the ownership of the DNS record. What
puzzles me is why are the other DHCP servers I have registering the
clients fine. Thanks for the help and the link.

Jeff
 
Re: Windows 2000 DHCP - forcing DNS registration

Is it the same workstation that is registered successduly on a dhcp server
and not on another ?


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"ctvader" <jeff.swift@gmail.com> wrote in message
news:1187890036.286823.90950@q4g2000prc.googlegroups.com...
> Thanks Mathieu.
>
> I'll have to test if its the ownership of the DNS record. What
> puzzles me is why are the other DHCP servers I have registering the
> clients fine. Thanks for the help and the link.
>
> Jeff
>
>
 
Re: Windows 2000 DHCP - forcing DNS registration

This is a legacy DHCP server (Windows 2000 SP4) that has been around
for years and serves 5 subnets of our network (the other DHCP servers
are in other buildings/sites) so all clients that are pointing to it
are being affected. The other DHCP Servers (mix of W2K and W2K3) do
not experience the same problem. We're going against a Linux DNS
server (BIND) but we know thats not the problem.
 
Re: Windows 2000 DHCP - forcing DNS registration

So you don't know if a workstation getting dhcp from it would get dns
registered correctly if using another dhcp ?

If you have only 2000/XP, as written in the webpage of my previous post,
dhcp client can register themselves DNS IN A. The dhcp only register the
PTR.
That would be a more simple config

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"ctvader" <jeff.swift@gmail.com> wrote in message
news:1187891364.653932.229120@x40g2000prg.googlegroups.com...
> This is a legacy DHCP server (Windows 2000 SP4) that has been around
> for years and serves 5 subnets of our network (the other DHCP servers
> are in other buildings/sites) so all clients that are pointing to it
> are being affected. The other DHCP Servers (mix of W2K and W2K3) do
> not experience the same problem. We're going against a Linux DNS
> server (BIND) but we know thats not the problem.
>
 
Back
Top