-
Notifications
You must be signed in to change notification settings - Fork 492
GANDI: dns records with uppercase characters aren't respected #3581
Description
Describe the bug
Unable to modify dns records in gandi containing uppercase characters via dnscontrol.
To Reproduce
Steps to reproduce the behavior:
- Setup API for GANDI
- Setup an A record for your domain containing a capital letter e.g.
demoV3. - Attempt to modify the record with a dnsconfig.js file e.g.
demoV3 xx.xx.xx.24 -> xx.xx.xx.80 - ./dnscontrol push
- See 500 error
#1: ± MODIFY demov3.xxx.org A (xx.xx.xx.24 ttl=10800) -> (xx.xx.xx.80 ttl=10800)
FAILURE! {Code:0 Message: UUID: Object: Cause: Status: Errors:[]}: StatusCode: 500 ; Err: 500: The server has either erred or is incapable of performing the requested operation.
Expected behavior
I would expect the dns record to be updated, no 500 error.
DNS Provider
- GANDI_V5
Additional context
From testing it seems to be that by the time requests are being put to the gandi api uppercase characters have been transformed to lower case. The same 500 errors can be seen if you have a dns record such as demoV3 and attempt to modify to local rules relating to demov3 (as opposed to demoV3) in a .js file.
My assumption is that the capitals are being transformed before they hit the GANDI api - however it's also possible that the GANDI api simply doesn't respect upper case characters.
Either way I believe it's the mismatch of requests attempting to modify demov3 and the actual record in gandi being demoV3 which is causing the issue.