Skip to content

Private DNS

Private DNS lets connected users reach your private resources by name, for example wiki.parzify.internal, instead of by IP address. While a user is connected, the agent sends DNS requests to the DNS servers you set here.

You can set DNS servers for a whole network, and different DNS servers for one region of it.

Private DNS servers only

Use the IP of a DNS server inside your private network, for example an AWS Route 53 Resolver endpoint or your office domain controller. Public DNS servers such as 8.8.8.8, 8.8.4.4, 1.1.1.1 or 9.9.9.9 can't be used here.

Set DNS servers for a network

  1. Open the network, click the ... menu on the network card and choose Private DNS.
  2. Turn on Enable Private DNS.
  3. Enter the Server IP Address and keep the Port at Standard (53). Click + Add Server to add more servers.
  4. Optional: in Search Domains, enter your internal domain, for example parzify.internal. Users can then type a short name like wiki instead of wiki.parzify.internal. Click + Add Domain to add more.
  5. Click Apply. Connected agents get the change right away and reconnect on their own.

Add Private DNS dialog with the switch, the server and the search domain highlighted

When private DNS is set, the network card shows a globe icon above the network name.

Set DNS servers for one region

Use this when each region has its own DNS server, for example one per office.

  1. On the region card, click the ... menu and choose Regional Private DNS.

    Region menu with Regional Private DNS

  2. Fill in the dialog as above and click Apply.

    Regional private DNS for New Jersey with its own server and search domain

Users connected to a gateway in that region use the regional servers.

The DNS server must be reachable

The DNS server's IP must be reachable through a tunnel and listed in the route table. With Manual split tunneling, the server's subnet must be in the list too.

Turn off private DNS

Open the dialog, turn off Enable Private DNS and click Apply. Names then resolve only on public DNS.

Troubleshooting

Problem What to check
Names don't resolve The agent is connected to this network. The DNS server is reachable, see the tip above. The DNS server has a record for the name.
Short names don't work The domain is in Search Domains. Reconnect the agent after the change.