Internal and External server same name

Dang that was an easy fix..  Thank you

Welcome to the community. 

But this should works without using the internal dns option. Netskope should be intercepting that fqdn. What we found is that blocking dns over https is usually the cause for this. We’ve deployed a simple utility policy in Netskope to do this and all our NPA fqdn intercepting works now. 

I have a follow up question.  On a different app we are seeing where the private app only works when we disable dns over https in the browser.   How would I do that in Netskope?

You can accomplish this with a simple Real-time Protection Policy. “DNS over HTTPS” is an application in the list. Just create a policy to block it with no notification. In fact, I’m under the impression this is standard policy deployment for new customers by their SE’s now. 

That worked like a charm