On Fri, 2019-07-05 at 12:00 -0700, stan via users wrote:
Why doesn't the bind/named server forward the name for resolution
to
the router that is its forwarder?
From your recent command line tests, you appear to have missed a step
to prove that (you queried the router, and tried to query DNS servers
on the WWW, but didn't query your own router).
There's many ways BIND can be configured, not all of them will act in
the way you've been hoping. Though nothing jumps out at me from your
initial posting with your named.conf file, other than have you changed
the named.conf forwarders from the unreachable 1.1.1.1 and 9.9.9.9 to
your router IP?
Subsequent posts show that things are still trying to use IPv6, and
you've said your network can't support it. So you do want to disable
IPv6 activity. That should get some of the failures out of the way.
I think these results means that it is the router that is doing the
filtering rather than the ISP. True?
It looks that way. It could be due to firewalling at the router, that
may be user-configurable. If your router has any parental filtering
features, switch them off. And check your computer's firewall, again.