pangolin_mirror/docs-v2
1
0
Fork 0
mirror of https://github.com/fosrl/docs-v2.git synced 2026-09-19 12:29:08 +02:00
Code Issues Packages Projects Releases Wiki Activity

Remove ping comments

Browse Source
This commit is contained in:
Owen
2026-05-11 18:06:05 -07:00
parent 6b59558384
commit 22e5aa55a0
1 changed files with 0 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
manage/resources/private/alias.mdx
-4
View File
@@ -40,7 +40,3 @@ If you use a wildcard such as `*.proxy.internal`, it will match any hostname tha
Aliases work by overriding the DNS of your computer running the client so that all DNS requests are sent to the Pangolin client for resolution. That behavior is controlled by the Enable Aliases (Override DNS) preference; see [Configure Clients](/manage/clients/configure-client#enable-aliases-override-dns). The DNS server on your computer is typically `100.96.128.1` (the first address inside of your utility subnet on the org) when connected to the tunnel, which forwards requests to an upstream server. By default, we use `1.1.1.1`, but this upstream address can be configured in the CLI or in the client settings.
**If you are attempting to set an upstream DNS server that is only accessible via the tunnel, ensure that you create a resource and check the tunnel DNS option in the client configuration settings.** Otherwise, connectivity to the server may fail when connected to the tunnel. Enable Aliases (Override DNS) must also be on—see [Configure Clients](/manage/clients/configure-client#enable-aliases-override-dns)—so the client can intercept DNS and forward queries to the upstream server.
## ICMP Ping
Aliases do not currently support ICMP ping requests. If you attempt to ping an alias, it will not respond, even if the underlying resource is reachable. This is because the Pangolin client does not intercept ICMP packets for alias resolution.