Pfsense dynamic dns not updating
At “Username” and “Password“, specify your username (username is required for all types except Namecheap and Free DNS) and password.
At “Description“, enter an appropriate description. Then press the “Save” button to save the settings and, on the next page, press “Apply Changes” to apply the changes if necessary. If the cached IP is green then the hostname was successfully updated.
In this ways I can recall my local servers/devices using their assigned names in the domain and I can have a local cache to very quickly resolve the names for the sites I use more often.
Of course I have a local GNU/Linux server that will be used for this and I used BIND9 to setup the DNS server.
This is where you add details about your DNS zone as well as the key to update BIND9.
To this end, many providers offer commercial or free DDNS service for this scenario, with reconfiguration generally implemented in the user’s router or computer.
The client will automatically update the dynamic host each time the WAN IP changes or every 25 days.
You probably want to make sure your client is connecting to the service, since some providers will remove inactive hosts if they have not been updated for 30 days.
The Web is full of articles on how to setup BIND9 on different GNU/Linux distributions so I will not cover this topic at all.
What, on the contrary, I found a little bit more complicted to do (not too much to be honest, but still worth to talk about) is how to have a DHCP server running on a different hardware to update the DNS entries everytime a new device asks for an IP.