This guide explains the combined DNS view used to audit a public Direct Connect hub hostname before testing its service ports.
Usage
- Open DNS Overview and enter a public hostname or hub URL in Host Or Address.
- Select Review DNS.
- Compare the grouped A, AAAA, CNAME, MX, NS, SOA, and TXT records returned to the hublist server.
Concrete Example
After adding IPv6 to hub.example.net, the overview should show the intended IPv4 A record and IPv6 AAAA record. If a CNAME is present, its final target should provide the usable addresses. NS and SOA should name the zone you actually manage.
Interpretation
A and AAAA are client connection targets. CNAME is an alias. NS and SOA describe authority and zone timing. MX and TXT usually support mail, verification, or policy rather than a DC++ connection. NXDOMAIN means the queried name does not exist; an empty NOERROR response means the name exists without that record family.
Troubleshooting
- No Address Record: Add the required A or AAAA record.
- Old Address: Correct the authoritative zone and allow the previous TTL to expire.
- Different Local Result: Check split DNS and resolver caches.
- DNS Correct, Hub Offline: Test the published port with TCP Connect, inspect secure endpoints with TLS Certificate, and verify the protocol with Protocol Test.
Icon Reference
| Icon | Label | What It Does |
|---|---|---|
| Review DNS | Review DNS collects the supported public DNS record families. | |
| Complete | Complete marks a finished grouped DNS response. | |
| Review Output | Review Output marks missing, empty, or inconsistent record groups. | |
| Open Help | Open Help opens this guide from the DNS Overview panel. |