Project

General

Profile

Bug #9276

DNS troubleshooting tool incorrectly reporting "ai." as an invalid hostname

Added by Steve Malloy 3 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Very Low
Assignee:
Category:
Web Interface
Target version:
Start date:
01/17/2019
Due date:
% Done:

100%

Estimated time:
Affected Version:
All
Affected Architecture:
All

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.

Associated revisions

Revision e56c473d (diff)
Added by Jim Pingle 3 months ago

Allow a trailing dot in a hostname on diag_dns.php. Fixes #9276

Revision 2cc24f95 (diff)
Added by Jim Pingle 3 months ago

Allow a trailing dot in a hostname on diag_dns.php. Fixes #9276

(cherry picked from commit e56c473d7c4c2e7de71c43420c844e452dbcfa82)

History

#1 Updated by Jim Pingle 3 months 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.

#2 Updated by Jim Pingle 3 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#3 Updated by Vladimir Lind 3 months 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.

#4 Updated by Jim Pingle 3 months ago

  • Status changed from Feedback to Resolved

#5 Updated by Jim Pingle about 1 month ago

  • Target version changed from 48 to 2.5.0

Also available in: Atom PDF