name resolution for non-domain remote computers

  • Thread starter Thread starter RJ
  • Start date Start date
R

RJ

I have 2 LANs connected by a WAN link. I have one
corporate AD domain and a DHCP server in each LAN in the
same domain. I have machines that are in their own
workgroups and other AD domains for development purposes.
All these machines use the same 2 DHCP servers for IP
addressing. They are all Win2k machines. They all have
the box "register this connection's address in DNS"
checked along with the other default DHCP settings. The
DNS Tab on both DHCP servers have the boxes "Automatically
update DHCP client information in DNS" and "Always update
DNS" checked.

All of the non domain member machines do not register
their host names in the DNS zone which is the DNS suffix
that is handed out the all DHCP clients.

I can resolve machines by name in the same local subnet
from domain member machines that receive their IP address
from the same DHCP server. I cannot resolve by name the
non domain member machines in the remote subnets.\

The problem is that the DNS zone information does not get
populated with the host name. Is that the way it is
supposed to work?

What is the answer to resolving names for non domain
members that use a remote DHCP server? This issue was
resolved by WINS in NT 4.0.

Thanks,
RJ
 
In
RJ said:
I have 2 LANs connected by a WAN link. I have one
corporate AD domain and a DHCP server in each LAN in the
same domain. I have machines that are in their own
workgroups and other AD domains for development purposes.
All these machines use the same 2 DHCP servers for IP
addressing. They are all Win2k machines. They all have
the box "register this connection's address in DNS"
checked along with the other default DHCP settings. The
DNS Tab on both DHCP servers have the boxes "Automatically
update DHCP client information in DNS" and "Always update
DNS" checked.

All of the non domain member machines do not register
their host names in the DNS zone which is the DNS suffix
that is handed out the all DHCP clients.

I can resolve machines by name in the same local subnet
from domain member machines that receive their IP address
from the same DHCP server. I cannot resolve by name the
non domain member machines in the remote subnets.\

The problem is that the DNS zone information does not get
populated with the host name. Is that the way it is
supposed to work?

What is the answer to resolving names for non domain
members that use a remote DHCP server? This issue was
resolved by WINS in NT 4.0.

Thanks,
RJ

Add the machine account that has DHCP on it to the DnsUpdateProxy group.
In ADUC click on the properties of the machine's account that is the DHCP
server, on the "Member of" tab click "Add" select DnsUpdateProxy Group.
Also the DHCP server will need option 015 DNS domain name.

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
http://www.lonestaramerica.com/
============================
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================
--
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================
 
-----Original Message-----
In

Add the machine account that has DHCP on it to the DnsUpdateProxy group.
In ADUC click on the properties of the machine's account that is the DHCP
server, on the "Member of" tab click "Add" select DnsUpdateProxy Group.
Also the DHCP server will need option 015 DNS domain name.

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
http://www.lonestaramerica.com/
============================
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================
--
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================

I had all the DNS settings and DHCP settings that you
mentioned on your post to my question below. I
accidentally posted this post twice. Anyway, I just added
both DHCP servers, (which are both domain controllers) to
the DnsUpdateProxy group.

1 Do I need to restart services to get this working?
2. Will the host names actually get populated in the dns
zone of the domain name of AD?

Thanks,
RJ
 
In
RJ said:
I had all the DNS settings and DHCP settings that you
mentioned on your post to my question below. I
accidentally posted this post twice. Anyway, I just added
both DHCP servers, (which are both domain controllers) to
the DnsUpdateProxy group.

1 Do I need to restart services to get this working?

No you should not have to
2. Will the host names actually get populated in the dns
zone of the domain name of AD?

Yes


--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
http://www.lonestaramerica.com/
============================
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================
--
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================
 
Also, if the zone is AD integrated, you may want to change the Allow Updates setting for the zone to Yes. By default AD integrated zones only allow secure
updates. Non members will not be able to register their addresses. If the DHCP server is a member of the domain, it should be able to handle this though.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
First of all, thanks for the replies from both of you.

I have done all the suggestions and the clients in the
other workgroups as well as other domains that use the
same DHCP server as the main AD domain are still not
being populated in the dns zone. Any event log messages
that I could check?

Thanks,
RJ
-----Original Message-----
Also, if the zone is AD integrated, you may want to
change the Allow Updates setting for the zone to Yes. By
default AD integrated zones only allow secure
updates. Non members will not be able to register their
addresses. If the DHCP server is a member of the domain,
it should be able to handle this though.
Thank you,
Mike Johnston
Microsoft Network Support
confers no rights. Use of included script samples are
subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all
responses to this message are best directed to the
newsgroup/thread from which they originated.
 
In
RJ said:
First of all, thanks for the replies from both of you.

I have done all the suggestions and the clients in the
other workgroups as well as other domains that use the
same DHCP server as the main AD domain are still not
being populated in the dns zone. Any event log messages
that I could check?
If your DHCP options are set up correctly with the DNS server and DNS domain
name this should work If this is an AD integrated zone check the permission
on the security page.
Post an ipconfig /all from the workgroup client
 
Back
Top