Navigation

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

    Dynamic DNS Client for Route 53 ipv6

    DHCP and DNS
    3
    7
    875
    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.
    • V
      vc6SfV8 last edited by

      I am trying to use the Dynamic DNS Client for Route 53, but can't seem to get it to update ipv6 addresses.  I've checked all documentation and can't find anything that says this isn't supported.  Does anyone know if it is/isn't or how to get it working?

      Thanks!
      Ryan

      1 Reply Last reply Reply Quote 0
      • JKnott
        JKnott last edited by

        Why do you even need dynamic DNS for IPv6?  You should have static, MAC based addresses you point the DNS at.  I've been using IPv6 for 7 years and never had a need for dynamic DNS.

        1 Reply Last reply Reply Quote 0
        • V
          vc6SfV8 last edited by

          I use charter which issues DHCP Ipv6 addresses.  They change all the time. :(

          1 Reply Last reply Reply Quote 0
          • JKnott
            JKnott last edited by

            @vc6SfV8:

            I use charter which issues DHCP Ipv6 addresses.  They change all the time. :(

            Do you have "Do not allow PD/Address release" on the WAN tab selected?

            1 Reply Last reply Reply Quote 0
            • V
              vc6SfV8 last edited by

              Yes.  I imagine this is not uncommon.  It appears numerous Dynamic DNS clients in pfSense support IPv6.  I am uncertain why Route53 doesn't.  (Maybe it does, but I am selecting something incorrectly..)

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

                I (re)wrote most of the r53.class that appears in 2.3.4 and at the moment it only supports IPv4 addresses. Adjusting the code to support AAAA records is the setting of a variable instead of a hard-coded A. The real work is all of the hooks into dyndns.class to support a Route53 IPv6 flavor, which is work that hasn't been done yet. I was thinking about doing it, but haven't had the time yet.

                1 Reply Last reply Reply Quote 0
                • V
                  vc6SfV8 last edited by

                  @ink:

                  I (re)wrote most of the r53.class that appears in 2.3.4 and at the moment it only supports IPv4 addresses. Adjusting the code to support AAAA records is the setting of a variable instead of a hard-coded A. The real work is all of the hooks into dyndns.class to support a Route53 IPv6 flavor, which is work that hasn't been done yet. I was thinking about doing it, but haven't had the time yet.

                  That explains it, thank you.  At least that means I am not doing something wrong.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post

                  Products

                  • Platform Overview
                  • TNSR
                  • pfSense
                  • Appliances

                  Services

                  • Training
                  • Professional Services

                  Support

                  • Subscription Plans
                  • Contact Support
                  • Product Lifecycle
                  • Documentation

                  News

                  • Media Coverage
                  • Press
                  • Events

                  Resources

                  • Blog
                  • FAQ
                  • Find a Partner
                  • Resource Library
                  • Security Information

                  Company

                  • About Us
                  • Careers
                  • Partners
                  • Contact Us
                  • Legal
                  Our Mission

                  We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                  Subscribe to our Newsletter

                  Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                  © 2021 Rubicon Communications, LLC | Privacy Policy