cyber_birkeland
asked on
DHCP DNS Suffix Search List
We have a dhcp server, Windows 2008 R2. We are using server option 135 with a listing of 3 domains (1 parent, 2 child). When I release and renew dhcp on the client systems, it is not picking up the 1 child domain DNS I just added into the list (it's 2nd in the search order listing). The local systems are dhcp, no GPO setup for DNS suffix, no local policies setup on the clients, and networking adapter is set to "append primary and connection specific dns suffixes" and "append parent suffixes of the primary DNS suffix"
I've stopped/restarted dhcp, I've rebooted client, I've /release /renewed client and still not picking up correct suffix order. Any suggestions?
I've stopped/restarted dhcp, I've rebooted client, I've /release /renewed client and still not picking up correct suffix order. Any suggestions?
footech
Windows clients do not query for option 135, they will never get it. You will need to use another method like Group Policy to configure this.
ASKER
Thanks for the response. Then why does DHCP even have a suffix option then?
Option 135 is not support by Microsoft DHCP servers.
See previously answered question:
https://www.experts-exchange.com/questions/27552418/How-do-I-add-DHCP-DNS-Suffix-Search-List.html?anchorAnswerId=37492919#a37492919
The link in that answer tells you why and how to achieve your objective.
http://msmvps.com/blogs/acefekay/archive/2011/02/12/configuring-dns-search-suffixes.aspx
See previously answered question:
https://www.experts-exchange.com/questions/27552418/How-do-I-add-DHCP-DNS-Suffix-Search-List.html?anchorAnswerId=37492919#a37492919
The link in that answer tells you why and how to achieve your objective.
http://msmvps.com/blogs/acefekay/archive/2011/02/12/configuring-dns-search-suffixes.aspx
ASKER
We have 2 dhcp servers, one is for our production environment child domain and the other is for our lab environment child domain - these both are all under the same forest.
I have setup server option 119 domain search list on our lab dhcp server, which is also a DC for lab.company.com. This is working for both our linux users and windows users getting our 2 child domain suffixes and our forest suffix fine.
I am trying to setup the same 119 server option for our production dhcp, which is not on a DC. On the linux machines, they just get the child domain, on the windows, they get the child domain suffix and forest suffix.
What could be causing this issue? We cannot setup GPO as we have a lot of linux and mac users. We are trying to avoid having each client system setup dns suffixes in their DNS NIC properties.
I have setup server option 119 domain search list on our lab dhcp server, which is also a DC for lab.company.com. This is working for both our linux users and windows users getting our 2 child domain suffixes and our forest suffix fine.
I am trying to setup the same 119 server option for our production dhcp, which is not on a DC. On the linux machines, they just get the child domain, on the windows, they get the child domain suffix and forest suffix.
What could be causing this issue? We cannot setup GPO as we have a lot of linux and mac users. We are trying to avoid having each client system setup dns suffixes in their DNS NIC properties.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.