configure error for bind-9.20.1

2024-09-16 Thread Sakuma, Koshiro
Hello.

I am trying to setup bind-9.20.1, but I got error as below.  OS is RHEL9.4
and I am installing bind from source.  Actually, libatomic has already been
install.  I am not sure if I can skip this one and can make or not.

"checking whether -latomic is needed for 64-bit stdatomic.h functions...
configure: error: in `/usr/local/src/bind-9.20.1':
configure: error: libatomic needed, but linking with -latomic failed,
please fix your toolchain."

Regards,
-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Unrecognized Options --enable-threads

2022-05-03 Thread Sakuma, Koshiro
Hi Team,

I am going to upgrade to 9.16.28 version.  Currently, I'm using 9.16.13.
Now, I am trying to upgrade and I got something error like this.

Unrecognized options:
--enable-threads
---
For more detail, use --enable-full-report.

This option might be disabled with version 9.16.28?  Also, I just do "make
install" for bind upgrade?  I mean, this way might be overwritten current
bind files??  Or please let me know how I can upgrade.

Thanks for your help.

Regards,
-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


dnssec bad cache hit error for bind9.16.13

2021-04-01 Thread Sakuma, Koshiro
Hello Team;

I've just finished setup for bind9.16.13 from scratch (source).  But I got
error when I checked with bind function with "dig" command.   The error I
got was as below.

1. dig result;
; <<>> DiG 9.11.20-RedHat-9.11.20-5.el8_3.1 <<>>
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: *SERVFAIL,* id: 17070
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

2. named.log
There are many bad cache hit logs.
dnssec: view internal:   validating nikkei225jp.com/SOA: bad cache hit
(com/DS)

I tried to dig out for this issue, I found one thing that disable
dnssec-validation option.
After changing, the issue had been fixed.  However, I'm wondering if I can
disable this option for security reason.  Or there is another solution??

Thank you for your support!

Regards,
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users