gamliela:
And this is when it's turned on (and when the problem occurs):
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : 94-DE-80-B0-B0-DA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fd84:4765:979a:d00:8ac9:b0ce:655f:f3b(Preferred)
Temporary IPv6 Address. . . . . . : fd84:4765:979a:d00:8c7b:d767:d487:517a(Preferred)
Link-local IPv6 Address . . . . . : fe80::502d:d445:a8ca:5fcd%14(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.11(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, 7 August 2023 8:13:55 pm
Lease Expires . . . . . . . . . . : Tuesday, 8 August 2023 8:13:54 pm
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 244637312
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-28-D2-F7-12-94-DE-80-B0-B0-DA
DNS Servers . . . . . . . . . . . : fe80::1%14
192.168.1.1
192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Note the "fe80::1%14" address in the DNS server, I suspect this is the culprit.
Those fd84:: IPv6 addresses are in the fc00::/7 range which is for "unique local unicast" addresses. Those addresses are to be used for creating a local IPv6 network that does not connect to the Internet - they are not routeable, and traffic from them will be dropped by any Internet router. So that is a problem if they are being used. I have no idea why such IPv6 addresses have been assigned, but that is clearly wrong.
The fe80::1%14 address for the DNS server is potentially valid - it is a link local IPv6 address and that sort of address is what is frequently used to route packets to a next hop router, which in this case is likely to be your gateway router. If that router is a DNS server or DNS relay, as home Internet routers often are, the configuration would work. The %14 on that address is the interface number for the interface to be used for that fe80::1 address. Your posted data shows that interface is the one that goes to your gateway router, and the ::1 device ID says it is is likely the address of your gateway router. So it should work. To test if it actually works as a DNS server, run a command like this:
nslookup 8.8.8.8 fe80:1%14
If you get back a reply, then it is working. The results should be the same as you get from:
nslookup 8.8.8.8 192.168.1.1
