Closed ohitstom closed 2 years ago
What are your full logs? (Unredacted please, except for credentials)
Thanks, that's helpful.
You have an A record named tompc.tk
within your tompc.tk
zone. That looks like a mistake: tompc.tk.tompc.tk
.
It probably should be @
.
This doesn't appear to be an issue with this module, so I'll close this issue.
Whenever i type in @ for the name it sets it to tompc.tk tompc.tk does resolve to tompc.tk tompc.tk.tompc.tk does not
Does Cloudflare let you use .tk domains with their API? I've heard that they have restrictions on what you can do with .tk. What happens if you try a more "normal" domain?
I dont really have access to another domain, and seeing as it can change the ip regardless i wouldnt see why its a limitation. Are you sure i havent setup my api key incorrectly as per the screenshots in the original issue?
I don't really know, tbh. I use this plugin with Cloudflare and it works fine for me :no_mouth: I'd recommend debugging the actual API response by putting some log.Printlns in the code or something like that.
Did it actually update the DNS record properly though? Looks like it still worked.
It is updating the record, just thinks its wrong at startup... By any chance could i have a pic of your dns setup so i can compare? obviously with ip etc taken out.
Nevermind, it works regardless so theres no need, the added check at startup really doesnt effect anything anyways
On startup it says:
domain not found in DNS {"domain": "@"}
then says theres a different ip address even if there isnt. If i set the dns to something other than the servers ip, it is correctly setting it, but seems to be triggering when it doesnt need to.my config is below:
IMAGE
A | url.tk | public_ip | Proxied | Auto -- | -- | -- | -- | --