Only you can answer that question… it’s your system.
--
Ondřej Surý — ISC (He/Him)
My working hours and your working hours may be different. Please do not feel
obligated to reply outside your normal working hours.
> On 1. 10. 2021, at 0:04, Maihöfer via bind-users
> wrote:
>
> How did it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 2021-09-30 at 16:30 -0700, Fred Morris wrote:
> https://github.com/m3047/tcp_only_forwarder
So what exactly are the media devices doing to screw up dns resolution
between the osx laptop and the local dns server?
-BEGIN PGP
Hi there. Media devices and a crappy SOHO wifi AP? I know that feeling.
;-)
On Thu, 30 Sep 2021, Donika Mirdita wrote:
I have set up a nameserver and I would like to force all future client
requests to TCP only.
You can't really. You can try, by setting TC, but if the clients never
see the
Hi Petr,
hey Ondrej,
something is missing.
philipp@log$ ldd /usr/lib/x86_64-linux-gnu/libisc-9.16.15-Debian.so |
grep libuv
libuv.so.1 => /usr/local/lib/libuv.so.1 (0x7fd42d2e3000)
philipp@log$ readelf --dyn-syms /usr/local/lib/libuv.so.1 | grep
uv_udp_connect
philipp@log$
The
Hello,
I have set up a nameserver and I would like to force all future client
requests to TCP only.
Essentially, one scenario would be for all UDP requests to be countered
with a packet that has the TC bit set so the connection
is retried via TCP. I want this rule to be applicable to all
Using ldd is a good debugging step, but I would start with deleting the obsolete
copy of libuv from /usr/local. That helps in 99% of cases like this.
> Either packagers on Debian made mistake
Definitely not ;-)
Ondrej.
--
Ondřej Surý (He/Him)
ond...@isc.org
> On 30. 9. 2021, at 14:39, Petr
Can you check with ldd whether libuv is explicitly set on libisc library?
ldd /usr/lib/x86_64-linux-gnu/libisc-9.16.15-Debian.so
It works on Fedora just fine:
ldd /usr/lib64/libisc-9.16.21-RH.so | grep libuv
libuv.so.1 => /lib64/libuv.so.1 (0x7f4bf7716000)
readelf --dyn-syms
7 matches
Mail list logo
