DynDNS and Dual-wan problem with CloudFlare (works with No-Ip)
-
I have a simple setup with dual-wan links and dynamic IPs. I use a No-ip Round Robin setup like this
WAN1FailsToWAN2 -> my.hostname.com@gw1 WAN2FailsToWAN1 -> my.hostname.com@gw2
where
WAN1FailsToWAN2
is a gateway group withGW_WAN
on Tier 1 andGW_WAN2
on Tier 2WAN2FailsToWAN1
is a gateway group withGW_WAN2
on Tier 1 andGW_WAN
on Tier 2my.hostname.com
is my No-Ip hostnamegw1
andgw2
are labels I set up in No-Ip hostname when I selected the "RoundRobin" type.
And, for years now, this have been working flawlessly:
a) If both links are up a
nslookup my.hostname.com
returns both public IP addresses (WAN1 and WAN2).
b) If WAN1 link is down anslookup my.hostname.com
returns only WAN2 public IP address.
c) If WAN2 link is down anslookup my.hostname.com
returns only WAN1 public IP address.The update is very quick (less than 1 minute). Everything is good.
Problem is: This doesn't work with a CloudFlare domain. In the event of a link down, the unreachable IP address is not removed from the CloudFlare dns record.
Like No-Ip, Cloudflare supports RoundRobin hostnames. However, unlike No-Ip, Cloudflare doesn't have "labels" for each record.
When one of the links is down, I can see (via "Dynamic DNS Status" widget on main pfSense page) that the link change was detected by pfSense and that CloudFlare hostname was updated with only the working IP address. However a
nslookup my.hostname.com
shows me that the unreachable IP address was not removed. -
No comments from devs?
Nobody else trying to use CloudFlare DynDns with Multi-Wans?
Is this the appropriate place to report this problem?
-
A DNS server is a computer server that contains a database of public IP addresses and their associated hostnames, and in most cases serves to resolve, or translate error, those names to IP addresses as requested. DNS server not responding run special software and communicate with each other using special protocols.