Erratic behaviour regarding updating aliases by hostname
-
I have to use Track Interface because of dynamic IPv6. For an inbound firewall rule on WAN I use an alias as destination which should be updated by the DHCPv6 server on LAN via hostname. This is working for IPv4 but not for IPv6, the table only shows the IPv4-adress. Sometimes it works but most of the time it doesn't.
-
My DHCP IPv6 server setup :
and because the 5.xxx.43.182 is a classic bind domain name server that manages (example) "mypsense-internal-network-name.net" (I rent that domain name) I can see the zone of "mypsense-internal-network-name.net", all my devices that use IPv6 are registered with the correct IPv6.
I can see the bind logs that show the updates coming from the DHCPv6 server of pfSense, it seems to work well. I have to say , my IPv6 prefix didn't change over the last year ... I've just checked : they are all up to date.
The same setup for IPv4 doesn't make any sense, as registering 192.168.1.8 = dvr.mypsense-internal-network-name.net" in a public accessible domain name server is ... useless.
edit : my domain name server runs on a dedicated server somewhere, in a datacenter in Paris. Not behind pfSense are locally.
-
@Gertjan Your usecase is "dynamic-DNS". I wish pfSense would let you do what you did but with the DDNS-Clients onboard.
My usecase is a host-alias for firewall rules, which can be private IPs for v4. And it has worked in the past, now it only works partially.
