Cannot resolve by short name after moving DHCP to Windows AD.

Linux DHCP was able to give out DNS search domains.  Windows doesn't.
Cannot resolve by short names after migrating DHCP to Windows AD Servers 2016.
Option 119 DNS Search List not working.  Even though says it design for non-windows client.  Domain names with semicolon.   Still not resolving.
Group Policy wont work because the clients aren't joined the Domain.  

So the only option to tell the users to use a FQDN (long names) from now on.  Some unhappy.  Oh well.  

Any other options?
LVL 17
Tiras25Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MaheshArchitectCommented:
Windows DHCP and windows clients both did not support DHCP option 119

The only way to provide search list is to use group policy for domain joined machines or configure script / manually on workgroup machines

without search list windows dns only able to resolve hostnames in native domain zone

for other zones, it cannot resolve those short names unless client is configured to use search list
https://blogs.msmvps.com/acefekay/2011/02/12/configuring-dns-search-suffixes/

I would suggest that educate users to use FQDN as far as possible as DNS is meant to resolve FQDN only

one more option is to use Linux dns as primary dns on clients via dhcp and it should resolve all hostnames

Configure secondary zone of your active directory domain dns on Linux server or setup conditional forwarder on Linux dns towards AD domain dns so that when Linux box receives any query wrt AD, query will get forwarded and handled by windows DNS

mean time you can find out way on client machines to configure dns search list on NIC properties and then switch fully to windows dns
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Shaun VermaakTechnical SpecialistCommented:
0
footechCommented:
Windows clients will ignore Option 119, but Linux and Mac won't.
Good description of creating the option in Windows DHCP is here.
http://www.mattzuba.com/2011/03/windows-2008-rc2-dhcp-server-option-119/

I would use the PS script found in the below link to set the value correctly.
https://www.craig-tolley.co.uk/2016/03/07/dhcp-option-119-dns-search-suffix-powershell-array-builder/
0
Shaun VermaakTechnical SpecialistCommented:
If you want suffixes in Windows, use Group/Local policy
manage-dns-suffix-configuration-through-
0
Tiras25Author Commented:
Sorry for the delay.  Still working on the right solution.  Will get back to you soon.
Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.