Skip to content
Connection-specific DNS Suffix Search List not applied in Windows 11
Got a problem with Viscosity or need help? Ask here!
Just tested, we have the VPN server pushing the list in a split-dns configuration and DNS not working as expected.
If you run a ipconfig /all you can see that Connection-specific DNS Suffix Search List is not being applied in Windows 11 although it's being pushed by the server.
If you run a ipconfig /all you can see that Connection-specific DNS Suffix Search List is not being applied in Windows 11 although it's being pushed by the server.
Hi basseed,
Could you please post the following as well as a copy of your ipconfig output - https://sparklabs.com/support/kb/articl ... ort-staff/
As this is a public forum, you're welcome to email this to us instead - https://sparklabs.com/support#contact
Regards,
Eric
Could you please post the following as well as a copy of your ipconfig output - https://sparklabs.com/support/kb/articl ... ort-staff/
As this is a public forum, you're welcome to email this to us instead - https://sparklabs.com/support#contact
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Hi basseed,
Per our email back and forward I'm just posting a follow up in case anyone else comes across this. We have reported this to Microsoft and received a confirmation that there is a bug in Windows 11 where domain suffixes (DHCP Option 119 and static) are ignored by the operating system. There is a fix in the pipe line coming apparently but there is no public tracking link.
Our recommendation for now is if you require suffixing beyond a single domain, you will need to remain on Windows 10 for now until a fix is pushed via Windows update for Windows 11.
Regards,
Eric
Per our email back and forward I'm just posting a follow up in case anyone else comes across this. We have reported this to Microsoft and received a confirmation that there is a bug in Windows 11 where domain suffixes (DHCP Option 119 and static) are ignored by the operating system. There is a fix in the pipe line coming apparently but there is no public tracking link.
Our recommendation for now is if you require suffixing beyond a single domain, you will need to remain on Windows 10 for now until a fix is pushed via Windows update for Windows 11.
Regards,
Eric
Eric Thorpe
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
Viscosity Developer
Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
3 posts
Page 1 of 1