Bug #9053
closed
Dynamic DNS will not allow Route 53 wildcard record
100%
Description
When configuring a dynamic DNS client to update Route 53 (AWS) records, the web form will not validate a hostname that contains a wildcard character, e.g.: "*.example.com". Creating A-records with wildcard characters is allowed in Route 53.
Additionally, creating a dynamic DNS client for "example.com" and enabling the "wildcards" option will not update the record with a literal wildcard, in this case, "*.example.com"
The expected behavior is that a hostname with a wildcard character would be allowed, given that it's a perfectly valid DNS record in Route 53.
Updated by Tom Embt over 5 years ago
https://github.com/pfsense/pfsense/pull/4038
It seems to me the wildcard checkbox is intended for providers that offer a canned dynamic DNS product, where adding a wildcard entry is basically a feature toggle. For providers such as AWS Route53 which are full featured DNS providers, the sensible approach seems to be to just put the wildcard in the hostname literally (which currently fails validation as described).
- hide wildcard and MX checkboxes since neither are used by the Route53 code
- update the call to is_domain() to have a truthy second argument, allowing wildcards for route53 and route53-v6
Tested working for me with wildcards on IPv4 and IPv6 both at the top of the zone and farther down.
Updated by Renato Botelho almost 5 years ago
- Status changed from New to Feedback
- Assignee set to Renato Botelho
- Priority changed from High to Normal
- Target version set to 2.5.0
- % Done changed from 0 to 100
PR has been merged. Thanks!
Updated by Jim Pingle over 4 years ago
- Target version changed from 2.5.0 to 2.4.5
Updated by Tom Embt over 4 years ago
Tested in a current snapshot of 2.4.5 and was able to create a Route53 wildcard entry