Hub DNS Dig Tool 🇬🇧 🇨🇳 🇮🇳 🇪🇸 🇨🇿 🇩🇪 🇳🇱 🇫🇷 🇮🇹 🇵🇱 🇷🇴 🇷🇺

Created: 2026/06/26 19:26:35 America/Chicago

By: admin

What This Tool Checks

The DNS dig tool shows how the hublist server resolves a public hub hostname for a selected DNS record type.

Use it after moving a hub, changing DNS, adding IPv6, or checking why clients see a different target than expected.

Correct DNS is essential for DC++ discovery because hublist files and client bookmarks usually depend on hostnames staying stable.

Run a dig-style DNS lookup for public hub hostnames and inspect A, AAAA, MX, NS, SOA, TXT, or CNAME records.

Host Or Address Enter a public hostname, IP address, or hub-style address such as dchub://example.com:411.

Record Type Choose the DNS record type to query.

Solve CAPTCHA

Submit a public Direct Connect hub for hourly checks, searchable indexing, and inclusion in the public NMDC, NMDCS, ADC, and ADCS hublist files.

Test whether a public DC++ or Direct Connect hub hostname responds to ICMP ping, then review packet loss, latency, and DNS resolution.

Look up public WHOIS, registrar, domain, and network ownership information for Direct Connect hub hostnames and IP addresses.

Review A, AAAA, CNAME, MX, NS, SOA, and TXT records for public Direct Connect hub hostnames from the hublist server.

Check reverse DNS PTR hostnames for public IP addresses used by Direct Connect and DC++ hubs.

Test whether a specific public Direct Connect TCP port accepts connections from the hublist server for NMDC, NMDCS, ADC, and ADCS hubs.

Test whether a public DC++ hub endpoint accepts dchub, NMDC, NMDCS, ADC, or ADCS connections from the hublist server.

Inspect public TLS certificate details for secure Direct Connect endpoints, NMDCS hubs, ADCS hubs, or related hostnames.

Trace the network path from the hublist server to a public Direct Connect hub hostname or IP address for routing diagnostics.

Run a bounded public TCP check against common Direct Connect hub ports and see which NMDC, NMDCS, ADC, or ADCS ports appear reachable.