Solved

Remove DNS records in Domain B from DHCP Server in Domain A

Posted on 2010-08-25
3
608 Views
Last Modified: 2012-08-14
We are building virtual desktops for another organization that we have a two way domain level trust with. The desktops get their IP addresses from Domain A and then register their A records on DNS server in Domain B and join to the Domain B windows domain. This works very well.

However, when the desktop is destroyed (every time a log our or disconnection occurs) the DHCP server releases the IP address, based on a very short lease duration, builds a new desktop with the same name, then gets a new DHCP address with a different MAC address. However, the old machine name and IP address is never removed from Domain B's DNS servers so the new IP address is never registered and hense, the desktop cannot reach the domain resources it requires in Domain B.

If we manually delete the A records from the Domain B DNS server then the recreated machines will register themselves just fine. It's the re-registration that's killing me.

Is there any solution short of mucking with routing and trying to use the DHCP server in domain B? It would be nice if a script could be run at log out that would delete the A record. I've tried testing with the dnscmd /recorddelete command but cannot get it to successfully delete an A record even when it tells me it did.

Any script would have to be run with sufficient privileges to delete the record and it would have to know the IP address to make it happen.

Any ideas. I'm stumped.
0
Comment
Question by:hcca
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 28

Accepted Solution

by:
bgoering earned 500 total points
ID: 33527078
Have you considered dns scavanging for the dns server in domain B? Take a look at http://technet.microsoft.com/en-us/library/cc776907(WS.10).aspx and see if that would help your situation.

To go along with the scavenging set a short intervel for aging the record, and configure the clients to refresh frequently so they don't accidently get deleted. See http://support.microsoft.com/kb/816592 for how to manage the interval.

"By default, Windows XP and Windows Server 2003 reregister their A and PTR resource records every 24 hours regardless of the computer's role. To change this time, add the DefaultRegistrationRefreshInterval registry entry under the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TcpIp\Parameters
The interval is set in seconds. "

Another thing that might help is to configure scope option on dhcp, go to configure options, hit advanced tab, the microsoft options. Option 2 will release lease at shutdown and (possibly) unregister DNS when link expires.

Hope this helps
0
 

Author Comment

by:hcca
ID: 33555429
I tried or had already tried all the solutions outlilned by bgoering and I really appreciate his response. Since he was the only responder and brought some solutions, particularly the "microsoft options, option2" which seemed like it ought to work. Unfortunately it did not solve the problem.

We did find a solution and it was to enable both non secure and secure dns updates in domain B. As soon as this was enabled the symptoms of the problem went away. I am unsure if there is a way to make this happen with only secure updates. We even found this to be a problem within Domain A.

If somebody has a solution to this new twist than I'll split the points, otherwise Monday or Tuesday I'll mark this solved and pass the points to the only responder.
0
 

Author Closing Comment

by:hcca
ID: 33578884
Enabling both secure and non-secure updates did the trick
0

Featured Post

Business Impact of IT Communications

What are the business impacts of how well businesses communicate during an IT incident? Targeting, speed, and transparency all matter. Find out more in this infographic.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When converting a physical machine to a virtual machine using VMware vCenter Converter Standalone or vCenter Converter Enterprise, if an adapter type is not selected during the initial customization the resulting virtual machine may contain an IDE d…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question