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

    Localhost IPv6 added as resolver after 24.11 upgrade

    Scheduled Pinned Locked Moved General pfSense Questions
    8 Posts 4 Posters 423 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.
    • J
      jim82
      last edited by

      Hi all,

      After upgrading my system to 24.11, ::1 was added as a resolver to my list of DNS servers (see screenshot).

      I'm not using IPv6 and have followed the guidelines to block/disable it on these forums.

      How can I remove it from the resolver list?

      Thanks
      /Jim

      6f060ae3-e2ef-4131-b95c-d89a0b92b6df-image.png

      Best regards
      Jim

      Still learning, correct me if I'm wrong please.

      GertjanG 1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        It's harmless and only local to the device. While you can block IPv6 there is no way to disable it completely in the OS, and it's necessary in certain cases.

        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!

        J 1 Reply Last reply Reply Quote 0
        • GertjanG
          Gertjan @jim82
          last edited by Gertjan

          @jim82 said in Localhost IPv6 added as resolver after 24.11 upgrade:

          How can I remove it from the resolver list?

          Yes !
          A forum user known as johnpoz showed how to do that, or in any case this week.

          edit : Humm can't find it.

          It was something like this :

          c5216336-e4c3-4ad0-b861-b73b866a4a44-image.png

          the idea is : normally the perfect two (127.0.0.1 and ::1) are present, except if you define your own, like the image shows.

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

          J 1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            You have to set the 'DNS Resolution Behavior' to Use Remote Servers only so it doesn't add localhost automatically too.

            J 1 Reply Last reply Reply Quote 0
            • J
              jim82 @jimp
              last edited by

              @jimp Thanks a lot, then I will just leave it as is :)

              Best regards
              Jim

              Still learning, correct me if I'm wrong please.

              1 Reply Last reply Reply Quote 0
              • J
                jim82 @Gertjan
                last edited by

                @Gertjan Many thanks for showing me the workaround. I tried and it's a viable option.

                Best regards
                Jim

                Still learning, correct me if I'm wrong please.

                GertjanG 1 Reply Last reply Reply Quote 0
                • J
                  jim82 @stephenw10
                  last edited by

                  @stephenw10 Thanks a lot for your reply. It works.

                  Best regards
                  Jim

                  Still learning, correct me if I'm wrong please.

                  1 Reply Last reply Reply Quote 0
                  • GertjanG
                    Gertjan @jim82
                    last edited by Gertjan

                    @jim82 said in Localhost IPv6 added as resolver after 24.11 upgrade:

                    it's a viable option

                    But limited in time.
                    I'm like everybody else, I saw IPv6 coming, and thought back then (early 2000) : "wow, that's something my kids have to deal with, IPv4 rocks, works fine, and I've other things to do".
                    Now, its 2024. Every OS on planet earth will use initially IPv6, and if that doesn't work out, it will fall back to IPv4 if available.
                    Read again what I've just said. For every connection that is created, this decision step is taken.

                    True, not every ISP offers a IPv6 connection. Lets presume most do now. And if they do, chances are the connection is pretty broken in the way they implemented it "not as it should be". (RFCs are clear, but they are like us : don't want to learn new things, and, it costs them $โ‚ฌ)
                    We've seen this already happening ones, when IPv4 went mainstream for 'everybody', when ISPs were created. It took a decade or so for IPv4 as a connection method became a no-brainer. These days, it works out of the box, with much knowledge needed.

                    Anyway, if you can, make IPv6 work. deal with it now. Our kids have already enough problems to deal with, like flooding, overheated planet and so on ๐Ÿ˜Š

                    No "help me" PM's please. Use the forum, the community will thank you.
                    Edit : and where are the logs ??

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