Re: Using bind for a local caching name server, is this configuration correct?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 5 Jul 2019 17:49:11 -0700
Samuel Sieb <samuel@xxxxxxxx> wrote:

> Because you didn't ask it.  You need to use @127.0.0.1

$ 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: 33696
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: f6efe6837c0ec785830c77a65d2345ab25f6d7cc67762264 (good)
;; QUESTION SECTION:
;rootusers.com.                 IN      A

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Jul 08 06:31:23 MST 2019
;; MSG SIZE  rcvd: 70


>From the current named.conf,
options {
  listen-on port 53 { 127.0.0.1; };
//  listen-on-v6 port 53 { ::1; };
  forwarders  { 192.168.0.1; };

So, it should be forwarding resolve queries to the router, which has no
problem resolving the request.  

$ dig rootusers.com @192.168.0.1

; <<>> DiG 9.11.8-RedHat-9.11.8-1.fc31 <<>> rootusers.com @192.168.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3131
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;rootusers.com.                 IN      A

;; ANSWER SECTION:
rootusers.com.          1800    IN      A       104.24.126.122
rootusers.com.          1800    IN      A       104.24.127.122

;; Query time: 84 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Mon Jul 08 06:31:59 MST 2019
;; MSG SIZE  rcvd: 74

$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4
localhost4.localdomain4 
::1         localhost localhost.localdomain
localhost6 localhost6.localdomain6

> It definitely looks that way.  Just change your router's DNS to
> forward to what you want instead of the one it gets from your ISP.
> Then you don't have to change anything on your computer.  Much
> simpler and it works for everything on your network.

That is essentially what I have done, though I had to set the
connection to not provide dns service with the dhcp address, and set the
dns to be the router address.  That still doesn't provide caching, the
original purpose of setting up named as a caching nameserver, so I will
use dnsmasq or knot-resolver.  Done with named.
_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux