topic Re: Global Protect DNS Suffix Not Propogating to Client in General Topics

Global Protect DNS Suffix Not Propogating to Client

MHaran — Tue, 08 Mar 2016 22:02:16 GMT

Hi,

I have a strange issue where my Global Protect SSL Client connects to the firewall with no issues. I get the IP, the routes and the DNS servers but I don't get anything listed in the DNS Suffix entry. I have configured the DNS Suffix correctly under 'Global Protect Gateway', 'Client Configuration', 'Network Settings' and can even see the DNS Suffix being received from the agent during my agent debug when trying to connect but nothing shows up in IPCONFIG.

Any ideas?

Regards

Mike

Re: Global Protect DNS Suffix Not Propogating to Client

vkalal — Wed, 09 Mar 2016 13:31:37 GMT

Try this:

> Run gpedit.msc

> Browse Local Computer Policy

> Computer Configuration

> Administrative Templates -> Network -> DNS Client

Enable "Allow DNS Suffix Appending to Unqualified Multi-Label Name Queries"

Please let me know if this helps

Re: Global Protect DNS Suffix Not Propogating to Client

OtakarKlier — Wed, 09 Mar 2016 14:41:35 GMT

Hello,

Do you have the domain listed under the radius profile?

Device->Server Profiles-> RADIUS

Then see if the domain is listed there. This did the trick for me.

Regards,

Re: Global Protect DNS Suffix Not Propogating to Client

MHaran — Wed, 09 Mar 2016 18:21:21 GMT

Unfortunately no difference

Re: Global Protect DNS Suffix Not Propogating to Client

Lucky — Thu, 10 Mar 2016 06:39:47 GMT

Hi MHaran,

did you search Windows logs? Could it be that some other software is protecting / preventing GP Agent to set DNS suffix to the system? Is your GP Agent running as a service as well on that Windows host? What is the version of Windows you are having as hosts?

Re: Global Protect DNS Suffix Not Propogating to Client

abjain — Thu, 24 Mar 2016 01:26:36 GMT

Hi,

Did you had a chance to look at https://live.paloaltonetworks.com/t5/Management-Articles/DNS-Suffix-is-not-Listed-under-GlobalProtect-Network-Adapter/ta-p/58001

If this is already verified, could you check if the issue is specific to any Client OS/ GP version?