Erik Nordmark writes: > Does this mean it would be wise from an interoperability perspective to > extend and evolve the dhcpagent interface so that dhcpagent doesn't do > any SIOCS* ioctls?
Yes. In fact, we've discussed exactly this (in various forms) on the NWAM mailing list in the past -- either as a "stop-and-wait" checkpoint in dhcpagent, or as a "let somebody else actually plumb" design. > The alternative (which is less work) is to hope that all DHCP servers > that matter will provide the domain name in the offer/advertise message. I think that's probably not a good bet. Given the way ISPs seem to operate, I doubt that they'll provide usable domain names, because, frankly, they don't care or need to care. You don't need to know the "local" domain in order to browse www.google.com, and that's all that matters. Enterprises, though, are quite likely to set this up properly -- if they set it up at all. One problem here is that the DHCPv6 domain name (actually, search list) matters only if you're getting IPv6 DNS server addresses as well from the DHCPv6 server. Given that many people using IPv6 are still running DNS itself over IPv4, there might not be much of a point in configuring that into a DHCPv6 server. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
