Dns rebounder not working



  • The rebounder isnt performing dns services, can any1 guide me thru the process of checking if its not configured properly?

    Thnx in advance for any reply.


  • LAYER 8 Global Moderator

    rebounder??  What is that?  You mean resolver unbound?

    Is the service running?  What is it not doing, does it not resolve local, does it not resolve multiple domains, specific one.  Does it give you a timeout when your clients query, does it send back SERVFAIL.  What is in the logs?

    Is this a clean install, upgrade, you switch from the forwarder to resolver?  Something to work with is required to help you pinpoint the source of your problem.



  • Sorry yea, I mean dns resolver, I keep forgetting they changed the name of it.
    Yes, dns resolver service is running, and the DHCP server is configured to use "this interface IP" for dns lookups, but dns resolver isnt caching or responding to any dns requests.

    This is not a clean install, is an upgrade.



  • When I try to use the dns resolver everything just times out.
    This happens on all my devices thats set to use pfsense dns resolver.

    This site can’t be reached

    viaplay.se’s server DNS address could not be found.
    ERR_NAME_NOT_RESOLVED

    ![dns resolver2.jpg](/public/imported_attachments/1/dns resolver2.jpg)
    ![dns resolver.jpg](/public/imported_attachments/1/dns resolver.jpg)
    ![dns resolver.jpg_thumb](/public/imported_attachments/1/dns resolver.jpg_thumb)
    ![dns resolver2.jpg_thumb](/public/imported_attachments/1/dns resolver2.jpg_thumb)


  • LAYER 8 Global Moderator

    It was never called rebounder ;)

    The resolver walks down from roots and talks to each name server down the tree until it actually queries the authoritative server for the domain your wanting to query a specific record, etc.

    So depending what your isp does, or what your blocking say in front of pfsense if you can not talk directly to name servers then yeah resolver is never going to work.

    From your stats there doesn't seem like your even seeing any queries to it.. Are your clients able to talk to pfsense on 53 udp?  You notice for example mine

    May 22 06:51:21 unbound 21699:0 info: server stats for thread 1: 5006 queries, 1763 answers from cache, 3243 recursions, 154 prefetch

    Curious why you have dpinger off?  And depending how your using pfblocker it not running could cause you dns troubles.

    Have you edited your default lan rules?  Common mistake is only allow tcp, when dns requires UDP.  Can you query pfsense IP for something that should be local, like its own name.. Use your fav dns query tool, nslookup, dig, drill, host, etc.  shoot even a simple ping for pfsense host name should return its ip.

    
    user@ubuntu:~$ dig pfsense.local.lan
    
    ; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> pfsense.local.lan
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55046
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;pfsense.local.lan.             IN      A
    
    ;; ANSWER SECTION:
    pfsense.local.lan.      3600    IN      A       192.168.9.253
    
    ;; Query time: 3 msec
    ;; SERVER: 192.168.9.253#53(192.168.9.253)
    ;; WHEN: Tue May 24 08:01:01 CDT 2016
    ;; MSG SIZE  rcvd: 62
    
    user@ubuntu:~$
    
    

Log in to reply