Hi John,
It all depends on the key material that is used to sign your zone. It
looks like you have to update the DNSKEY RRset, so I assume the vendors
are responsible for signing and each have their own key material.
In order to let the world know you are going to use new keys you will
have to pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
https://www.five-ten-sg.com/mapper/bind contains links to the source
rpms, and build instructions.
-BEGIN PGP SIGNATURE-
iHMEAREKADMWIQSuFMepaSkjWnTxQ5QvqPuaKVMWwQUCXz7EtRUcY2FybEBmaXZl
LXRlbi1zZy5jb20ACgkQL6j7milTFsHXUwCffZxEKWp/Ssbw7cXJa
On 8/20/20 11:45 AM, Carl Byington via bind-users wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> https://www.five-ten-sg.com/mapper/bind contains links to the source
> rpms, and build instructions.
How/why are these^ generally different than the isc-maintained pkgs at
htt
As for Viettel, I don't know how they configure it.
But when I use a server on another network, the result is as follows:
; <<>> DiG 9.6-ESV-R8 <<>> @115.84.177.8 250.0-24.199.212.125.in-addr.arpa
ptr
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status:
> my question is why would anyone do this, as this apparently does not make
> sense.
Because when I was from a server that was querying the reverse record
250.199.212.125.in-addr.arpa it gave an error with the "SERVFAIL" error
code so I tried to query directly to the hosting that managed it to
de
5 matches
Mail list logo
