I have set up a VMware View testing environment with an automated pool of nonpersistent linked clones. One of the key demands to these machine from my side is, that they are to be destroyed after usage, so the user gets a "fresh" clone each time he connects. Everything works fine so far, but the machine entries in DNS are not updated or deleted as they should. So everytime a poolmachine gets recreated by the composer, the original entry of her predecessor is still in place in DNS and the new one ist not to be found with her actual IP.

I thought about differing the naming patter through a continuous ordernumber (would become astronomically high, i know) or something like that, but there is no option for such a wildcard given. So the only chance was to set DNS-Update to non-secure, which actually works. But this can't be the only solution. Do you know if there is a more suitable fix for this problem?

I would be gratedful for any suggestions. Thanks in advance