Re: DDNS Issues

From: Herb Martin (news_at_LearnQuick.com)
Date: 02/08/05


Date: Mon, 7 Feb 2005 21:34:45 -0600


"James Madden" <James.Madden@kmcnetwork.org> wrote in message
news:#ede23YDFHA.1936@TK2MSFTNGP14.phx.gbl...
> 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.

IN THE SCOPE options, not so much the DHCP server itself.

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

Fix the scope.

> 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.

Yes, they can but so can DHCP if you just adjust the settings
on the scope (usually).

This will give the correct suffix to the clients AND fixup the
DDNS.

> 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!!!
>

-- 
Herb Martin
"James Madden" <James.Madden@kmcnetwork.org> wrote in message
news:#ede23YDFHA.1936@TK2MSFTNGP14.phx.gbl...
> 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: 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: Clients not registering in AD integrated DNS
    ... the DHCP server was set to do the registration (as mentioned in my ... clients in DNS: ... The 1st of those ("Register this connection's addresses in DNS") should be ... on the client had no effect at all. ...
    (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: Client not registering DNS
    ... We use a VPN for traveling users. ... IP get's registered in our DNS. ... If it is a DHCP server, what OS is the DHCP server. ... This setting is designed for computers that register A resource records in ...
    (microsoft.public.windows.server.dns)
  • Re: Clients not registering in AD integrated DNS
    ... the DHCP server was set to do the registration (as mentioned in my ... clients in DNS: ... The 1st of those ("Register this connection's addresses in DNS") should be ...
    (microsoft.public.windows.server.dns)