Skip to main content
Question

DNS Resolve internal application NPA

  • June 26, 2026
  • 1 reply
  • 9 views

julien.thomasse-09ebb597

Hello the community.
I need your help.
I’ve opened a high-priority support ticket separately, but I’m looking for information on how DNS works (ping / nslookup).
We’re having an issue with our business applications.

I have an internal application published on our DNS. 
I don’t have any issues at work.
But outside of work, when I ping it, I get the following response:

C:\Users\THOMAJULIE>ping wug.XXX.fr
Sending a ‘ping’ request to wug.XXX.fr [100.64.0.1]  > Normal comportment

C:\Users\THOMAJULIE>nslookup wug.XXX.fr
Server:  UnKnown
Address:  192.168.1.254

Non-authoritative answer:
Name:    wug.XXX.fr.transports.com
Addresses:  2a01:7e01::f03c:95ff:feeb:9d4b
          2a01:7e01::f03c:95ff:fe00:2692
          2a01:7e01::2000:dff:fec1:5cdb
          2a01:7e01::f03c:95ff:feed:783e
          2a01:7e01::f03c:95ff:fe91:5d91
          139.162.181.76
          172.104.149.86
          172.104.251.198
          139.162.174.209
          172.104.203.186

Is this normal behavior?

Can you tell me how ping/nslookup responses work on your tenant?

Have a nice evening 

Julien

1 reply

notskope
  • New Member III
  • July 9, 2026

Yes, this is normal.

 

NPA does not support ICMP, only TCP and UDP.

 

I suggest you check the documentation:

https://docs.netskope.com/en/private-access-best-practices