i think Daniel Goetzman wrote a doc about doing the DNS server thing somewhere but i can't find it.
these docs show using compliance to initiate the deploy, but you could just do the blpackage part w/ the property values.
Thanks for the links. They do help to do this in a compliance job but I'd prefer if there were a simplier method.
You mention you think it could be done in blpackage; how? I can't see how the blpackage can provide alternate nameserver IPs based upon the server location property.
The server location property should be of type property class, not string.
Then in the resolve.conf config file (not file) you can have entries for the nameserver lines like ??TARGET.LOCATION.DNS1?? as the value.
LOCATION would point to a custom class called SERVER_SETTINGS
It would have a couple properties like DNS1 and DNS2.
You’d have as many instances as locations, each location instance would have different values for DNS1 and DNS2.
So you’d set the LOCATION property to the instance it should be per server. then the blpackage would resolve the values based on the instance associated w/ the server.
A few questions that would help develop some answers:
How are you provisioning PXE, VGP, etc?
Do you have a separate datastore at each location?
App server in each location or central?
Is your /etc/resolv.conf
file more than 2000 characters?
Bill, thanks for the extra info on the blpackage model. It works really well but I did discover a problem. If I deploy the blpackage to a server that does not have the location property on it or the property is not set to a value it wipes out the current value in the file.
I know I can set a default value for the property but I’d like to know if there is a way around this behavior?
Set a default.
Or base the deploy on compliance that handles that condition ☺
That’s what I figured but thought perhaps you knew of some magic