Bug #12761
closed
Input validation prevents configuring wildcard Dynamic DNS records on Google Domains
100%
Description
Copy of Bug #12750 but with Google Domains selected, gives same error. Apparently bug has been around for 2+ years, but most people have gotten around by using subdomain and then assigned a CNAME in DNS to main domain.
Updated by Viktor Gurov almost 3 years ago
- Assignee set to Viktor Gurov
- Target version set to CE-Next
- Plus Target Version set to 22.05
- Affected Version set to 2.6.0
Updated by Jim Pingle almost 3 years ago
- Status changed from New to Pull Request Review
- Target version changed from CE-Next to 2.7.0
Updated by Viktor Gurov almost 3 years ago
- Status changed from Pull Request Review to Feedback
Updated by Jim Pingle over 2 years ago
- Status changed from Feedback to New
Something in that commit has broken Namecheap DDNS and likely others. For Namecheap it fails to load the password properly and it fails to recognize that the username is not required. As a result, saving the entry fails.
If I back out 728608824e8fa11acadaac35e46b0d7e2a865870 I can save existing entries without error.
Updated by Jim Pingle over 2 years ago
Looks like it was only the Namecheap username that was the problem. The definition in the new code was wrong. I pushed a fix which appears to work for my own entries. I double checked the other types and the only one that didn't match on old and new behavior was Namecheap so this should be OK now.
Updated by Jim Pingle over 2 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset e92dded8cbe2e1eb8037b4156255bd603d82958e.
Updated by Jim Pingle over 2 years ago
- Subject changed from Dynamic DNS bug with Google Domains wildcard to Input validation prevents configuring wildcard Dynamic DNS records on Google Domains
Updating subject for release notes.