Navigation

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

    Unbound Error: Address already in use…when using Cloudflare config

    DHCP and DNS
    5
    7
    1704
    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
      gsmornot last edited by

      Searching did not find much for this error, any ideas? Quad9 does not have this issue, it is (for me) only when I use Cloudflare in my DNSResolver config.

      Apr 16 14:15:19 unbound 57988:1 error: outgoing tcp: connect: Address already in use for 2606:4700:4700::1001
      Apr 16 13:51:29 unbound 57988:1 error: outgoing tcp: connect: Address already in use for 1.1.1.1
      Apr 16 11:23:57 unbound 57988:0 error: outgoing tcp: connect: Address already in use for 2606:4700:4700::1111
      Apr 16 11:18:07 unbound 57988:0 error: outgoing tcp: connect: Address already in use for 1.1.1.1
      Apr 16 10:49:35 unbound 57988:1 error: outgoing tcp: connect: Address already in use for 2606:4700:4700::1001
      Apr 16 07:59:54 unbound 57988:0 error: outgoing tcp: connect: Address already in use for 1.1.1.1

      The config I am using at the moment:
      server:
      include: /var/unbound/pfb_dnsbl.*conf
      forward-zone:
      name: "."
      forward-ssl-upstream: yes
      forward-addr: 1.1.1.1@853
      forward-addr: 1.0.0.1@853
      forward-addr: 2606:4700:4700::1111@853
      forward-addr: 2606:4700:4700::1001@853

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

        Did you uncheck forwarder in Resolver Settings?

        Home Server "Gandalf":  unRAID Pro 6 | MB**:**  ASUS Z9PE-D8 WS | CPU:  Dual Xeon E5-2670 | RAM:  64GB Crucial PC-1600 ECC

        1 Reply Last reply Reply Quote 0
        • M
          MoonKnight last edited by

          Hi,

          I have the same in my log.

          --- 23.01 ---
          Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
          Kingston DDR4 2666MHz 16GB ECC
          2 x HyperX Fury SSD 120GB (ZFS-mirror)
          2 x Intel i210 (ports)
          4 x Intel i350 (ports)

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

            @NeoDude:

            Did you uncheck forwarder in Resolver Settings?

            Yes. I have not used the forward option.

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

              I’m getting this now too:

              Apr 18 06:13:35 unbound 56170:1 error: SSL_handshake syscall: Connection reset by peer
              Apr 18 06:12:44 unbound 56170:1 error: SSL_handshake syscall: Connection reset by peer
              Apr 18 06:12:23 unbound 56170:1 error: SSL_read syscall: Connection reset by peer

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

                Also seeing this!

                Apr 13 08:56:26 unbound 77728:4 error: outgoing tcp: connect: Address already in use for 1.1.1.1
                Apr 13 08:56:33 unbound 77728:3 error: outgoing tcp: connect: Address already in use for 1.0.0.1
                Apr 14 10:21:28 unbound 77728:3 error: outgoing tcp: connect: Address already in use for 1.0.0.1
                Apr 15 13:16:32 unbound 77728:2 error: outgoing tcp: connect: Address already in use for 1.1.1.1
                Apr 15 19:39:52 unbound 77728:2 error: outgoing tcp: connect: Address already in use for 1.1.1.1
                Apr 15 22:26:56 unbound 77728:4 error: outgoing tcp: connect: Address already in use for 1.1.1.1
                Apr 16 19:31:21 unbound 77728:2 error: SSL_read syscall: Connection reset by peer
                Apr 16 20:39:28 unbound 77728:5 error: outgoing tcp: connect: Address already in use for 1.0.0.1
                Apr 17 21:25:30 unbound 77728:7 error: outgoing tcp: connect: Address already in use for 1.1.1.1
                Apr 17 22:23:10 unbound 77728:5 error: outgoing tcp: connect: Address already in use for 1.0.0.1
                Apr 17 22:29:41 unbound 77728:3 error: outgoing tcp: connect: Address already in use for 1.1.1.1

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

                  That's apparently a side effect of Unbound re-using a source port for a different destination, and can safely be ignored.

                  https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=3582

                  The message is suppressed for these cases in Unbound 1.7 which is already in pfSense 2.4.4 snapshots.

                  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!

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