-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple A records being created for same subdomain #18
Comments
I am unable to reproduce this, if you can provide an example set of commands that can reproduce it I can have a look overwise from my end everything seems to be working fine. |
Could this happen if I have multiple instances of command in parallel? |
I am fairly certain multiple instances could result in this behaviour, however they would have to be pointing at the same zone and record. This however is a limitation of Netlify. The technical explanation as to why is that Netlify DNS records are idempotent (can't be changed), hence this project finds and delete the old record and then creates a new one every time it detects your IP address has changed. Theoretically, if you had two instances of the app running at the same time and they ran the update at the same time (highly unlikely but possible) they could run both send the delete command (although one of them would possibly fail) and then both create a new record. |
Alright, I think this might have happened |
Can you see anything in the console output of |
Just checkd my syslog. Doesn't seem to look like they is an error. TBH I'm not too sure if this would logged anyway. I actually had a cron every 5 minutes, not after reboot. Sorry!
|
@neugartf You might want to deactivate and change your access token as it's visible in the screenshot. |
@rahul003 Thanks for the warning! 🤗 |
@neugartf I don't do any validation of the arguments so that I don't introduce any issues if my validation logic doesn't match Netlify's but when I get some time I might make the app exit if the first update upon startup fails. This should prevent the loop as you have found above and act as a way to use Netlify to validate the arguments. |
How do I prevent multiple records from being created? I'm running like this. This only happens some times. Unable to figure out when it replaces the IP vs when it creates a new entry
NDDNS_IPv6_ENABLED=false /sgt/projects/dyndns/nddns_Linux_Arm64 --accesstoken `cat /sgt/projects/dyndns/netlify.key` --zone $DOMAIN.com --record $rec --interval 0
The text was updated successfully, but these errors were encountered: