On Sat, 06 Jul 2019 10:47:26 +0930
Tim via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> 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).
$ dig rootusers.com @127.0.0.1
; <<>> DiG 9.11.8-RedHat-9.11.8-1.fc31 <<>> rootusers.com @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 63917
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: c1c3426a72f01e7bff3ec2cd5d23536f093aaa28fbe35249 (good)
;; QUESTION SECTION:
;rootusers.com. IN A
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Jul 08 07:30:07 MST 2019
;; MSG SIZE rcvd: 70
>
> 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?
Yes, I did so.
options {
listen-on port 53 { 127.0.0.1; };
// listen-on-v6 port 53 { ::1; };
forwarders { 192.168.0.1; };
# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4
localhost4.localdomain4
::1 localhost localhost.localdomain
localhost6 localhost6.localdomain6
> 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.
It's disabled in the dhcp server in the router, and I have it set to
ignore in the connection. Where else would I turn it off? Actually, I
think these are the authorative servers being queried from the named
server, part of the includes in named.conf.
> 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.
The firewall explicitly allows dns in both router and firewalld.
I'm done with this. Pounding my head against the wall is a waste of
time. I'll use dnsmasq or knot-resolver to get caching from the router
being used as dns.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
