-
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
Not actually failing over. #5
Comments
@MostHated i've not actually tested this is great detail. DNS failover happens at the application level where multiple A records are provided. I created this simple project for development use, I wouldn't use this in production without spending some time testing it. |
Unfortunately, this is the only node dns app I can find that does failover at the application level, I was hoping to run it on an external DigitalOcean.com droplet as a standalone DNS server and use it for failover between our 2 locations and dual fiber lines. You do not happen to know of any that are tested well and known to work, do yo? |
@MostHated not for NodeJS - it's easy enough to write a decent one in Python or Java however. There are a few good libraries too in those languages. |
Alrighty, well I appreciate the information and can appreciate the work you put into this. Thanks! |
Hello,
I was hoping to use this for my current project, but I am having an issue with the IP not failing over to the next. The primary IP for each site is working just fine, but then I tried to change the primary IP to something random that was non-responsive in order to see if it would fail over to the second IP, but have had no such luck. The only thing I have changed is that I moved the entries to their own file so that I could easily add and manage several of them. It is pulling them just fine it seems, as I mentioned, the primary IP of each domain works well.
Thanks,
The text was updated successfully, but these errors were encountered: