• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

DNS resolver broken again

Scheduled Pinned Locked Moved DHCP and DNS
2 Posts 2 Posters 411 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B
    billmcg
    last edited by billmcg Jan 8, 2019, 1:58 AM Jan 8, 2019, 1:55 AM

    I routinely have this problem and its driving me crazy.

    I can resolve a particular name from the diagnostics on my pfense box, but from internal machines it doesn't resolve.

    I'm running DNS resolver with DNS Query forwarding. It seems to be intermittent too. Last time I posted about this the problem resolved itself a half an hour later. I'm getting so that I don't trust the dns resolver.

    Is there some issue where it won't return addresses in private IP ranges?

    billm@spy:~>dig rancher.***.com
    
    ; <<>> DiG 9.10.6 <<>> rancher.***.com
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8480
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;rancher.***.com.		IN	A
    
    ;; Query time: 7 msec
    ;; SERVER: 192.168.223.254#53(192.168.223.254)
    ;; WHEN: Mon Jan 07 17:48:41 PST 2019
    ;; MSG SIZE  rcvd: 50
    

    This is obsured but it totally resolves correctly from the pfsense box itself. WTF?

    Oh...
    https://www.netgate.com/docs/pfsense/dns/dns-rebinding-protections.html

    1 Reply Last reply Reply Quote 0
    • D
      Derelict LAYER 8 Netgate
      last edited by Derelict Jan 8, 2019, 3:37 AM Jan 8, 2019, 3:35 AM

      Sounds like you might have forwarding on and DNSSEC enabled and are forwarding to forwarders that don't properly forward the DNSSEC forwarding.

      This is obsured but it totally resolves correctly from the pfsense box itself. WTF?

      Yes. Unless you set the domain as a private domain in unbound it will not return RFC1918 answers to queries.

      Chattanooga, Tennessee, USA
      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
      Do Not Chat For Help! NO_WAN_EGRESS(TM)

      1 Reply Last reply Reply Quote 0
      1 out of 2
      • First post
        1/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received