DNS and DHCP in different domains

[Matt Hartel]

We are running two parallel domains at once, as a part of
a email migration and are experiencing DNS issues with
workstations in the new domain. They are not updating
their A records in the new domain (DOMAIN2). I believe
that this is because I am currently using a DHCP server to
hand out addresses that exists in the old domain
(DOMAIN1). This DHCP server uses the new DNS servers when
handing out the address. I know that DNS and DHCP for the
domain should be hosted on the same server (in the same
domain too), but I am looking for a temporary way around
it.

DOMAIN1 (old domain) has an external trust with DOMAIN2
(new domain) that is not transitive. The DNS on both
domains are Active Directory integrated.

The basic problem is, when my workstations go to update
their A record, they dynamically send the update request
to the new DNS servers, which refuse the request, I'm
assuming because they were not issued a DNS entry to begin
with??? This is causing considerable problems with AD
(being so DNS dependent)

The error log shows: Source DNSAPI and Event ID 11153
errors on the workstations. Description: The system
failed to register network adapter with settings....

Any Suggestions?

 

[Kevin D. Goodknecht Sr. [MVP]]

In

We are running two parallel domains at once, as a part of
a email migration and are experiencing DNS issues with
workstations in the new domain. They are not updating
their A records in the new domain (DOMAIN2). I believe
that this is because I am currently using a DHCP server to
hand out addresses that exists in the old domain
(DOMAIN1). This DHCP server uses the new DNS servers when
handing out the address. I know that DNS and DHCP for the
domain should be hosted on the same server (in the same
domain too), but I am looking for a temporary way around
it.

DOMAIN1 (old domain) has an external trust with DOMAIN2
(new domain) that is not transitive. The DNS on both
domains are Active Directory integrated.

The basic problem is, when my workstations go to update
their A record, they dynamically send the update request
to the new DNS servers, which refuse the request, I'm
assuming because they were not issued a DNS entry to begin
with??? This is causing considerable problems with AD
(being so DNS dependent)

The error log shows: Source DNSAPI and Event ID 11153
errors on the workstations. Description: The system
failed to register network adapter with settings....

Any Suggestions?

DHCP will register in the DNS servers listed in TCP/IP properties of the
machine DHCP is located on, it doesn't use the DNS servers in the scope.
This is stated on the DNS tab of the scope properties. "Updates are sent to
the DNS servers configured in TCP/IP properties for network connections
active at this server."