Related

Tool Instant DNS Lookup Tool Tool
[NEW] Bandwidth Pricing Calculator Tool
DNS problems in CentOS 6.5 Question Question
How do I set up a single subdomain to point to my droplet? Question Question

Question

How to know if all DNS have switched to the floating IP upgrade?

Posted September 15, 2016 2k views
NetworkingDNS

Hi all!

Added a floating IP to the server A, everything working and looking good.
Next step would be changing our DNS record to point to the floating IP instead of pointing to the droplet IP.

We expected the networking charts of the droplet to let us discern traffic from both IP’s, but all we get is an aggregate traffic (I think/hope!).

How could we discern when it is “safe” to assume that every DNS in the world have replicated and all traffic is flowing through the floating IP, so we can float it to the new (upsized and updated) replicated server B?

Add a comment
infern0
By:
infern0
Add a comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer
ryanpq September 15, 2016

If you are using the DigitalOcean DNS then it’s already updated. We run a very very low TTL and our DNS records are proxied via CloudFlare. DNS changes are quick enough that we recommend using FloatingIPs with tools like heartbeat as a high-availability solution implementing failover.

In this situation it would be possible to set up two virtualhosts in your web server to listen on the public ipv4 address and on the floating ip’s anchor IP. The anchor IP is the IP address your droplet sees the floating IP interface as. You can get your anchor IP with:

curl -s http://169.254.169.254/metadata/v1/interfaces/public/0/anchor_ipv4/address

If you set up two virtualhosts you can have them log visits to different files making it easy to know when requests to one stop.

How To Create a High Availability Setup with Heartbeat and Floating IPs on Ubuntu 14.04
by Mitchell Anicas
Heartbeat is an open source program that provides cluster infrastructure capabilities—cluster membership and messaging—to client servers, which is a critical component in a high availability (HA) server infrastructure. Heartbeat is typically used in conjunction with a cluster resource manager (CRM), such as Pacemaker, to achieve a complete HA setup. However, in this tutorial, we will demonstrate how to create a 2-node HA server setup by simply using Heartbeat and a DigitalOcean Floating IP.
Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help