DHCP client error: domain_not_set.invalid
Sebastiaan van Erk
sebster at sebster.com
Tue Nov 22 06:20:18 PST 2005
>>I understand the idea that bad values should be rejected, but in
>>reality, I have the same DSL modem that these others have and there is
>>no way to change the domain search list that it sends. No way that I
>>could find at least. This is SBC-Yahoo in California, so there are a lot
>>of people out there with this modem.
> Well ring your ISP and complain. Too many people just
> accept crappy service.
This is just the attitude that's going to get people to use other
software. People are going to laugh at you trying to get a network
connection and joke "it works fine with Windows". Then you try and
explain that it's not your OS's fault and somebody messed up some
setting somewhere else. And then they laugh some more watching you struggle.
Furthermore it's really not realistic to expect that ISP's are going to
do anything about it either. They have a billion other more important
issues other than solving that insignificant problem that "that guy who
is using an unsupported OS" has. They really don't care.
>>dhcpd should either
>>1. accept bogus names (warnings are fine)
>>2. offer a configuration option or command line switch to allow the
>>bogus domain if we wish
>>3. offer a configuration option like isc-dhcpd does so that we can
>>ignore or override the setting
I would have to agree here. I think option 2 is great, because it gets
people to be aware of the problem, but it allows them to workaround it
I really think it's terrible to have the software just reject a lease
because of an invalid search domain, without you being able to fix it
without hacking code. That's going a bit overboard IMHO and is just
going to cause more problems than it's going to solve.
More information about the freebsd-stable