DDNS IPv6 Cloudflare
-
@johnpoz When I go to Diag/table it will only say 192.168.1.30
But why? Why can't I input the same for IPv6 there. -
And where do you think it gets that from?? U2 is not a FQDN it can not resolve... you have it in your host file on pfsense.. or you append the domain to it when you query it...
Do you have IPv6 there... I can resolve any fqdn I want for ipv6...
-
@johnpoz So who put the 192.168.1.30 in that table? Where originated it? Why can't I do the same thing for IPv6?
-
Here
there is no ipv4 for pfsense, but there is a pfsense.local.lan IPv6 entry in my resolver host override... So when I tell ping to ping that host via ipv6 it gets the IPv6 address..
-
@johnpoz So my question is this, it is working for IPv4, tested it.
FQDN also works.
Why is it not working for IPv6?
-
Because its not int he TABLE!!!!
Where do you think its going to magically come up with that IPv6 address???
-
@johnpoz The same way it got not magically the IPv4 in that table.
How can I achieve that? I have the feeling it could be a bug, but little do I know. -
Its not freaking magic... You have that address in your host file... See mine has IPv6 for pfsense and nothing for pfsense IPv4 - so it doesn't resolve IPv4..
Put in a IPv6 address in your host file via host override!
Your lack of understanding does not = bug!
-
@johnpoz So I have not willingly or knowingly put it in a host file for IPv4. When does pfSense this and why it didn't happened for IPv6 also?
I think it is a bug. The bug is that the alias is taking no hosts or FQDN for IPv6, only for IPv4.
2.4.4-RELEASE-p3 -
Dude this is not rocket science --- here I turned on ipv6 via dhcp6 on my client.... Setup a static entry for it - bing bang soom there you go host name is in the host file, both fully qualified and just host..
So pfsense can not resolve it with just host name
Having your client register its dns name can be done via the dhcpv6 setup or the client into pfsense...
-
@johnpoz Could you do me a favor by creating an hostname or FQDN IPv6 Alias in pfSense and making a screenshot?
I have my names in DHCP and DNS Resolver already.
-
In my ongoing "battle" with DDNS and dynamic prefixes I was able to get a "RFC 2136 Client" in pfSense working with dynv6.com. The "normal" DDNS-Client in pfSense for dynv6 wouldn't work for me.
Anyway, what it allows me, is to have a prefix on an interface in the DNS. Together with static interface identifiers (host part), like you can have in pfSense with DHCPv6 Static Mappings on an interface which tracks IPv6-WAN, now the hosts have a working DDNS, because the changing prefix get registered in DNS, not only in pfSense.
dynv6.com even allows you to use your own sub-domain via delegation, which I did.
