Templates and reverse lookup zones

[proden20]

I seem to have a problem where my reverse lookup zones are getting populated with a template's hostname, and another record with the VM's hostname post-sysprep.

This is causing problems with some applications that are apparently using reverse lookup zone information for translation, although I couldn't clarify exactly how it is causing the failure, I know that purging the template's record alleviates the issue.

Probably more of an MS issue than VMWare...but perhaps someone knows what I've done wrong...

Dennis Procopio - VCP

Please remember to award points for helpful or correct responses.

[RParker]

> template's hostname, and another record with the VM's hostname post-sysprep.

Yeah that's not a problem, that's how DNS works. Your template comes up FIRST, THEN it gets configured. The name it has ON the network is what DNS sees.. There is nothing you can do about that.

That's how sysprep works, whatever name is in the machine it boots, then the name changes then it restarts with the NEW name...

[proden20]

I understand that's how DNS works I put the zones there.

MS should understand that if a machine had a name one moment and the next moment it has a brand-new name, they should use their ultra savvy AD integrated DNS capabilities and clean up the records.

What good is a lookup zone if the returned data is inaccurate? What happens if I want to set up reverse DNS with a VMWare View environment where machines are constantly being deployed and destroyed?

I'm looking for a solution other than going in by hand.

thanks anyway.

Dennis Procopio - VCP

Please remember to award points for helpful or correct responses.

[RParker]

they should use their ultra savvy AD integrated DNS capabilities and clean up the records.

Yeah they do, it's called the LAN ADMINISTRATOR

What good is a lookup zone if the returned data is inaccurate?

If the zone is innacurate, that's a function of your DNS configuration. And the fact that you setup machines that are destroyed constantly, isn't a problem still. That's simply a side affect.

What happens if I want to set up reverse DNS with a VMWare View environment where machines are constantly being deployed and destroyed?

Besides you are way over thinking this, just set the aging record on the template name to expire after like 1 minute.. That will solve the problem.

you want DNS and Microsoft to rewrite the system just because it's a problem for YOU to cleanup a few records? I think you should find the culprit of the reverse lookup with Apps, rather than finding fault with the system.

The system is fine, if it weren't millions of users would have flagged this as an issue long ago. no its not perfect, but what you describe just isn't feasible, so you can live with it..

Besides which you have to give your apps a chance to realize the change.. I bet you test the apps immediately after completion of deployment and immediately go to the DNS server to fix it right?

Yeah.. just give it a few minutes, it will probably correct it self, then you will you panic for nothing.

This is STILL not a problem.

[proden20]

Either someone wrote MS DNS or the template provisioning system, or just needs a Midol. These communities are for questions, your aging answer would've sufficed the first time. With the # of points you have in these communities you could have better etiquette.