Re: [SOLVED] Re: bind listening on UDP port 53 using 2 fd

On 26.01.21 12:04, Bernardo wrote: Again, the problem here is that perfectly valid configuration lines in /etc/named.conf would cause serious trouble. again, the "port 53" is what causes the problem. The rest is okay. Using those options without "port 53" is okay too. El lun, 25 ene 2021 a

Re: [SOLVED] Re: bind listening on UDP port 53 using 2 fd

Again, the problem here is that perfectly valid configuration lines in /etc/named.conf would cause serious trouble. BIND 9.16.1.+ DNS admins should be aware of it. So that's the reason I wrote this post. Regards,

Re: [SOLVED] Re: bind listening on UDP port 53 using 2 fd

On 25.01.21 14:05, Bernardo wrote: Yes. This causes serious problems. The problem is that these perfectly valid configuration lines in /etc/named.conf file (provided that 192.168.10.100 is the IPv4 address of your DNS server, it doesn't matter if it is a primary or secondary) will cause you a lo

Re: [SOLVED] Re: bind listening on UDP port 53 using 2 fd

Hi Matus, Yes. This causes serious problems. The problem is that these perfectly valid configuration lines in /etc/named.conf file (provided that 192.168.10.100 is the IPv4 address of your DNS server, it doesn't matter if it is a primary or secondary) will cause you a lot of trouble. query-sourc

Re: [SOLVED] Re: bind listening on UDP port 53 using 2 fd

On 23.01.21 12:44, Bernardo wrote: Finally I've found the solution. The problem seems to be caused by a known issue since BIND version 9.16.1 Commenting out these lines in /etc/named.conf solves the issue: query-source address 192.168.10.100; notify-source 192.168.10.100 port 53; transfer-sourc

[SOLVED] Re: bind listening on UDP port 53 using 2 fd

Hi all, Finally I've found the solution. The problem seems to be caused by a known issue since BIND version 9.16.1 Commenting out these lines in /etc/named.conf solves the issue: query-source address 192.168.10.100; notify-source 192.168.10.100 port 53; transfer-source 192.168.10.100 port 53; T