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

Reverse lookup for unbound conditional forwarder?

DHCP and DNS
3
5
3.8k
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.
  • G
    gjaltemba
    last edited by Mar 21, 2015, 9:46 PM

    I have 2 pfsense routed with a conditional forwarder in unbound to each domain but reverse lookup only works for the local domain. How done?

    1 Reply Last reply Reply Quote 0
    • J
      johnpoz LAYER 8 Global Moderator
      last edited by Mar 24, 2015, 4:14 AM

      yeah going to need a bit more detail.. And example of what your doing and what is not working would be very helpful in helping you.

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.11 | Lab VMs 2.7.2, 24.11

      1 Reply Last reply Reply Quote 0
      • G
        gjaltemba
        last edited by Mar 25, 2015, 2:52 PM

        Thank you for your help with my setup of reverse lookup for unbound conditional forwarder.

        Background
        I have 2 pfsense running with traditional lan wan opt1 interface, unbound. and dhcpd. They are subnet 192.168.1.0/24 and 192.168.2.0/24. Domain names are localdomain1 and localdomain2. Opt1 is a gateway with default route to the other pfsense's lan address. On localdomain1, hosts can resolve by name and ip for localdomain1.

        Problem
        localdomain1 unbound has domain override for localdomain2. Hosts on localdomain1 can resolve localdomain2 hosts by name but not by ip.

        Example
        On localdomain1,
        nslookup pfsense.localdomain2 answers 192.168.2.1
        nslookup 192.168.2.1 answers

        ** server can't find 1.2.168.192.in-addr.arpa: NXDOMAIN

        1 Reply Last reply Reply Quote 0
        • P
          phil.davis
          last edited by Mar 26, 2015, 1:02 AM

          You need to also put a domain override for the reverse-lookup names:
          168.192.in-addr.arpa

          to point to the internal DNS server that knows the reverse-lookup zone.

          As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
          If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

          1 Reply Last reply Reply Quote 0
          • G
            gjaltemba
            last edited by Mar 26, 2015, 1:55 AM

            That's the ticket. Reverse lookup works now.

            1 Reply Last reply Reply Quote 0
            3 out of 5
            • First post
              3/5
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.