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

    FAILOVER DHCP problems registering Hostnames

    Scheduled Pinned Locked Moved
    DHCP and DNS
    3
    8
    4.2k
    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.
    • A
      alopez
      last edited by

      Hi,

      Recently instaled two boxes of pfsense with CARP that works fine. I only have a problem with dhcp registering hostnames at dns. If one host receives an IP when box1 is master, DNS resolves the local IP correctly, but if the cluster changes to the second node, then the IP of that host is not resolved.

      It seems a problem of ddns syncronitation between the two nodes, because all of other things as lease table, firewall rules, static routes, Virtual IP, etc synchronizes correctly

      Could you help me?

      Coud you show me a correct configuration of a failover dhcp that works fine.

      I am triyng this with version 1.0.1 and then updating to 1.2-RC3 but the problem persists

      Thank you

      1 Reply Last reply Reply Quote 0
      • S
        sullrich
        last edited by

        This would be a bug.  Please open a ticket at cvstrac.pfsense.com and assign it to me.

        1 Reply Last reply Reply Quote 0
        • A
          alopez
          last edited by

          Ok, I did it

          pfSense - Ticket #1553

          Rgds

          1 Reply Last reply Reply Quote 0
          • A
            alopez
            last edited by

            Hello,

            Is there something new about this problem? (Ticket 1553 at cvstrac)

            Rgds

            1 Reply Last reply Reply Quote 0
            • S
              sullrich
              last edited by

              No, please be patient.

              1 Reply Last reply Reply Quote 0
              • A
                alopez
                last edited by

                Hello,

                I see that version 1.2 stable is released. Is there this bug corrected in this version? I will upgrade my old 1.0.1 inmediatly.

                Thanks

                1 Reply Last reply Reply Quote 0
                • H
                  hoba
                  last edited by

                  Looks like it won't be fixed before 1.3 as it's assigned to branch RELENG_1: http://cvstrac.pfsense.org/tktview?tn=1553,6

                  1 Reply Last reply Reply Quote 0
                  • A
                    alopez
                    last edited by

                    Ok, thank you very much

                    :)

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