Hi everyone,
I noticed that connecting to the web UI I have an inconsistency, with a local IPv6 address being added as secondary DNS, somehow. Anyone has an explaination?
Page 1: (no secondary DNS, “IPv4 only” setting enabled)
Page 4: (Secondary DNS as IPv6)
I noted that after a reboot, the page has only the primary DNS enabled, then after awhile the IPv6 thing appears. Go figure 
Raffaele
That’s the IPv6 local link address :-
fe80::/10 – Addresses in the link-local prefix are only valid and unique on the local subnet. This address range is comparable to the auto-configuration addresses 169.254.0.0/16 of IPv4.
I don’t see it on my NSC-222 or Mu-so V1.
It would be handed out by your router via the IPv6 router advertisement process rather than the DHCP V6 process unlike DHCP V4.
Interestingly, the Router has DHCP enabled but IPv6 disabled, as well as the MuSo 2 has IPv4 only flag set.
I’d have assumed no IPv6 would ever reach the device. An auto-configuration address for the DNS endpoint would make no sense to me; would be as the IP of the device failing auto-discovery, but as DNS is puzzling. As well is puzzling it appears only in one page, and not the other.
Thanks for your reply!
Update: Feels like a known ‘feature’ in the latest firmware release of my Router that the DNSv6 protocol cannot be disabled, so it will push IP addresses of itself as DNS for both V4 and V6 even if the latter is disabled.
Probably the MuSo2 supports both and receive the IP address of the router in V6 and V4 formats; I hope it will prefer the V4, otherwise connection will be broken.
I came into this as I found lately that time to time the device was disconnecting from the network becoming no more discoverable, and this started in line with the new firmware update to the router (that had V6 disabled by default, before). The only way to bring it online is to reset/power off, so it may be linked to IP lease - setting a fixed IP did not helped, so I’m now testing the “IPv4 only” flag
