DHCPv6 Doesnt provide DNS Interface
-
Hi there,
all of my interfaces have an IPv6 Address with configured DHCPv6 but the DNS Server (interface intself) doesnt come with the DNS-Settings.
Do I miss a step somewhere?
-
(I do) not need for :
I'm not using the Resolver as a forwarder anyway.
Who is 172.16.24.113 ?
Neither here :
I've no DNS servers mentioned here :
Note that
Leave blank to use the system default DNS servers - this interface's IP if DNS Forwarder or Resolver is enabled, otherwise the servers configured on the General page
Your Resolver is enabled, right ? It should communicate " the interface's IP (v6) " of the LAN of pFsense.
So, on my PC, it has a IPv6 DNS : the pfSense LAN IPv6 interface :
Btw :
This :
Means that you have no IPv6 support on that pfSense LAN from pfSEnse.
See my image for real data.You have to give a valid (== you have to have the right to use) IPv6 network :
Normally, the IPv6 /64 network is part of a bigger IPv6 block assigned to you by your ISP.
on your LAN interface.
-
@gertjan i managed to fix this by my own.
It was the Windows 11 what didnt get the DNS. The 172.16.24.113 in my subnet is the DNS Server because i host different servers at home i need my own dns with my own domain.But its fixed now. So no worries.
-
Is there some reason you're using DHCPv6? Android doesn't support it, so if you have any Android devices you'll have to use SLAAC. You can thank some genius at Google for that one.
-
@jknott maybe i missunderstand this point but im using SLAAC with Stateless DHCPv6:
Event Android doesnt support it, SLAAC still works.
-
According to that image, you're using DHCPv6 on the LAN side and the topic title says the same thing. I use Unmanaged here, which provides SLAAC. There's also an option to provide DNS addresses with RDNSS, which is part of the Router Advertisement.
-
@jknott as I said this setting work for me perfectly.
