[Userland] [OpenIndiana Distribution - Feature #2876] sysidcfg name_service setting to enforce fetching DNS config from DHCP

[illumos project]

Issue #2876 has been updated by Ken Mays.

Assignee set to OI Userland


----------------------------------------
Feature #2876: sysidcfg name_service setting to enforce fetching DNS config from DHCP
https://www.illumos.org/issues/2876

Author: Jim Klimov
Status: New
Priority: Normal
Assignee: OI Userland
Category: 
Target version: 
Difficulty: Medium
Tags: needs-triage


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)?
* http://thestaticvoid.com/post/2011/01/11/persistent-search-domains-with-nwam-and-dhcp/

I've started a thread on the mailing list (also touching on some other related issues), but so far got no answers, here: http://www.mail-archive.com/openindiana-discuss@openindiana.org/msg08029.html


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account