Why does bind not list on UDP port 53?

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
#1
I'm running on a Debian 10 physical box with two wired network ports. This looks like it's supported. I've been having trouble getting the DNS request from the client working. Looking at the supplied bind config it's listening on port 5300 and there are no forwarders defined.

// GENERATED BY KEEXYBOX WEBUI
// DO NOT EDIT THIS FILE

options {
        directory "/opt/keexybox/bind//etc/zones";
        listen-on port 5300 { any; };
        dnssec-validation no;
        pid-file "/opt/keexybox/bind//var/run/named/named.pid";
        auth-nxdomain no;    # conform to RFC1035
        //listen-on-v6 { any; };
};
controls {
        inet 127.0.0.1 port 9530 allow {localhost;};
};
include "/opt/keexybox/bind//etc/conf.d/profiles.conf";
include "/opt/keexybox/bind//etc/conf.d/logging.conf";


Is this correct?

I changed the 5300 to 53 and added a forwarders section and it works.
Reply
#1
I'm running on a Debian 10 physical box with two wired network ports. This looks like it's supported. I've been having trouble getting the DNS request from the client working. Looking at the supplied bind config it's listening on port 5300 and there are no forwarders defined.

// GENERATED BY KEEXYBOX WEBUI
// DO NOT EDIT THIS FILE

options {
        directory "/opt/keexybox/bind//etc/zones";
        listen-on port 5300 { any; };
        dnssec-validation no;
        pid-file "/opt/keexybox/bind//var/run/named/named.pid";
        auth-nxdomain no;    # conform to RFC1035
        //listen-on-v6 { any; };
};
controls {
        inet 127.0.0.1 port 9530 allow {localhost;};
};
include "/opt/keexybox/bind//etc/conf.d/profiles.conf";
include "/opt/keexybox/bind//etc/conf.d/logging.conf";


Is this correct?

I changed the 5300 to 53 and added a forwarders section and it works.
Reply


Messages In This Thread
Why does bind not list on UDP port 53? - by BlobZ - 01-30-2022, 02:12 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)