DNS Record Refuses to Update Via API
I have several DNS records for my domain as well as an api key which is utilized by an instance of ddclient running on my firewall to facilitate ip address updates. These all work fine, until last night.
I added two new records for new services I was spinning up, the first worked without issue, the second one was giving me grief. In the course of troubleshooting the later I deleted and re-added the DNS record from the Cloudflare dashboard. From that moment on nothing I have done has allowed that DNS record to update it's ip via api.
I have confirmed it is being pointed to the wrong IP via dig, which is also what is shown on the CF dashboard.
The ddclient logs show that the api responded that the record in question already had the current address and that no change should/would be made.
I have removed and re-added the record from both cloudflare and ddclient.
I have confirmed that the other records are being correctly updated by ddclient via api.
I have re-rolled the api key.
I have rebooted the firewall appliance.
I have tried working with the A"I" support chat from Cloudflare.., up until which I thought that rage-quit videos were attention seeking schemes meant to increase channel views. My, now defunct, old keyboard, wall, and hand would now disagree.
I don't know how this gets fixed without intervention from someone at CF, but apparently since I only pay them in a registrar capacity I can't open a support ticket related to DNS.
I added two new records for new services I was spinning up, the first worked without issue, the second one was giving me grief. In the course of troubleshooting the later I deleted and re-added the DNS record from the Cloudflare dashboard. From that moment on nothing I have done has allowed that DNS record to update it's ip via api.
I have confirmed it is being pointed to the wrong IP via dig, which is also what is shown on the CF dashboard.
The ddclient logs show that the api responded that the record in question already had the current address and that no change should/would be made.
I have removed and re-added the record from both cloudflare and ddclient.
I have confirmed that the other records are being correctly updated by ddclient via api.
I have re-rolled the api key.
I have rebooted the firewall appliance.
I have tried working with the A"I" support chat from Cloudflare.., up until which I thought that rage-quit videos were attention seeking schemes meant to increase channel views. My, now defunct, old keyboard, wall, and hand would now disagree.
I don't know how this gets fixed without intervention from someone at CF, but apparently since I only pay them in a registrar capacity I can't open a support ticket related to DNS.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Was this page helpful?
