Skip to content

Can't use my custom DNS server #21

@kirlis950

Description

@kirlis950

Describe the Bug

I cannot ping DNS records and use in my custom DNS server

INFO: 2026/01/30 22:28:00 Starting HTTP server on socket /var/run/olm.sock
INFO: 2026/01/30 22:28:00 Created shared UDP socket on port 53086 (refcount: 2)
INFO: 2026/01/30 22:28:00 Starting hole punch for 1 exit nodes
INFO: 2026/01/30 22:28:00 Websocket Connected
INFO: 2026/01/30 22:28:01 The tunnel IP is: 100.90.128.16/24
INFO: 2026/01/30 22:28:01 Set IPv4 addresses: [100.90.128.16], subnet masks: [255.255.255.0]
INFO: 2026/01/30 22:28:01 Set MTU: 1280
INFO: 2026/01/30 22:28:01 Added IPv4 included route: {DestinationAddress:100.96.128.0 SubnetMask:255.255.255.0 GatewayAddress: IsDefault:false}
INFO: 2026/01/30 22:28:01 Adding route to 100.96.128.0/24 via interface pangolin
INFO: 2026/01/30 22:28:01 Added route for remote subnet: 100.96.128.0/24
INFO: 2026/01/30 22:28:01 Added IPv4 included route: {DestinationAddress:192.168.12.0 SubnetMask:255.255.255.0 GatewayAddress: IsDefault:false}
INFO: 2026/01/30 22:28:01 Adding route to 192.168.12.0/24 via interface pangolin
INFO: 2026/01/30 22:28:01 Added route for remote subnet: 192.168.12.0/24
INFO: 2026/01/30 22:28:01 Added IPv4 included route: {DestinationAddress:192.168.20.0 SubnetMask:255.255.255.0 GatewayAddress: IsDefault:false}
INFO: 2026/01/30 22:28:01 Adding route to 192.168.20.0/24 via interface pangolin
INFO: 2026/01/30 22:28:01 Added route for remote subnet: 192.168.20.0/24
INFO: 2026/01/30 22:28:01 Added IPv4 included route: {DestinationAddress:192.168.12.151 SubnetMask:255.255.255.255 GatewayAddress: IsDefault:false}
INFO: 2026/01/30 22:28:01 Adding route to 192.168.12.151/32 via interface pangolin
INFO: 2026/01/30 22:28:01 Added route for remote subnet: 192.168.12.151/32
INFO: 2026/01/30 22:28:01 Added IPv4 included route: {DestinationAddress:192.168.12.20 SubnetMask:255.255.255.255 GatewayAddress: IsDefault:false}
INFO: 2026/01/30 22:28:01 Adding route to 192.168.12.20/32 via interface pangolin
INFO: 2026/01/30 22:28:01 Added route for remote subnet: 192.168.12.20/32
INFO: 2026/01/30 22:28:01 Started monitoring for site 7 at 100.90.128.1:53818
INFO: 2026/01/30 22:28:01 Configured peer /5Bfp5fMbPQS2Ilc2bpCVAlXR8JYxvDaBjI1kLENxi4=
INFO: 2026/01/30 22:28:01 Started monitoring peer 7

INFO: 2026/01/30 22:28:01 Started holepunch connection monitor
INFO: 2026/01/30 22:28:01 DNS proxy started on 100.96.128.1:53 (tunnelDNS=false)
INFO: 2026/01/30 22:28:01 Starting rapid holepunch test for site 7 at [IP_REDACTED]:53817 (max 5 attempts, 400ms timeout each)
INFO: 2026/01/30 22:28:01 Detected DNS manager: systemd-resolved
INFO: 2026/01/30 22:28:01 Using systemd-resolved DNS configurator
INFO: 2026/01/30 22:28:01 Current DNS servers: []
INFO: 2026/01/30 22:28:01 Setting DNS servers to: [100.96.128.1]
INFO: 2026/01/30 22:28:01 Original DNS servers backed up: []
INFO: 2026/01/30 22:28:01 Set DNS servers: [100.96.128.1]
INFO: 2026/01/30 22:28:01 WireGuard device created.
ERROR: 2026/01/30 22:28:03 Failed to get DNS response for <REDACTED_FQDN_1>.
ERROR: 2026/01/30 22:28:03 Failed to get DNS response for <REDACTED_FQDN_1>.
WARN: 2026/01/30 22:28:03 WireGuard connection to site 7 is DISCONNECTED
WARN: 2026/01/30 22:28:03 Rapid test: site 7 holepunch FAILED after 5 attempts, will relay
INFO: 2026/01/30 22:28:03 Rapid test failed for site 7, requesting relay
INFO: 2026/01/30 22:28:03 Sent relay message
ERROR: 2026/01/30 22:28:04 Failed to get DNS response for <REDACTED_FQDN_2>.
ERROR: 2026/01/30 22:28:04 Failed to get DNS response for <REDACTED_FQDN_3>.
ERROR: 2026/01/30 22:28:04 Failed to get DNS response for <REDACTED_FQDN_3>.
ERROR: 2026/01/30 22:28:04 Failed to get DNS response for <REDACTED_FQDN_4>.
ERROR: 2026/01/30 22:28:04 Failed to get DNS response for <REDACTED_FQDN_4>.
ERROR: 2026/01/30 22:28:04 Failed to get DNS response for <REDACTED_FQDN_2>.
ERROR: 2026/01/30 22:28:05 Failed to get DNS response for <REDACTED_ADMIN_PANEL_FQDN>.
ERROR: 2026/01/30 22:28:05 Failed to get DNS response for <REDACTED_ADMIN_PANEL_FQDN>.
INFO: 2026/01/30 22:28:08 Holepunch to site 7 failed 6 times, triggering relay
INFO: 2026/01/30 22:28:08 Sent relay message
ERROR: 2026/01/30 22:28:08 Failed to get DNS response for <REDACTED_FQDN_1>.
ERROR: 2026/01/30 22:28:08 Failed to get DNS response for <REDACTED_FQDN_1>.
ERROR: 2026/01/30 22:28:08 Failed to get DNS response for <REDACTED_LABS_FQDN>.
ERROR: 2026/01/30 22:28:08 Failed to get DNS response for <REDACTED_LABS_FQDN>.
ERROR: 2026/01/30 22:28:09 Failed to get DNS response for <REDACTED_FQDN_3>.
ERROR: 2026/01/30 22:28:09 Failed to get DNS response for <REDACTED_FQDN_3>.
ERROR: 2026/01/30 22:28:09 Failed to get DNS response for <REDACTED_FQDN_4>.
ERROR: 2026/01/30 22:28:09 Failed to get DNS response for <REDACTED_FQDN_2>.
ERROR: 2026/01/30 22:28:09 Failed to get DNS response for <REDACTED_FQDN_2>.
ERROR: 2026/01/30 22:28:09 Failed to get DNS response for <REDACTED_FQDN_4>.
ERROR: 2026/01/30 22:28:10 Failed to get DNS response for <REDACTED_ADMIN_PANEL_FQDN>.
ERROR: 2026/01/30 22:28:10 Failed to get DNS response for <REDACTED_ADMIN_PANEL_FQDN>.
ERROR: 2026/01/30 22:28:13 Failed to get DNS response for <REDACTED_PTR_DOMAIN>.
ERROR: 2026/01/30 22:28:13 Failed to get DNS response for <REDACTED_LABS_FQDN>.
ERROR: 2026/01/30 22:28:13 Failed to get DNS response for <REDACTED_FQDN_1>.
ERROR: 2026/01/30 22:28:13 Failed to get DNS response for <REDACTED_LABS_FQDN>.
ERROR: 2026/01/30 22:28:13 Failed to get DNS response for <REDACTED_FQDN_1>.
ERROR: 2026/01/30 22:28:13 Failed to resolve primary relay endpoint: DNS lookup failed: lookup <REDACTED_ADMIN_PANEL_FQDN> on 127.0.0.53:53: read udp 127.0.0.1:42388->127.0.0.53:53: i/o timeout
ERROR: 2026/01/30 22:28:14 Failed to get DNS response for <REDACTED_FQDN_3>.
ERROR: 2026/01/30 22:28:14 Failed to get DNS response for <REDACTED_FQDN_2>.
INFO: 2026/01/30 22:28:14 Holepunch to site 7 failed 7 times, triggering relay
INFO: 2026/01/30 22:28:14 Sent relay message
INFO: 2026/01/30 22:28:22 Received exit request via API
INFO: 2026/01/30 22:28:22 Processing shutdown request via API
INFO: 2026/01/30 22:28:22 Restoring original DNS configuration
INFO: 2026/01/30 22:28:22 DNS configuration restored successfully
INFO: 2026/01/30 22:28:22 Hole punch manager stopped
INFO: 2026/01/30 22:28:22 Stopped holepunch connection monitor
INFO: 2026/01/30 22:28:22 UDP hole punch goroutine ended for all exit nodes
ERROR: 2026/01/30 22:28:22 Failed to resolve primary relay endpoint: DNS lookup failed: lookup <REDACTED_ADMIN_PANEL_FQDN> on 127.0.0.53:53: server misbehaving
INFO: 2026/01/30 22:28:23 DNS proxy stopped
INFO: 2026/01/30 22:28:23 Released shared UDP bind
INFO: 2026/01/30 22:28:23 Olm service stopped

i don't know it this referenced in #5 or not.

i tried use documentation, but no avail.

Environment

  • OS Type & Version: Linux Mint 22.3
  • Pangolin Version: Latest
  • Gerbil Version: Latest
  • Traefik Version: Latest
  • Newt Version: Latest
  • Client Version: (if applicable) Latest

To Reproduce

  1. Install Pangolin CLI
  2. Log in as self hosted
  3. Use command (Example: "pangolin up --upstream-dns [self-hosted dns server ip]"
  4. Try ping some website (example: "example.com")

Expected Behavior

Should be given from the IP domain. (or some response)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions