Consult log of bind9 service. It should autodetect 4 cores without any
options, just with plain start of the service.
It should show isc-socket thread for each core:
pstree -t $(pidof named)
I were surprised of my output however, because I have multiple
isc-net-000{1}. My version is bind-9.16.18
I’m in the process of building a custom version of bind with DoH and would also
like to add DNSSEC algorithm 15 for experimental purposes
DoH works just fine on the servers I have configured.
My “configure" command is
./configure --with-openssl=../openssl-1.1.1k --with-libxml2 --with-json-c
Eric,
configure uses pkg-config to detect OpenSSL version thus you need to point
pkg-config to the right directory.
There’s no such option to configure.
Ondřej
--
Ondřej Surý — ISC (He/Him)
My working hours and your working hours may be different. Please do not feel
obligated to reply outside
I’m confused
./configure --help | grep openssl
--with-openssl=DIR root of the OpenSSL directory
---
Eric Germann
ekgermann {at} semperen {dot} com || ekgermann {at} gmail {dot} com
LinkedIn: https://www.linkedin.com/in/ericgermann
Twitter: @ekgermann
Telegram || Signal || Phone +1 {dash}
Oh, you are right. That will get only used when pkg-config based method doesn’t
work. We probably should remove that as openssl.pc is now widely available.
Ondřej
--
Ondřej Surý — ISC (He/Him)
My working hours and your working hours may be different. Please do not feel
obligated to reply outsid
Bummer.
Thanks for the quick turnaround though!
---
Eric Germann
ekgermann {at} semperen {dot} com || ekgermann {at} gmail {dot} com
LinkedIn: https://www.linkedin.com/in/ericgermann
Twitter: @ekgermann
Telegram || Signal || Phone +1 {dash} 419 {dash} 513 {dash} 0712
GPG Fingerprint: 89ED 36B3 5
Setting PKG_CONFIG_PATH should work as charm…
--
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 5. 7. 2021, at 19:33, Eric Germann wrote:
>
> Bummer.
>
> Thanks for the quick
Currently running Bind v9.11.4:
Several years ago, I implemented multiple VIEWs using (almost) the exact
example in the Reference Manual. However, I wanted the
"example-internal.db" and "example-external.db" to be the same file.
This worked until I wanted to have "example.com" updateable via
Has ISC given any thought to releasing dig as a separate source package?
It’s good for testing DoH, but you need to build the entire bind package to get
it. It would be useful for support analysts without the overhead of compiling
all of bind to get it
---
Eric Germann
ekgermann {at} semperen
I've been getting a few errors along these lines (bind 9.16.18), the IPs
changes, but I don't know what "non0improving referral" means or if I should be
concerned.
DNS format error from 64.70.78.82#53 resolving ok.contact/NS for
127.0.0.1#16749: non-improving referra
This IP is owned bv Cent
> On 6 Jul 2021, at 05:56, Eric Germann via bind-users
> wrote:
>
> Has ISC given any thought to releasing dig as a separate source package?
>
> It’s good for testing DoH, but you need to build the entire bind package to
> get it. It would be useful for support analysts without the overhead
> On 6 Jul 2021, at 06:40, @lbutlr wrote:
>
> I've been getting a few errors along these lines (bind 9.16.18), the IPs
> changes, but I don't know what "non0improving referral" means or if I should
> be concerned.
>
> DNS format error from 64.70.78.82#53 resolving ok.contact/NS for
> 127.
If you want the content to be the same in both views and to be dynamically
updatable then use
view view1 {
zone example.com {
type primary;
[ allow-update / update-policy ] { … };
…
};
};
view view2 {
zone example.com { in-v
Well! That was the quickest & simplest WORKING solution I have ever
received from a mailing list! Thank you!
On 2021-07-05 17:55, Mark Andrews wrote:
If you want the content to be the same in both views and to be dynamically
updatable then use
view view1 {
zone example.com {
14 matches
Mail list logo
