sysidcfg name_service setting to enforce fetching DNS config from DHCP
In /etc/sysidcfg templates we can set name_service to be DNS, LDAP, NIS or NONE. Would it be inappropriate to define a new type and set it to "DHCP" (and then fetch name-service info from DHCP)?
Some networking clients might want the changes to their DNS/nsswitch config files from a dynamic wizard, others might not. The policy might even differ per-local zone (see also bug #2875 regarding DHCP-DNS support for local zones). For example, there is "fear" of scripts which might corrupt manually crafted settings for files+dns+ldap host lookups, etc.
So far I have not seen any configurable switch that would request or forbid changes to the /etc/resolv.conf and /etc/nsswitch.conf files using data from DHCP.As an option, might it make sense to integrate this solution (an SMF service to combine user-preferred and DHCP-dynamic resolver options, which can then be enabled or disabled on a particular zone)?
I've started a thread on the mailing list (also touching on some other related issues), but so far got no answers, here: http://email@example.com/msg08029.html