This guide explains PTR lookup results and when reverse DNS is useful for a public DC++ hub address.
Usage
- Open Reverse DNS and enter a public IP address, hostname, or hub URL in Host Or Address.
- Select Check Reverse DNS.
- Compare the resolved public address with its returned PTR hostname.
Concrete Example
A hub named hub.example.net may resolve to a VPS address whose PTR is server-42.provider.example. That generic provider name can be valid. A PTR that still names the previous host is useful evidence for a provider support ticket.
Interpretation
The address owner controls PTR delegation. A matching forward and reverse name can improve operational clarity, but it is not required for most Direct Connect hubs. A generic provider hostname identifies infrastructure, not the hub operator.
Troubleshooting
- No PTR: Ask the hosting provider whether reverse DNS is available.
- Stale Name: Update PTR in the provider panel or support request.
- Several Addresses: Test the exact public address used by clients.
- PTR Exists, Hub Fails: Continue with DNS Overview, TCP Connect, and Protocol Test.
Icon Reference
| Icon | Label | What It Does |
|---|---|---|
| Check Reverse DNS | Check Reverse DNS submits the public target for PTR lookup. | |
| Complete | Complete marks a finished reverse lookup. | |
| Review Output | Review Output marks a missing or notable PTR response. | |
| Open Help | Open Help opens this guide from the Reverse DNS panel. |
Comments
No Comments Yet. Start The Conversation.