Azure Dynamic DNS w IPv6 address
-
Using the great notes in this other post Azure Dynamic DNS setup help I was able to get my Dynamic DNS updating to Azure DNS just fine for IPv4.
PFSense thinks my IPv6 addresses are updating correctly (shown in green on the status, log says IP address changed successfully) but in Azure they are showing up as blank (a hyphen to be exact). The updates do indeed hit Azure as they wipe out any IPv6 address I have manually entered into Azure. Any tips for using IPv6 with Azure for Dynamic DNS?
-
This:
https://redmine.pfsense.org/issues/9248
Guess I will wait patiently for the next release. -
Why do you need dynamic DNS for IPv6? Normally, your addresses shouldn't change.
-
The short answer is I don’t. IPv4 works just fine.
The long answer is that each time the router reboots, it’s IPv6 changes (Spectrum residential cable internet).
-
@mhab12 said in Azure Dynamic DNS w IPv6 address:
The short answer is I don’t. IPv4 works just fine.
The long answer is that each time the router reboots, it’s IPv6 changes (Spectrum residential cable internet).
Go to the WAN page and ensure "Do not allow PD/Address release" is selected.
-
@mhab12 I see the pull request for the fix has been merged. Does anyone have a date when that may find its way into a release?
-
With the fix completed, you could use the System Patches package to apply the commit URL below as a patch to pfSense. It will patch the appropriate file and allow things to work while waiting for the official update. Once the update containing the fix is released (it looks like it will be part of 2.5.0, so it might be a while), you can revert the patch before performing the update to ensure all updates just fine.
https://github.com/pfsense/pfsense/pull/4064/commits/1ca156ea0875014b5175855c9fe8459950173d0b
I added this as a patch to my 2.4.4p3 pfSense box and it's now successfully updating my IPv6 hosts in my Azure DNS.
Now if only I could use @ as a hostname in pfSense to properly update the default entry for the domain.
-
@virgiliomi It's working here too. Thanks for your help!
-
@virgiliomi PS: "@" is a valid Name for A and AAAA records but I see that Dynamic DNS is calling it invalid. I don't see a good reason to block its use but maybe one exists. Perhaps you can post it as an issue on the GitHub project and see what you hear back.
-
I would imagine the reason is because some of the services don't allow you to use @ (especially traditional dynamic DNS services that need a specified hostname, as opposed to actual full DNS services). So their check is for the lowest common denominator. Whether or not they could change the logic to allow it for some services and not others would probably be a more significant effort, especially in the homework to find out whether each service permits the use of @ as a hostname or not. However with more traditional DNS services - Azure, Route 53, and the like - being present in the service list these days, it might be worth it.
There is a workaround in creating an actual hostname, then using @ as an alias for that hostname... but kinda annoying.
