Project

General

Profile

Actions
Copy link

Bug #6122

closed
TS JP

Hostname Field for NameCheap Dynamic DNS Rejects "@"

Bug #6122: Hostname Field for NameCheap Dynamic DNS Rejects "@"

Added by Trel S over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
Dynamic DNS
Target version:
2.3.1
Start date:
04/12/2016
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3
Affected Architecture:

Description

The hostname field for NameCheap in dynamic DNS is rejecting the "@" character.

Error Below:
The following input errors were detected:

The hostname contains invalid characters.

Expected Behavior: Allow the "@" character in the hostname field.

Files

namecheap-host-fix-6122.patch (693 Bytes) namecheap-host-fix-6122.patch Jim Pingle, 04/13/2016 09:32 AM

TS Updated by Trel S over 10 years ago Actions
Copy link
 #1

Affected Version: 2.3 release.

JP Updated by Jim Pingle over 10 years ago Actions
Copy link
 #2

Attached patch should fix it, waiting on confirmation since none of my domains on Namecheap are setup in such a way that I can update using @ safely.

TS Updated by Trel S over 10 years ago Actions
Copy link
 #3

With that patch applied, it accepted the "@" symbol for the hostname.

Additionally, I confirmed that it correctly updated the correct record at NameCheap.

JP Updated by Jim Pingle over 10 years ago Actions
Copy link
 #4

Thanks for the confirmation, I just pushed the fix

JP Updated by Jim Pingle over 10 years ago Actions
Copy link
 #5

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

Applied in changeset commit:7cb8fabc6ed56e4d182c662350d9e2f65a492d2d.

CB Updated by Chris Buechler over 10 years ago Actions
Copy link
 #6

  • Status changed from Feedback to Resolved

works

Actions
Copy link

Also available in: Atom