Non Domain Client Records

Hi. I have the following environment: single domain, Server 2003/2008 active
directory, unsecured dynamic updates, with 120 users, 3 sites with 1 DC in
each. How can I get non domain clients to register forward and reverse lookup
records via DHCP in DNS? At this point, the Reverse (pointer) registers the
FQDN, but no forward record registers. Tia
Dave

"SF Dave" <> wrote in message
news:FCA0C8F2-EAAF-4A99-BE43-...
> Hi. I have the following environment: single domain, Server 2003/2008
> active
> directory, unsecured dynamic updates, with 120 users, 3 sites with 1 DC in
> each. How can I get non domain clients to register forward and reverse
> lookup
> records via DHCP in DNS? At this point, the Reverse (pointer) registers
> the
> FQDN, but no forward record registers. Tia
> Dave


All you have to do is go into DHCP server's properties, and check the radio
button to Register all clients, whether they can or not.

In addition, I would suggest to configure credentials to use for DHCP so it
can update records it has registered, otherwise it can't. I also suggest to
configure scavenging to clean up old, stale records. Read my blog in the
following link for more information,how to do it, and why.

DHCP, Dynamic DNS Updates, Scavenging, static entries & timestamps, and the
DnsProxyUpdate Group (How to remove duplicate DNS host records)
http://msmvps.com/blogs/acefekay/arc...ate-group.aspx


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

Try this setting:

Unchecking "Register this connection's addresses in DNS" in the DNS tab of
Advanced TCP/IP settings makes things go a lot faster
for computers not joined to the domain.

That setting makes dhcp do all of the registrations instead of the client.
Make sure that you are using option 15 in DHCP.

Rui

"SF Dave" <> wrote in message
news:FCA0C8F2-EAAF-4A99-BE43-...
> Hi. I have the following environment: single domain, Server 2003/2008
> active
> directory, unsecured dynamic updates, with 120 users, 3 sites with 1 DC in
> each. How can I get non domain clients to register forward and reverse
> lookup
> records via DHCP in DNS? At this point, the Reverse (pointer) registers
> the
> FQDN, but no forward record registers. Tia
> Dave

Thanks for the tips!
Dave

"J de Boyne Pollard" wrote:

> SD> Hi. I have the following environment: single domain, Server
> SD> 2003/2008 active directory, unsecured dynamic updates,
> SD> with 120 users, 3 sites with 1 DC in each.
>
> As others have said, the most sensible configuration, especially in an
> environment such as you imply yours is where you have arbitrary
> personal machines being attached to the LAN, is to have one's DHCP
> server, and *only* one's DHCP server, perform the Dynamic DNS
> updates. So make your dynamic updates secure, and perform the
> necessary incantations with ACLs and user accounts to ensure that only
> your DHCP server gets to modify your DNS database. For best results,
> ensure that none of the DHCP clients can hi-jack the names used by
> your server machines. (There's a mechanism in the most recent DHCP
> server for preventing this. But a simpler approach that works on a
> wide range of platforms is to use subdomains to separate the
> namespaces.)
> .
>