DHCP Server is not providing domain search list to clients…

[GVJosh]

I'm using pfSense 2.1.2 (haven't had a chance yet to upgrade to 2.1.3), but I don't see anything in the release notes affecting my issue.  So, with that said, in my DHCP server settings I have set the "Domain Name" field to mycompany.local and then set the "Domain search list" field to mycompany.local;othercompany.local.

Generally when this is done, an IP is newed up on a client, and the search list is distributed to that client (Windows 8.1 in this case) and if I were to try to ping somecomputer on the othercompany.local domain the client would search my domain first (i.e. somecomputer.mycompany.local) and if not found then search for (somecomputer.othercompany.local), find it, and return a ping.

However, I found that doing an ipconfig /all is only showing the "Domain name" and nothing in the "Domain search list".  I found a few other posts with this or a similar issue from awhile back but nothing with any solutions: 1) https://forum.pfsense.org/index.php?topic=35329.msg182636#msg182636 2) https://forum.pfsense.org/index.php?topic=60699.msg326940#msg326940 3) https://forum.pfsense.org/index.php?topic=45486.msg238684#msg238684 4) https://forum.pfsense.org/index.php/topic,35329.0.html

I'd be more than happy to work with someone on this to troubleshoot the issue and so I look forward to hearing back soon.  Have a great day y'all.

[johnpoz]

This issue is not with the server, but with the client.. Windows clients don't ask for this info..  Maybe they changed it with 8?  But I doubt it - in the past, windows clients did not ask for this..  You had to set it up via gpo.. And that wasn't even supported until 2003 server I believe.

So this is answered here
https://doc.pfsense.org/index.php/DHCP_Search_Domains_on_Windows_DHCP_Clients

But I like to be complete in answers ;) So as you can see from my attachments did a bit of sniffing for proof in the pudding.. W7 client does not ask for dhcp option 119 (search list) but clearly a freebsd client does - and the dhcp server clearly sends the info when asked for it.

Not every dhcp option is sent in every offer, some have to be requested..

[GVJosh]

OMG, not sure how I missed that in the documentation!  :-[

Thanks for bringing me back to reality and pointing me in the right direction!

[johnpoz]

No problem - why were are here ;)  I have not been able to find any reasoning behind MS not allowing for the dhcp request.  They update their dhcp server software to be able to offer it, and have documentation on how to add option 119..  So why would they not allow their clients to use it via dhcp?