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

    After reboot, the DNS resolver must be restarted before it will advertise the ipv6 address of the resolver

    Scheduled Pinned Locked Moved
    IPv6
    4
    15
    1.0k
    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.
    • IsaacFLI
      IsaacFL @Derelict
      last edited by

      @Derelict said in After reboot, the DNS resolver must be restarted before it will advertise the ipv6 address of the resolver:

      There is nothing I can think of in DNS resolver that has anything to do with configuring the router advertisements for IPv6.

      If it were me, I would get it into the broken state and packet capture for the router advertisements on the inside interfaces (which is where the clients will get their DNS servers using SLAAC). and see what they contain.

      Diagnostics > Packet Capture
      Interface: LAN (or whatever the inside interface is)
      Address Family: IPv6 only
      Host address: ff02::1
      Count: 100000 or something

      Let it run for a while and stop it.

      Wireshark will dissect that for you and you can look for the Recursive DNS Server options in the Router Advertisements.

      I used to run completely unmanaged and never had any issues, nor am I aware of any issues elsewhere.

      Or post the pcap file here.

      Not sure how to post the pcap files here. Upload file gives error message.

      ![0_1564336503033_packetcapture - prior reboot.cap](Uploading 100%)

      ![0_1564336555916_packetcapture - after reboot.cap](Uploading 100%)

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        No idea. Maybe try without a bunch of spaces in the filenames.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        IsaacFLI 1 Reply Last reply Reply Quote 0
        • IsaacFLI
          IsaacFL @Derelict
          last edited by

          @Derelict Had to rename .cap to .pcap

          packetcapture-prior-reboot.pcap

          packetcapture-after-reboot.pcap

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            Don't know what to tell you. .cap is a valid extension.

            packetcapture.cap

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            IsaacFLI 1 Reply Last reply Reply Quote 0
            • PippinP
              Pippin
              last edited by

              /me can not upload .cap too .....
              https://forum.netgate.com/topic/138124/posting-to-a-forum-issue

              I gloomily came to the ironic conclusion that if you take a highly intelligent person and give them the best possible, elite education, then you will most likely wind up with an academic who is completely impervious to reality.
              Halton Arp

              1 Reply Last reply Reply Quote 0
              • IsaacFLI
                IsaacFL @Derelict
                last edited by

                @Derelict It is pretty easy to reproduce. You just have to create an environment where the unbound does not get automatically restarted. Then you notice the ipv6 DNS problems after rebooting. Restarting the unbound service manually fixes it.

                My configuration:

                DHCPv6 Server is Disabled. RA is Unmanaged.

                Unchecked Resolver, DHCP Registration.

                1 Reply Last reply Reply Quote 0
                • DerelictD
                  Derelict LAYER 8 Netgate
                  last edited by

                  It did not used to be allowed. The .cap extension was added recently.

                  Chattanooga, Tennessee, USA
                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

                  1 Reply Last reply Reply Quote 0
                  • DerelictD
                    Derelict LAYER 8 Netgate
                    last edited by

                    OK. Guess that's the case then. I'd open a bug report at https://redmine.pfsense.org/ detailing the steps to reproduce, the expected behavior, and the observed behavior.

                    Chattanooga, Tennessee, USA
                    A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                    DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                    Do Not Chat For Help! NO_WAN_EGRESS(TM)

                    IsaacFLI 1 Reply Last reply Reply Quote 0
                    • IsaacFLI
                      IsaacFL @Derelict
                      last edited by

                      @Derelict I created Bug #9654

                      1 Reply Last reply Reply Quote 0
                      • DerelictD
                        Derelict LAYER 8 Netgate
                        last edited by

                        Cool. That is the channel to get the developers (I am not one) to look at it.

                        Chattanooga, Tennessee, USA
                        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                        Do Not Chat For Help! NO_WAN_EGRESS(TM)

                        1 Reply Last reply Reply Quote 0
                        • ?
                          A Former User
                          last edited by A Former User

                          Hi

                          Just wanted to add also saw this issue during an upgrade from 2.4.4_3 to 2.4.5, I had previously unchecked "Register DHCP leases in the DNS Resolver" due to loads of restarts on the DNS Resolver service. On upgrading to 2.4.5 (I think unrelated to the upgrade, it was just because of the restart) I found an issue with my VoIP phone over IPv6 failing to register. Various trouble shooting later I ended up testing from a Windows PC using NSLOOKUP which picked up the DNS server on the IPv6 address but it was timing out and returning no results.

                          A Goggle brought me here, so as per OP I restarted the DNS Resolver and NSLOOKUP started returning addresses, and low and behold the VoIP phone registered back up. So definitely a bug somewhere.

                          Regards

                          Phil

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