Behavior of port tag in options clause is ambiguous

[Vikas Sharma]

Hi Team,

we have following configuration in my named.conf
where i named process on primary DNS is listening on port 15010.
whereas secondary DNS is running on port 53.
All Notification to secondary DNS is forwarded on destination port 53 from
primary DNS.

Now when i add tag port 15010 in options clause on primary DNS, then i see
some notification message being forwarded to secondary DNS to dest port
15010. these messages are in addition to notification to secondary DNS with
dest port 53.
changing port value form 15010 to 20598 sends notification to secondary
DSN on dest port 20598 in addition to notification to secondary on port 53.

i have a firewall on secondary DNS which is rejecting all packets on port
15010/20598.
i see that all my data is populated on secondary DNS without any problem
due to notifications to secondary DNS on port 53.

query is why named is sending notification to secondary DNS on port
15010/20598 when regular notification is also going to secondary DNS on
port 53.


acl theAllServers {
         thePrimary;
         theSecondary;
         localhost;
};

options {
         directory "/var/opt/named";
         pid-file "/var/opt/run/named.pid";
         allow-transfer { theAllServers; };
         allow-query { any; };
         zone-statistics no;
         notify yes;
         max-cache-size 14297m;
         max-journal-size 1048576;
         port 15010;                                       #=> used 20598
as well instead of 15010;
         listen-on port 15010 { 127.0.0.1; };
         also-notify {
                 10.1.2.4 port 53;
                 10.1.2.5 port 53;
         };
};

Best Regards,
Vikas Sharma
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20221216/bf367b80/attachment-0001.htm>