Prisma Access internal DNS server is 127.0.0.1
At a glance
Base severity
Area
Platform
Evidence level
Benchmark reference
Reads the export, not the device
ConfigProof reads a configuration export. This control is evaluated against the objects in that file, and it reports what the file says. It does not connect to the device and sees no traffic, so a finding here describes the configuration, not what the firewall is doing right now.
Why it matters
Palo Alto Networks states not to use 127.0.0.1 as a DNS server, as it can cause Prisma Access internal routing issues. Internal names do not resolve through it.
How to fix it
Web interface
The steps below are written for the web interface. A finding raised on your own export carries the same steps with your object names filled in.
- Replace it with the address of an internal DNS server that every mobile user pool can reach.
Command line
Panorama CLI, Cloud Services plugin
set plugins cloud_services remote-networks internal-dns-match <dns-entry> primary dns-server <address>An example. Values in angle brackets are yours to supply; a finding on your own export fills in the names it read. Nothing here commits or pushes. Review, commit, then push to Prisma Access yourself.
Read it back
show plugins cloud_services remote-networks internal-dns-matchValues to fill in2
- <dns-entry>
- The internal DNS entry
- <address>
- An internal DNS server address
Before you type it2
- Prisma Access is set in the Cloud Services plugin on Panorama: commit to Panorama, then push the change to Prisma Access from the plugin.
- A tenant managed by Strata Cloud Manager has no command line: make the same change in Prisma Access Setup and push it.
How to confirm the fix
- From a mobile user, resolve an internal name.
Limits
- No limitation is recorded for this control beyond the one that applies to all of them: it reads a configuration export.
Compliance references
No benchmark recommendation is mapped to this control in this version.
More in IPSec VPN
- PAN-SEC-143Prisma Access remote network subnet overlaps another network
- PAN-SEC-144Prisma Access site receives a default route from Prisma Access
- PAN-SEC-145Prisma Access service connection summarizes mobile user routes while remote networks exist
- PAN-SEC-146Prisma Access service connection has no secondary tunnel or backup
- PAN-SEC-147Prisma Access sends mobile user internet traffic to the data centers
- PAN-SEC-148Prisma Access BGP session has no secret
- PAN-SEC-150Prisma Access has service connections and no internal domains
- PAN-SEC-155Prisma Access infrastructure BGP AS is not a private AS
See it on your own firewall
One complete analysis of one firewall costs nothing. A card is required and nothing is charged.