Messages

1

23.1 Legacy Series / Re: os-bind did not listen port 53530

« on: May 05, 2023, 04:48:55 pm »

I did not make any default configuration changes.
sockstat |grep named shows
bind     named      31833 3  dgram  -> /var/run/logpriv
bind     named      31833 29 tcp4   127.0.0.1:9530        *:*
bind     named      31833 30 tcp4   127.0.0.1:9530        *:*
bind     named      31833 31 tcp4   127.0.0.1:9530        *:*
bind     named      31833 34 tcp4   127.0.0.1:9530        *:*

and named.conf config show
options {

        directory       "/usr/local/etc/namedb/working";
        pid-file        "/var/run/named/pid";
        dump-file       "/var/dump/named_dump.db";
        statistics-file "/var/stats/named.stats";

        listen-on port 53530 { 0.0.0.0; };
        listen-on-v6 port 53530 { ::; };

        recursion          yes;
        allow-recursion {
                localNetwork;
        };


        allow-query {
                localNetwork;
        };

        max-cache-size    80%;
        dnssec-validation    no;
};

Thanks

2

23.1 Legacy Series / Re: os-bind did not listen port 53530

« on: May 05, 2023, 04:42:24 pm »

Log look normal to me.  When I run netstat -an|grep 53530, nothing shows up.

Here is startup log
05-May-2023 10:14:22.932 zoneload: info: managed-keys-zone: loaded serial 0
05-May-2023 10:14:22.934 zoneload: info: zone 0.ip6.arpa/IN: loaded serial 42
05-May-2023 10:14:22.935 zoneload: info: zone 127.in-addr.arpa/IN: loaded serial 42
05-May-2023 10:14:22.937 zoneload: info: zone localhost/IN: loaded serial 42
05-May-2023 10:14:22.937 general: notice: all zones loaded
05-May-2023 10:14:22.937 general: notice: running

3

23.1 Legacy Series / os-bind did not listen port 53530

« on: May 05, 2023, 04:17:55 pm »

I installed os-bind plugin and add some secondary zone. It is a very simple setup.  After starting the bind, I did not see bind is listening on port 53530.

I am running opnsense 23.1.7_2-amd64.

I am not sure what configuration is missing.

Thanks