To give this a report some more shape of a bug report...

dhcdbd seems not to set the domain name it received with the DHCP response from the DHCP server. Does dhcdbd already have support for setting the domain name?

additionally, it seems that the "old" scripts are fighting with networkmanager over the interface:

g67:~ # ps aux|grep ifplugd
root      4885  0.0  0.0   1476   428 ?        Ss   13:58   0:00 /sbin/ifplugd -i eth0 -r /etc/sysconfig/network/scripts/ifplugd-selectif -f -I

i have now stopped networkmanager and restarted network and now i have a nis domainname.

Installation was a simple click-through-accept-everything install of alpha3, network was proposed as dhcp for wired, unconfigured for wlan and i accepted this.

OK, this another problem.  The default installation of Alpha 3 does not yet set network devices to "managed".  Thus, ifplugd does try to get its hands on the device(s) as well as NetworkManager.

If you want to use NetworkManager, please change the interfaces to "managed" using YaST.  Afterwards ifplugd (ifup) does not try to touch the interfaces and NetworkManager does the job.

See #134054 for details.

The domain name issue remains.

Yes, it is a known issue that dhcdbd / NM do not set the hostname from DHCP.

I think this is intentional, by the original authors, to avoid the usual X hostname problems.  Or maybe they just felt that the feature was not needed.

But if we need it, we can add it.

Echoing Timo, the other issue is unrelated.  ifplugd and any other dhcp client outside of NM's pervue should not be running.

We definitly need the hostname to be set via DHCP.  Do you think Jason will accept a patch for upstream to get this into dhcdbd?

I am sure he will.

*** Bug 134170 has been marked as a duplicate of this bug. ***

This must be configurable. Some people need the hostname to be set, others hate it because of X trouble.
It were nice if we could add a command line option for NM to en/disable this. Then we could use /etc/sysconfig/network/dhcp:DHCLIENT_SET_HOSTNAME.

*** Bug 119921 has been marked as a duplicate of this bug. ***

I just committed a patch from sscheler to CVS to add NIS support, so this bug is resolved as fixed once we build updated packages.

NM now manages NIS data from DHCP, writes out the configs, and (re)starts the daemons.

The issue is still present on alpha4. Domainname is not set, no NIS available.
Roberts fix just missed alpha4.

Note that you do want this to be configurable on a per interface basis. Setting NIS/NTP/hostname from the trusted LAN interface makes sense. You certainly don't want it on untrustworthy WLAN or DSL connections though.

Wrt NIS writing yp.conf and starting ypbind/autofs are separate steps IMO. On my laptop I do let dhcpcd write yp.conf but don't have ypbind and autofs running by default. I activate them manually if I actually need them.

*** Bug 142758 has been marked as a duplicate of this bug. ***

Still present in SLES10 preview4.  I'll try to get this fixed for beta 1.

/etc/dhclient.conf needs some love:

We need to add nis-servers and nis-domain to 'request':

     26 request subnet-mask, broadcast-address, time-offset, routers,
     27         domain-name, domain-name-servers, host-name, nis-servers,
     28         nis-domain;

Having this, dhclient will set the domainname, the hostname is still not being set.  Stefan will you please take care of this one?

cc'ing Peter, Stefan and Robert.

Note that one can configures whether to honor those options in /etc/sysconfig/network/dhcp. Would be good if NM could read that file.

Thanks for the pointer.  However, the right place to have this would be dhcdbd, not NM itself.

Oh what a wonderful field trip through the DHCP universe.

We don't need to touch NM or dhcdbd to achieve the desired behaviour.

I have made the following changes to the dhcp package to get everything done:

* add 'nis-domain' and 'nis-domain-servers' to 'request' of /etc/dhclient.conf
* extended /sbin/dhclient-script to set domain name and host name.  This will only happen if the relevant options in /etc/sysconfig/network/dhcp are set.

Please do tests whether things are working as expected.

Well, it's not 'nis-domain-servers' but 'nis-servers' as mentioned before.

Hm?  The patch looks like this:

request subnet-mask, broadcast-address, time-offset, routers,
-       domain-name, domain-name-servers, host-name;
+       domain-name, domain-name-servers, host-name, nis-domain,
+       nis-domain-servers;

What you are saying is that 'nis-domain-servers' is not required?

'nis-domain-servers' does not exist. this options is called 'nis-servers'.

Thanks Stefan, I've submitted an updated package to STABLE.