Bug #9276
closed
DNS troubleshooting tool incorrectly reporting "ai." as an invalid hostname
100%
Description
To reproduce:
Navigate to Diagnostics=>DNS Lookup (found at /diag_dns.php). Enter any TLD that should work as a single-label domain, "ai." for example. Include the terminating dot that indicates you mean an FQDN. This is a valid hostname. You will get a response saying otherwise.
I have tested this on 2.4.4-RELEASE-p1 and -p2. It is not an issue with ubound. Using dig at a command line does show the hostname (with terminating dot) to resolve just fine. The problem is at the diagnostic feature web page.
Files
Updated by Jim Pingle over 5 years ago
- Assignee set to Jim Pingle
- Target version set to 48
- Affected Version set to All
Looks like it's easily fixed by having the validation check ignore a trailing dot on the hostname, but including it in the query.
Updated by Jim Pingle over 5 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset e56c473d7c4c2e7de71c43420c844e452dbcfa82.
Updated by Vladimir Lind about 5 years ago
On 2.4.5-DEVELOPMENT (arm)
built on Fri Jan 25 05:46:46 EST 2019
Entered "ai.: in Diagnostics=>DNS Lookup and got response -> 209.59.119.34 A
Looks good.
Updated by Jim Pingle about 5 years ago
- Status changed from Feedback to Resolved
Updated by Jim Pingle almost 5 years ago
- Target version changed from 2.5.0 to 2.4.4-p3
Updated by Jim Pingle almost 5 years ago
- Status changed from Resolved to Feedback
Updated by Chris Linstruth almost 5 years ago
2.4.4-p3
Diagnostics > DNS Lookup accepts ai. as a hostname and returns valid results. Ran a couple other queries - all fine.
Updated by Jim Pingle almost 5 years ago
- Status changed from Feedback to Resolved