Overview

The DNS capability relies on your operating system’s DNS resolver. The node performs lookups against your system-configured DNS servers — if those servers are unreachable, misconfigured, or filtering Bitping’s domains, DNS will show as disabled.

Check System DNS Settings

Make sure your device has valid DNS servers configured (e.g. 1.1.1.1, 8.8.8.8, or your ISP’s DNS servers).

Linux:

cat /etc/resolv.conf
resolvectl status   # systemd-resolved

macOS:

scutil --dns | head -30

Windows (PowerShell):

Get-DnsClientServerAddress

Check For DNS Filtering

DNS-level ad blockers like Pi-hole, AdGuard Home, or NextDNS can interfere with name resolution — especially if a domain the node uses is on a blocklist. If you run any of these on your network, temporarily bypass them and restart the node to see if DNS lights up.

See Troubleshooting Connectivity for more on resolver-level filtering.

Test DNS Resolution Manually

nslookup p2p.bitping.com

Or with dig (more verbose):

dig p2p.bitping.com

If either command fails or returns 0.0.0.0, your DNS configuration needs attention — fix that first, then restart the node.

See also: Troubleshooting Protocol Failures.