Navigation

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

    BIND doesn't properly restart upon bouncing of LAN interface (pfSense 2.3.3_1)

    DHCP and DNS
    2
    3
    682
    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
      jtl last edited by

      Hello

      Using pfSense 2.3.3_1. I have the BIND package installed as a DNS server for my LAN, using some BIND specific features, etc.

      One issue I'm having is upon the LAN interface going down (doesn't happen often but it's still an issue nevertheless) the BIND server doesn't react properly to it and doesn't accept queries from clients, etc.

      Here is the relevant output from the named logs.

      
      Apr 30 13:32:42	named	99378	no longer listening on 192.168.1.1#53
      Apr 30 13:32:44	named	99378	listening on IPv4 interface em3, 192.168.1.1#53
      Apr 30 13:32:44	named	99378	could not listen on UDP socket: permission denied
      Apr 30 13:32:44	named	99378	creating IPv4 interface em3 failed; interface ignored
      Apr 30 13:32:44	named	99378	listening on IPv4 interface em3, 192.168.1.1#53
      Apr 30 13:32:44	named	99378	could not listen on UDP socket: permission denied
      Apr 30 13:32:44	named	99378	creating IPv4 interface em3 failed; interface ignored
      Apr 30 13:32:44	named	99378	listening on IPv4 interface em3, 192.168.1.1#53
      Apr 30 13:32:44	named	99378	could not listen on UDP socket: permission denied
      Apr 30 13:32:44	named	99378	creating IPv4 interface em3 failed; interface ignored
      Apr 30 13:32:44	named	99378	listening on IPv4 interface em3, 192.168.1.1#53
      Apr 30 13:32:44	named	99378	could not listen on UDP socket: permission denied
      Apr 30 13:32:44	named	99378	creating IPv4 interface em3 failed; interface ignored
      
      

      Thanks

      pfSense 2.4.2 - virtualized with PCIe passthrough on whitebox - 150/150 FTTP

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

        Seems like old or other process are still using the 53 port.

        Treinamentos de Elite: http://sys-squad.com

        Help a community developer! ;D

        1 Reply Last reply Reply Quote 0
        • J
          jtl last edited by

          Ah. I have DNS resolver/forwarder disabled though.

          Could it possibly be a phantom BIND instance of a sort?

          Will do more tests later.

          pfSense 2.4.2 - virtualized with PCIe passthrough on whitebox - 150/150 FTTP

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