Register IPv6 in DNS Resolver with only RA enabled

Bob.Dig

@backmup For dynamic GUAs you really should use DHCPv6.

BackMup

@bob-dig

I was afraid you going to say that ;-)

But which option?

Manged isn't a good option as Android wouldn't get addresses, right?
Assisted would take the ipv6 from DHCPv6 and additonal config like RDNSS from RA? Would that mean Androids are getting no IPv6 again?
Stateless DHCP would still assign IPv6 via RA and addtional config would come from DHCPv6?

That's how I understand it. Which melts down to "Assisted" or do I miss here something bigger?

Thanks for your help!

Bob.Dig

@backmup You only need a name if you run a server on it, so I wouldn't need one for my phone, no problem there.

Assisted is good and android gets an IP but no name.

JKnott

@bob-dig said in Register IPv6 in DNS Resolver with only RA enabled:

For dynamic GUAs you really should use DHCPv6.

The problem with that is Android devices won't work with it.

BackMup

@bob-dig
True, for the clients it's not that important.
I will give it a try with Assisted.

JKnott

@bob-dig said in Register IPv6 in DNS Resolver with only RA enabled:

Assisted is good and android gets an IP but no name.

The other side of this is how often will this be needed? All my devices are listed in host overrides. I just had to do it once.

Bob.Dig

@backmup The reason you don't need a name for clients is, every machine has many IPv6 addresses, only one of those has a name, the rest has none anyways, so the name is only good for a server to reach and according firewall rules to allow a connection but not good for blocking a machine via rules.

Bob.Dig

@jknott said in Register IPv6 in DNS Resolver with only RA enabled:

@bob-dig said in Register IPv6 in DNS Resolver with only RA enabled:

Assisted is good and android gets an IP but no name.

The other side of this is how often will this be needed? All my devices are listed in host overrides. I just had to do it once.

Your prefix is very undynamic then.

BackMup

@bob-dig
Basically you're right but it's just such a clash in my mind. In the IPv4 world you can define all the names of clients and in the IPv6 you can't (at least not with RA only).
But well, maybe I need to cut the strings and release the "old" thinking.

BackMup

@bob-dig
For GUA, it wouldn't work but that's also not really the aim. ULA should be fine and ULA doesn't change that much ;-)

JKnott

@backmup said in Register IPv6 in DNS Resolver with only RA enabled:

But well, maybe I need to cut the strings and release the "old" thinking.

Or maybe you can convince Google to stop listening to that idiot who thinks Android shouldn't support DHCPv6. That where the problem lies. He doesn't like it, so Android doesn't support it.

JKnott

@backmup said in Register IPv6 in DNS Resolver with only RA enabled:

and ULA doesn't change that much

My GUA hasn't changed for years and has survived replacing both my cable modem and the computer I run pfSense on. However, ULA is useful, if your ISP doesn't provide a consistent prefix.

Bob.Dig

@jknott Yep, for "reasons" I do NAT IPv6 to ULA for my email server and have given up using IPv6 for the rest...

JKnott

@bob-dig

Why do you use NAT? You can have both GUA and ULA on the same interface.

Bob.Dig

@jknott Because GUA with a dynamic prefix is problematic, especially for hosts that don't get notified that the prefix has changed. So for now, only pfSense has to know for its WAN interface. That does work better, as long as pfSense is the first router.