Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
02-29-2024 08:00 AM
We have a hostname that doesn't get resolved by DNS while running through Prisma Access. It works fine if you are off the internal network. I know DNS is proxied via Prisma Access so I'm wondering how to fix this issue. If I bypass DNS (entry in the hosts file) it works correctly.
If I query the hostname from a workstation to 8.8.8.8 I don't get a correct response. Most of my internal DNS servers get the same bad response. One of my internal DNS gets the correct one but not all clients query that internal server. Is there a rule I can create that will allow queries to external servers to function the same? I don't understand why there's a difference.
02-29-2024 09:01 AM
we created an override on the DNS securing profile then added it to the group policy for the particular rule. We are good at the moment.
04-03-2024 06:59 AM
Hi JJohnson37,
Have you created your DNS rule in prisma with both toto.fr and *.toto.fr ?
Rgds
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
