Scavenging of duplicate DNS names when ghosting

  • Thread starter Thread starter v_koski
  • Start date Start date
V

v_koski

Hi!

We're using Ghost for deployment of Windows XP machines in our AD
domain, and for every machine we deploy, we get duplicate hostnames in
the DNS: one for the Ghost image and one unique. Our problem is that we
have an application that relies on correct reverse zone lookups. Is
there a way to avoid the double hostname registrations?

Scavenging more often than once a day isn't a very good option, from
what I've read. We have the DHCP server always updating A & PTR
records, would skipping that option relieve us from the duplicates, or
is it just an unavoidable result of using Ghost for deployment?

I'd be grateful for any tips!
 
Hi!

We're using Ghost for deployment of Windows XP machines in our
AD
domain, and for every machine we deploy, we get duplicate
hostnames in
the DNS: one for the Ghost image and one unique. Our problem
is that we
have an application that relies on correct reverse zone
lookups. Is
there a way to avoid the double hostname registrations?

Scavenging more often than once a day isn't a very good
option, from
what I've read. We have the DHCP server always updating A &
PTR
records, would skipping that option relieve us from the
duplicates, or
is it just an unavoidable result of using Ghost for
deployment?

I'd be grateful for any tips!
Click to expand...

If you allow only secure dynamic updates the ghost image when restored
will not register its records because it is not allowed to do so as it
does not belong to the domain. However at this moment you cannot
control who gets an IP or not. So if DDNS is done by DHCP on behalf of
the clients the (both A and PTR) records will get registered as the
DHCP server is authorized and a member of the domain. What you could
do is:
* to have the DHCP server not register DNS records on behalf of the
clients
OR
* Install the clients on a separate subnet, have a DHCP scope for that
subnet but do not register DNS records on behalf of the clients for
THAT scope. In other words disable DDNS on THAT DHCP scope
 
Back
Top