No DNS-resolution after going to "unbound"
    Ewald Jenisch 
    a at jenisch.at
       
    Tue Mar 25 10:34:18 UTC 2014
    
    
  
Hi,
Since by default FreeBSD 10 uses "unbound" as standard DNS-server I
wanted to set up my system (FreeBSD 10, 64bit with kernel/system
current as per Mar 19) to run a local caching DNS-server using
unbound.
So I went ahead and proceeded as per
https://wiki.freebsd.org/WhatsNew/FreeBSD10 which in turn points to
http://blog.des.no/2013/09/local-caching-resolver-in-freebsd-10/ i.e.
# echo local_unbound_enable=yes >>/etc/rc.conf
# service local_unbound start
As a result my /etc/resolv.conf has 
nameserver 127.0.0.1
options edns0
which seems correct and 
# sockstat -4 | grep unbound
unbound  unbound    3719  5  udp4   127.0.0.1:53          *:*
unbound  unbound    3719  6  tcp4   127.0.0.1:53          *:*
# 
and /etc/unbound/unbound.conf is
# Generated by local-unbound-setup
server:
        username: unbound
        directory: /var/unbound
        chroot: /var/unbound
        pidfile: /var/run/local_unbound.pid
        auto-trust-anchor-file: /var/unbound/root.key
        verbosity: 1
include: /var/unbound/forward.conf
# 
However whatever name I try to resolve doesn't work:
# ping www.cisco.com
ping: cannot resolve www.cisco.com: Host name lookup failure
#
# drill www.cnn.com
;; ->>HEADER<<- opcode: QUERY, rcode: SERVFAIL, id: 46336
;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; www.cnn.com. IN      A
;; ANSWER SECTION:
;; AUTHORITY SECTION:
;; ADDITIONAL SECTION:
;; Query time: 126 msec
;; SERVER: 127.0.0.1
;; WHEN: Tue Mar 25 11:29:39 2014
;; MSG SIZE  rcvd: 29
#
BTW - no firewall etc. in place, just set up the Box from scratch,
updated kernel/system and then wanted to switch to a local caching
DNS-server using unbound.
Has anybody out there experienced the same problems? Any known cure
against it?
Thanks much in advance for any clue,
-ewald
    
    
More information about the freebsd-questions
mailing list