Thank you VickyWang-MSFT
I have found the issue with the Split-tunnel configuration in our VPN which had allowed only abc.local domain and not the rest of them. After allowing it works.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a domain abc.local and have xyz.local as another dns zone hosted on all AD integrated servers all domain joined computers can RESOLVE the AD Dns abc.local and also all the other zones, but when a non-domain joined computer is added to the network and is using one of the DCs to resolve it, then they only can resolve the AD Dns i.e abc.local but not the other dns zones. Why? Do i need to configure something different for non-domain joined.
Thank you VickyWang-MSFT
I have found the issue with the Split-tunnel configuration in our VPN which had allowed only abc.local domain and not the rest of them. After allowing it works.
Hi,
Thank you for posting in our forum.
1.Use nslookup xzy.local to see what results are returned
2.If you cannot get the result back, you can check the permission of xyz.local DNSzone, whether only users in the domain have permission to check.
Hope this information can help you
Best wishes
Vicky
Hi,
Thanks for your reply and waiting
ipconfig only reflects the current configuration of the local network card, and does not mean that the DNSserver is still used after contacting the vpn. Under normal circumstances, use the DNS server in the VPN after linking to the VPN
Hope this information can help you
Best wishes
Vicky
Hi,
Just checking in to see if the information provided was helpful.
Please let us know if you would like further assistance.
Best Regards,
Vicky