Re: Truncated TCP ?

2024-05-05 Thread Mark Andrews
> On 6 May 2024, at 07:38, J Doe wrote: > > Hello, > > I run BIND 9.18.26 as a recursive, validating resolver. In my logs, I > noticed the following: > >01-May-2024 00:52:49.689 lame-servers: info: truncated TCP response >resolving 'www.ipfire.org/A/IN': 74.113.60.134#53 > > I

Truncated TCP ?

2024-05-05 Thread J Doe
Hello, I run BIND 9.18.26 as a recursive, validating resolver. In my logs, I noticed the following: 01-May-2024 00:52:49.689 lame-servers: info: truncated TCP response resolving 'www.ipfire.org/A/IN': 74.113.60.134#53 I am aware that there are issues with DNS UDP traffic being

Re: Switching from rhel base 9.16 to 9.18 copr

2024-05-05 Thread Carlos Horowicz
I used these symlinks to transition from RHEL standard 9.16 to COPR 9.18 ln -s /var/opt/isc/scls/isc-bind/named /var/named ln -s /etc/opt/isc/scls/isc-bind/named.conf /etc/named.conf ln -s /var/opt/isc/scls/isc-bind/run/named /run/named ln -s /opt/isc/isc-bind/root/usr/sbin/rndc /usr/sbin/rndc

Re: Switching from rhel base 9.16 to 9.18 copr

2024-05-05 Thread Peter
On Sun, May 05, 2024 at 06:15:13PM +0200, Luca vom Bruch via bind-users wrote: ! Hello, ! ! I use bind (stock from alma 9.3) as a nameserver for a webhosting server ! with webmin/virtualmin. ! ! If I install BIND via copr (RHEL9 and derivatives only offer 9.16 instead of ! 9.18 - I want to

Switching from rhel base 9.16 to 9.18 copr

2024-05-05 Thread Luca vom Bruch via bind-users
Hello, I use bind (stock from alma 9.3) as a nameserver for a webhosting server with webmin/virtualmin. If I install BIND via copr (RHEL9 and derivatives only offer 9.16 instead of 9.18 - I want to experiment with DoT for opportunistic TLS between nameservers, upcoming standard