Thanks, Gustaf,
to answer your questions:
I think that it could be a problem to resolve the DNS on startup because of the timing issues. It is possible that they do not all startup at the exact same time, and therefore the code would be unable to resolve the DNS on startup.
Is there another place we could also try to resolve the DNS like at the time a custerwide command is issued, and we detect that one or more of the servers have not been resolved?
As for why I specified 127.0.0.11 in the nslookup? I believe you are right, it should be able to resolve without specifying the resolver.
Thanks for your help
Marty
