Fwd: About dnstap feature

2024-09-18 Thread Champion Xie
After executing rndc dnstap -reopen, the properties of the dnstap-output object file changed, and the original named became root. Of course, I used the root user to execute the rndc command. At this time, executing dnstap-read again will report an error, and the query log cannot be written to the d

Re: use dig query

2021-10-25 Thread Champion Xie
cloudflare.com. > > ;; Query time: 235 msec > ;; SERVER: 199.253.249.53#53(199.253.249.53) > ;; WHEN: Mon Oct 25 15:41:15 AEDT 2021 > ;; MSG SIZE rcvd: 127 > > ;; Sending: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6266 > ;; flags: ad; QUERY: 1, ANSW

use dig query

2021-10-24 Thread Champion Xie
dig version 9.14.8 Using the following command can not achieve the desired effect, dnssec information will still be output dig 1.1.1.1.in-addr.arpa +trace +nodnssec Normally, the parameters should not be in sequence -- Best Regards!! champion_xie

bind-9.14.9 with pkcs11 lib

2020-03-25 Thread Champion Xie
when I build BIND, bellow: hi all : ./configure --prefix=/opt/bind9 --with-openssl=/opt/openssl-1.1.1d * --with-pkcs11=/opt/hsm/libsspkcs11.so* --with-python-/usr/local/python27/bin/python && make && make install ok it'fine and then /opt/bind9/sbin/pkcs11-list -p "" --- it' s ok /opt/bind9/

catalog zone function

2019-12-09 Thread Champion Xie
hi all When I use the catalogzone function to automatically add zones, I found from the slave server that the zone files are not stored according to the custom path, but are stored in the directory defined in options. the service is started by chroot -- Best Regards!! champion_xie __

BIND 9.14.8

2019-12-09 Thread Champion Xie
hi all BIND 9.14.8 (Stable Release) When I start the server, I get such a prompt. Are there any parameters I 9turn off? After all, not all servers implement DNSSEC 09-Dec-2019 16:17:46.497 dnssec: warning: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out -- Best Regards!! champion_

BIND 9.14.8 version

2019-12-08 Thread Champion Xie
Hi, all When I use chroot, on the contrary this prompt message will cause confusion to the user Or you can specify the use of chroot in the compilation parameters, and then prompt for the default path according to the chroot path *BIND 9.14.8* (Stable Release) running on Linux x86_64 3.10.0-957.