Had to try this myself, and yes, a configuration option with this
name does not even exist in the source code of dhcpd. This caused
me to reread the manpage:
"Note that dhcpd(8) calls this option option-119 instead of
domain-search and only supports the rfc1035 variant."
So indeed, you can't use the option name "domain-search", but have
to use a line like:
option option-119 "dmz.dom.org";
I was unable to figure out, what exactly is meant with RFC1035 type
string, but came to the conclusion, that dhcpd in its current iteration
only supports one domain name here. Oh well.
Cheers,
Rudi
On Tue, 2019-09-24 at 08:32 +0000, Carlos Lopez wrote:
>
> Regards,
> C. L. Martinez
>
> On 24/09/2019 10:22, Rudolf Leitgeb wrote:
> > Could this be a case of missing semicolon at the end ?
> >
>
> Thanks Rudolf, but not ... My complete config is:
>
> subnet 172.22.55.0 netmask 255.255.255.224 {
> option routers 172.22.55.30;
> range 172.22.55.17 172.22.55.27;
> option subnet-mask 255.255.255.224;
> option broadcast-address 172.22.55.31;
> option domain-search "internal.dom.org", "dmz.dom.org";
> }
>
