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

Unbound forwarding mode incompatible with dns64-prefix custom option

Scheduled Pinned Locked Moved DHCP and DNS
3 Posts 2 Posters 731 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.
  • I
    IsaacFL
    last edited by Feb 12, 2019, 5:16 PM

    This is probably an Unbound issue.

    Using Unbound in the Resolver mode (Enable Forwarding Mode unchecked)

    Under custom options, add:

    module-config: "dns64 validator iterator"
    dns64-prefix: 2001:67c:27e4:1064::/96
    

    This will turn on DNS64 in unbound. You will see that ipv4 only addresses are now given an AAAA record.

    If you then go to the resolver and check "Enable Forwarding mode", you will get the following error message:

    The following input errors were detected:
    
        The generated config file cannot be parsed by unbound. Please correct the following errors:
        /var/unbound/test/unbound.conf:111: error: syntax error
        read /var/unbound/test/unbound.conf failed: 1 errors in configuration file
    
    

    I don't know if this is a pfSense issue or Unbound.

    1 Reply Last reply Reply Quote 0
    • J
      jimp Rebel Alliance Developer Netgate
      last edited by Feb 13, 2019, 3:45 PM

      You need to put server: on a line before your custom options to ensure they are in the proper context. It's in the docs. It worked by chance before because your options just happened to land in the server context, but when you enable forwarding, they end up after that which is in a different place.

      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      I 1 Reply Last reply Feb 13, 2019, 5:10 PM Reply Quote 2
      • I
        IsaacFL @jimp
        last edited by Feb 13, 2019, 5:10 PM

        @jimp said in Unbound forwarding mode incompatible with dns64-prefix custom option:

        server:

        This fixed it!

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