Project

General

Profile

Bug #3568

DynDNS: Hostname '@' not accepted for Namecheap

Added by Anonymous over 4 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Category:
Dynamic DNS
Target version:
Start date:
04/04/2014
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.1
Affected Architecture:
All

Description

When you try to create a dynamic DNS entry for '@' as per Namecheap's DNS configuration, pfSense gives an error "The Hostname contains invalid characters."

Associated revisions

Revision de29dadc (diff)
Added by Renato Botelho almost 4 years ago

Allow hostname to start with '@.' for namecheap. It fixes #3568

Revision 9ec8e1f2 (diff)
Added by Renato Botelho almost 4 years ago

Allow hostname to start with '@.' for namecheap. It fixes #3568

History

#1 Updated by Renato Botelho almost 4 years ago

  • Assignee set to Renato Botelho
  • Target version set to 2.2

#2 Updated by Renato Botelho almost 4 years ago

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

#4 Updated by Anonymous almost 4 years ago

Works great now, thanks Renato! Feel free to mark this one as resolved.

#5 Updated by Renato Botelho almost 4 years ago

  • Status changed from Feedback to Resolved

#6 Updated by Robert Qbik over 3 years ago

As you can see there:
https://www.namecheap.com/support/knowledgebase/article.aspx/597/10/how-can-i-set-up-a-catchall-wildcard-subdomain

If you want to add wildcard, you must type *.yourdomain.com, it's not working in pfSense because of "The Hostname contains invalid characters."

Can you fix this also ?

#7 Updated by Kill Bill almost 3 years ago

Robert Qbik wrote:

If you want to add wildcard, you must type *.yourdomain.com, it's not working in pfSense because of "The Hostname contains invalid characters."
Can you fix this also ?

https://github.com/pfsense/pfsense/pull/1914

Also available in: Atom PDF