Ok. According to the manual "Do not use the system nameservers option if you have a multi-WAN setup and have Unbound running alongside multiple DNS servers configured in General with separate gateways assigned to them. Unbound will use the locally created routes to reach the system nameservers, which will not work when the gateway is down."
I guess adding nameservers to System: Settings: General is not the way or does it mean if I have selected separate gateways for each nameserver?
Anyway, I have added 1.1.1.1 and 1.0.0.1 as custom forwarding in "query forwarding". Tried both with and without nameservers put in (system-settings-general). I also added a firewall rule on WAN: IPv4 TCP/UDP, source this firewall, destination any on DNS port 53, as some have suggested. Same problem still occurs, domains work for about 10 secs than dns stops working.
I guess adding nameservers to System: Settings: General is not the way or does it mean if I have selected separate gateways for each nameserver?
Anyway, I have added 1.1.1.1 and 1.0.0.1 as custom forwarding in "query forwarding". Tried both with and without nameservers put in (system-settings-general). I also added a firewall rule on WAN: IPv4 TCP/UDP, source this firewall, destination any on DNS port 53, as some have suggested. Same problem still occurs, domains work for about 10 secs than dns stops working.
"









