Dynamic DNS - IP failing to update
-
I now have a somewhat stable, (but still changes every month or so) IP address. My IP address changed, but the Dynamic DNS failed to update the Cloudflare IP address.
I don't understand the documentation as it is written - can someone please clarify the following for me:
Is the Dynamic DNS Client stand alone, or is a Check IP Services client necessary?
If so, do I need to host my own server, or is there a public server that this client can use with the Check IP Service?
-
@guardian said in Dynamic DNS - IP failing to update:
Is the Dynamic DNS Client stand alone, or is a Check IP Services client necessary?
The Services > Dynamic DNS > Dynamic DNS Clients pfSense functionality is a DDNS client.
It uses the default Services > Dynamic DNS > Check IP Services = http://checkip.dyndns.org (click on the link, you can see it work).
You didn't tell how you are connected to the Internet : does your pfSense WAN interface uses a modem type of device, so pfSense has the 'real' WAN IPv4 ? Or do you use an upstream ISP router, so your WAN IPv4 interface uses a RFC1918 kind of IPv4 ?
The first case : Your WAN IP changes, this means the pfSense WAN IPv4 changes.
When the 'new' WAN interface IPv4 is "loaded into the NIC" (the WAN interface) all related services are restarted. This includes the DDNS pfSense service. It will compare the new WAN IPv4 with the one in kept in a file. If it's the same, nothing happens and nothing needs to be updated. If it's different, it will use the 'DDNS access method' (you use Cloudflare) to communicate the new WAN IPv4.
DDNS is like any remote service : you need to show who you are = use the access credentials which gives you access to your Cloudflare account. Just like a mail account, Netflix access etc etc.The second setup needs more assistance (fully automated, though), as the pfSense WAN IP doesn't change, it will always keep the same TFC1918, but your upstream ISP router might have changed it WAN IPv4 IP.
Install the (imho : mandatory) pfSense Cron package, and you can see how it is done :
Every hour (and 1 minute), the pfSense DDNS client service will check for you (using [http://checkip.dyndns.org) what your 'real' WAN IPv4 is.
If it's not the one it kept in a fie on a safe place, it will processed with updating as mentioned above.@guardian said in Dynamic DNS - IP failing to update:
I don't understand the documentation as it is written
What documentation ?
You've created an (DDNS) account with Cloudflare ? This account should give you an URL, or user access code and/or password. These are need to initialize the settings on the pfSense side.Some examples : Cloudflare DNS with pfSense
When reading all these, be ware that a newer pfSense version might introduce changes.
Cloudflare also can (and will) change the way how things are done.Cloudfalre has a massive outage yesterday - see your classic news outlets - and here on this forum.
Btw : I'm not using Cloudflare myself, and my ISP never changes my IPv4, it's the same for the last 2 years now (same for the IPv6 prefixes). I still have an DDNS service, just in case of, as it's very bad practice to use the words 'ISP' and 'never' in the same phrase.
-
Yup Cloudflare was having all sorts of issues yesterday. Are you still seeing this today?
