Bug #12761
closed
Input validation prevents configuring wildcard Dynamic DNS records on Google Domains
Added by Ma Ar almost 3 years ago.
Updated over 2 years ago.
Plus Target Version:
22.05
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.
- 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
- Status changed from New to Pull Request Review
- Target version changed from CE-Next to 2.7.0
- Status changed from Pull Request Review to Feedback
- 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.
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.
- Status changed from New to Feedback
- % Done changed from 0 to 100
- 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.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF
Updated by Viktor Gurov 
Updated by