Re: Clients not registering in AD integrated DNS

Let's try this again...

See my comments embedded below.

--
John S

It's an OS, not a religion.


"Herb Martin" wrote:


"JohnS" <NNTPAlias@xxxxxxxxxxxxx> wrote in message
news:7D3DFE24-04D8-4F19-8C57-06E86EE58F66@xxxxxxxxxxxxxxxx
I have an issue where new clients, upon joining the domain, are not
registering in DNS. Further, they do not register in DNS at any point
thereafter.

DNS Clients must use STRICTLY the set of (internal) DNS servers which
can find the DNS servers for their own Domain AND ALL other domains
internally and externall.

The most common error is to mix DNS Servers (sets) on the DNS client
NIC->IP properties -- i.e, putting DNS servers in there which cannot
find everything the clients will ever need.

DNS Clients believe that EVERY DNS server will return the same and
the correct answers.


The DNS servers known to the client are technically not mixed, they just
aren't part of sub1.domB.com. The are both part of domA.com.

My environment consists of 2 separate AD forests/domains (domA.com and
sub1.domB.com), each having their own AD integrated DNS (Dynamic updates =
Secure only). The DNS servers for domA.com have a domain specific
Forwarder
record for sub1.domB.com.

There are also a number of other DNS zones hosted on BIND servers (e.g.
domB.com, sub2.domB.com, sub3.domB.com, etc). The DNS zones associated
with
domB.com represent a company that acquired the company that originally
owned
domA.com.

I am trying to add clients to sub1.domB.com and I would like for them to
register themselves in DNS in sub1.domB.com.

The DNS Server(s) these clients use must be either IN sub1.domB.com or able
to FIND sub1.domB.com. No exeptions.


The DNS servers in use by the client can consistently resolve sub1.domB.com
as well as all hostnames within sub1.domB.com.

Clients should also have their Primary DNS suffix set in the SYSTEM Control
Panel.


I should have specifically included this info before. Upon joining
sub1.domB.com, the Primary DNS suffix of this computer is successfully set.
In addition, Change primary DNS suffix when domain membership changes =
{checked}.

The clients are newly built XP SP2 with default TCP/IP properties:
Obtain an IP address automatically
Obtain DNS server address automatically
Append primary and connection specific DNS suffixes
Append parent suffixes of the primary DNS suffix = {unchecked}
DNS suffix for this connection = {blank}
Register this connection's addresses in DNS = {checked}
Use this connection's DNS suffix in DNS registration = {unchecked})

DHCP should also give out the correct DNS name for these clients if at
all possible.


I can't do this yet since the DHCP scope was not set up for and is not
specific to the destination domain.

The clients start out as workgroup machines. They obtain their TCP/IP
info
via a DHCP server that is a member of domA.com. The DHCP client service
is
running on the client.

When they switch to domain machines the Primary DNS suffix needs to be
added to them as part of this change.


Answered above.

On the DHCP server, the primary and secondary DNS servers are DNS servers
in
domA.com. Scope option 006 includes only DNS servers for domA.com. Scope
option 015 is set to domA.com. The DHCP server is also set to register
clients in DNS:
Automatically update DHCP client information in DNS = {checked}
Always update DNS
Discard forward (name-to-address) lookups when lease expires = {checked}
Enable updates for DNS clients that do not support dynamic update =
{checked}

The clients successfully join the sub1.domB.com AD domain using the fqdn.
However, they do not register in the sub1.domB.com DNS domain. Upon
reboot,
or upon using ipconfig /registerdns, they still do not register in the
sub1.domB.com DNS domain.

Can anyone explain why the DNS registration does not work?

--
John S

It's an OS, not a religion.



.

Relevant Pages

  • Re: Multiple hosts with same IP address
    ... Can we disable this option ""Register this connection's addresses in DNS" ... What I meant by the first part was that you can continue having the clients ... As an alternative you can use DHCP dynamic registration. ...
    (microsoft.public.windows.server.dns)
  • Re: Multiple PTR records wont go away in the reverse zone.
    ... What about the DHCP setting "Dynamically update DNS A and PTR records only ... if requested", so clients will specify. ... I do agree with all your DHCP server recommendations (especially entering ... there is no other reason for a client to register in DNS when off ...
    (microsoft.public.windows.server.dns)
  • Re: Multiple hosts with same IP address
    ... Can we disable this option ""Register this connection's addresses in DNS" ... What I meant by the first part was that you can continue having the clients ... As an alternative you can use DHCP dynamic registration. ...
    (microsoft.public.windows.server.dns)
  • Re: How to set up Clients with...
    ... The only place foreign DNS servers ... > the Clients need to have the SBS server as their primary DNS server.. ... >>> join any windows domain including an SBS domain. ...
    (microsoft.public.windows.server.sbs)
  • Re: Dynamic DNS, DNS Records & Scavenging
    ... We have an issue whereby we want external clients to register there ... There are two DHCP ... DNS however this doesn't seem to be the case. ... DNSUpdateProxy and when i did this i saw my test laptop register its ...
    (microsoft.public.windows.server.dns)