Re: DDNS Issues

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: James Madden (James.Madden_at_kmcnetwork.org)
Date: 02/08/05 

Date: Mon, 7 Feb 2005 22:26:19 -0500

The DHCP server does have the domain name specified under (Computer / Properties / Computer Name / etc..). The client however receives it's domain name from the dhcp server.

I can get DDNS to work if I manually configure each client, however that doesn't seem so dynamic to me.

I have read that DHCP and DDNS is different with 2000 / XP clients in that the clients themselves can register directly with DNS instead of the DHCP server registering the name with DNS. This is supposed to be a security enhancement. I totally understand how that can increase security, however until I'm on AD, this doesn't seem realistic. I want to try to avoid making changes manually (or by login script) on these 5000+ clients. The changes can be controled easily via GPO once I've migrated to AD.

What I need is to be able to make the Microsoft DHCP react like other DHCP servers that support DDNS. If I configure the dhcpproxy to point to my older Cisco Network Register DHCP server, the name is correctly registered with the MS DNS. Based on documentation from MS, the settings I have made should make the DHCP server register both A records and PTR records.

Thanks for your assistance!!!

James

>>> Herb Martin<news@LearnQuick.com> 2/7/05 7:33:12 PM >>>
> Windows XP Clients boot and receive the correct settings from the dhcp
server. However DDNS is not working correctly. The reverse dns entry is
updated with "CLIENTNAME." instead of "CLIENTNAME.DOMAIN.COM". As a result,
the forward zone is not updated since it looks like the DHCP server did not
send the dns suffix over to DNS.

DHCP server scope must include the DNS name and the
client really should have this set in the System Control
panel (where you join a domain or specify the client zone).

It can also be set on the Client NICs individually but the
primary place on the Clients is in the System properties.

Relevant Pages

  • Re: Always dynamically update DNS A and PTR records
    ... its name that the DHCP server gave during the lease which is Domain.local. ... The DHCP server always registers and updates client information with its ... its configured DNS servers, follow these steps: ... updates according to the settings below check box, ...
    (microsoft.public.windows.server.dns)
  • RE: DHCP - DNS Automatic update
    ... qualified domain name) allows a client to request that the DHCP server ... perform DNS name registration on behalf of the client. ... 2000-based DHCP server is configured to use the Update DNS only if DHCP ...
    (microsoft.public.windows.server.general)
  • Re: Update 2003 DNS with non-domain member clients
    ... I noticed there wasn't a subnet created in AD where the non-domain members PC ... Where SHOULD I see the update if the client isn't part of ... I have the DHCP handing out the DNS suffix to non-domain members ... Changed my DHCP server to 'Always dynamically update DNS A and PTR ...
    (microsoft.public.windows.server.dns)
  • Re: Failure Audit Event
    ... Machine tried to update its own DNS PTR record. ... correct the settings in DNS configuration on ... the machine and in the DNS & DHCP server settings, ... > Client Domain: FANTASYPRINTS ...
    (microsoft.public.win2000.security)
  • Re: Clients cannot find sharepoint
    ... The client machines had an entry in the append DNS ... Get ipconfig/all result on SBS and client computer. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)