dhcpcd-discuss

RE: 30-hostname Behavior When Switching Network Interfaces

Walrath, Paul

Thu Oct 29 05:48:22 2015

These questions sound similar to what we discussed in a previous thread.  In that thread, we talked about a dual stack server where different fqdns were being provided by both DHCPv4 and DHCPv6.  The first host name provided is what the device's host name got set to.  That became the controlling protocol for the host name.  This prevented the host name from switching back and forth between the DHCPv4 provided name and the DHCPv6 provided name.

I could see a similar issue with a device connected to two separate networks with two network interface adapters.  If each network has a DHCP server providing a host name to the device, the host name could switch back and forth.  I'm not sure, but I think the way this works now is that the first interface to receive a DHCP provided host name sets the device's host name and that interface becomes the controlling interface for the host name.  This is what would cause the issue with having the current network interface disconnect from its network then the other network interface connecting to its network where a new DHCP server exists which is providing a new host name.

Do I understand this right?

Follow-Ups:
Re: RE: 30-hostname Behavior When Switching Network InterfacesRoy Marples
RE: 30-hostname Behavior When Switching Network InterfacesWalrath, Paul
References:
30-hostname Behavior When Switching Network InterfacesWalrath, Paul
RE: 30-hostname Behavior When Switching Network InterfacesWalrath, Paul
Archive administrator: postmaster@marples.name