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

    DHCPv6 DDNS settings and native unbound DNS

    Scheduled Pinned Locked Moved IPv6
    5 Posts 3 Posters 2.7k 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.
    • G
      gnhb
      last edited by

      I'd like to set up DDNS under my DHCPv6 options on pfSense.

      I can't find any documentation about linking these options to pfSense unbound.

      How is this designed to work?

      I'm on 2.3-RELEASE
      ![Screen Shot 2016-05-09 at 8.43.02 AM.png](/public/imported_attachments/1/Screen Shot 2016-05-09 at 8.43.02 AM.png)
      ![Screen Shot 2016-05-09 at 8.43.02 AM.png_thumb](/public/imported_attachments/1/Screen Shot 2016-05-09 at 8.43.02 AM.png_thumb)

      1 Reply Last reply Reply Quote 0
      • I
        Inq
        last edited by

        Pfsense implements ISC dhcpd as a dhcp server. It's no surprise that is designed to work best with ISC bind. I doubt you can do ddns with unbound in pfsense.

        The problem with making something idiot proof is that the world keeps making better idiots.

        1 Reply Last reply Reply Quote 0
        • G
          gnhb
          last edited by

          What are people using for IPv6 DDNS?

          Is there a way to provide DNS lookup of local hosts IPv6 address as a service in pfSense at all?

          1 Reply Last reply Reply Quote 0
          • MikeV7896M
            MikeV7896
            last edited by

            I'm pretty sure that unless it's done from the host's end, dynamic DNS isn't possible with DHCPv6. The reason is because the hostname isn't sent back to the DHCPv6 server. The only way you'll get a hostname to appear in your DHCPv6 leases is if it's a static DHCPv6 entry.

            The S in IOT stands for Security

            1 Reply Last reply Reply Quote 0
            • I
              Inq
              last edited by

              It's possible. Just not with the exposed pfsense gui. Here are some logs after some heavy editing in dhcpd6.conf (rog is a W10 client):

              bind debug log

              
              client 2a02::1#23748/key dhcp_updater: updating zone 'example.com/IN': update unsuccessful: rog.example.com: 'name not in use' prerequisite not satisfied (YXDOMAIN)
              client 2a02::1#23748/key dhcp_updater: updating zone 'example.com/IN': deleting rrset at 'rog.example.com' DHCID
              client 2a02::1#23748/key dhcp_updater: updating zone 'example.com/IN': adding an RR at 'rog.example.com' DHCID AAIB6pZPrA7zoDg1s+EYgl0GGo0yjS0hKNuiDIcN0lyFMHs=
              client 2a02::1#23748/key dhcp_updater: updating zone 'example.com/IN': deleting rrset at 'rog.example.com' AAAA
              client 2a02::1#23748/key dhcp_updater: updating zone 'example.com/IN': adding an RR at 'rog.example.com' AAAA 2a02::b9c7
              
              

              Pfsense dhcpd log:

              
              May 13 08:33:57 srv dhcpd: Sending Reply to fe80::4854:ff3c:xxxx:xxxx port 546
              May 13 08:33:57 srv dhcpd: Added new forward map from rog.example.com to 2a02::b9c7
              May 13 08:33:57 srv dhcpd: Added reverse map from 7.c.9.b.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.a.2.ip6.arpa. to rog.example.com
              May 13 08:33:58 srv dhcpd: Renew message from fe80::4854:ff3c:xxxx:xxxx port 546, transaction ID 0xA7A3900
              May 13 08:33:58 srv dhcpd: Reply NA: address 2a02:::b9c7 to client with duid 00:01:00:01:1d:4e:73:c9:10:bf:xx:xx:xx:xx iaid = 51429192 valid for 1920 seconds
              
              ``` 
              
              Updated zone record:
              

              $TTL 600 ; 10 minutes
              rog A 10.0.200.7
              AAAA 2a02::b9c7
              DHCID ( AAIB6pZPrA7zoDg1s+EYgl0GGo0yjS0hKNuiDIcN0lyF
              MHs= ) ; 48819 13 32

              
              The problem is that the pfsense dhcpd server is very picky about dhcp clients. I couldn't register any apple ios device in ipv6 ddns zone. On the other hand i had no problems with a HP printer. ISC dhcp 4.3.4 might fare better.

              The problem with making something idiot proof is that the world keeps making better idiots.

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