Re: about apply Deckard to test BIND named

On 16. 02. 22 10:12, Ondřej Surý wrote: I guess you can possibly workaround this by disabling jemalloc from named build and hope that the static shims for jemalloc calls will trump the preloaded functions from libfaketime. Oh right, I forgot we can also compile BIND without jemalloc - it

Re: about apply Deckard to test BIND named

I guess you can possibly workaround this by disabling jemalloc from named build and hope that the static shims for jemalloc calls will trump the preloaded functions from libfaketime. Ondřej -- Ondřej Surý — ISC (He/Him) My working hours and your working hours may be different. Please do not

Re: about apply Deckard to test BIND named

Hi, it is even more complicated: - Latest version of Deckard uses Linux network namespaces and thus makes BIND GL#2088 unnecessary - It does not work anyway because jemalloc library used by libfaketime breaks libfaketime library is used by Deckard for DNSSEC tests. See

Re: about apply Deckard to test BIND named

Thank Ondřej for the information ! Best Regards,SUN Guonian On Wednesday, February 16, 2022, 04:05:06 PM GMT+8, Ondřej Surý wrote: Hi Sun, this is impressive effort, but it has several known gotchas: 1. The `named` looks for real interfaces to listen too and it     didn’t play well

Re: about apply Deckard to test BIND named

Hi Sun, this is impressive effort, but it has several known gotchas: 1. The `named` looks for real interfaces to listen too and it didn’t play well with Deckard in the past. I’ve been told that this is no longer a problem, but it could be something you should be aware of. See [GL

about apply Deckard to test BIND named

Hi, I notice that Deckard project can be used to test knot/knot-resolver/unbound/pdns except BIND.And I try to write the configuration and template files for named, but it didn't work. If BIND's implementation/configuration has any limitation to run with Deckard ? Thanks in advance ! Best