> On 4. 5. 2022, at 6:36, Sakuma, Koshiro wrote:
>
>
> 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
> -
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 --enab
I have in the past considered that putting these kinds of records in for
anycast nodes (such as, but not limited to root DNS servers), so that a person
can glean how far they are from the node serving them (gleaned via
hostname.bind or NSID), would be useful and fun science, in that in this way
On 2022-05-02 18:01, Timothe Litt wrote:
Still, overall DNS seems to generate more problems than fun, so if LOC
provides amusement, it's a good thing.
I know one of my users found them quite amusing. I can't recall what
location they picked or why, but it had some sort of personal
significanc
On 2022-05-03 06:31, Gaurav Kansal wrote:
Yup. But if the DNS infra is under my control, then definitely the keys (which
i have used for encryption) will also be with me. Am i missing something here ?
🧐
I'll see your privacy keys and raise you Perfect Forward Secrecy.
Although I'm not really
It’s already been addressed
--
Mark Andrews
> On 4 May 2022, at 06:16, Larry Rosenman wrote:
>
> I did find a manpage bug for the rndc man page for 9.18.2:
> dnssec (-status | -rollover -key id [-alg algorithm] [-when time] |
> -checkds [-key id [-alg algorithm]] [-when time] published
I did find a manpage bug for the rndc man page for 9.18.2:
dnssec (-status | -rollover -key id [-alg algorithm] [-when time] |
-checkds [-key id [-alg algorithm]] [-when time] published |
withdraw))
zone [class [view]]
s/withdraw/withdrawn/
withdraw garners a syntax error :(
Wh
I tried this utility and got the following message: gnutls-cli: command not
found...
Thank you
V/R
Jim DeCaro
-Original Message-
From: Ondřej Surý
Sent: Thursday, April 28, 2022 5:15 PM
Cc: DeCaro, James John (Jim) CIV DISA FE (USA) ;
bind-users@lists.isc.org; Mcallister, Reginald CT
Hello--sorry it took so long to respond. And I apologize for the length of this
email.
Yes, the curl command returns an xml file. I included an excerpt from the
output:
"About to connect() to download.copr.fedorainfracloud.org port 443 (#0)
* Trying 13.32.153.64...
* Connected to download.co
> On 3. 5. 2022, at 14:31, Gaurav Kansal wrote:
>
> Yup. But if the DNS infra is under my control, then definitely the keys
> (which i have used for encryption) will also be with me. Am i missing
> something here ? 🧐
Then you need to make the private keys available to the monitoring software.
Yup. But if the DNS infra is under my control, then definitely the keys (which
i have used for encryption) will also be with me. Am i missing something here ?
🧐
—
Gaurav Kansal
> On 03-May-2022, at 14:40, Petr Špaček wrote:
>
> On 03. 05. 22 10:56, Gaurav Kansal wrote:
>> Or if you are ready
Timothe Litt wrote:
> On 02-May-22 09:02, Stephane Bortzmeyer wrote:
> > Fun is a sufficient reason.
>
> I would never discourage anyone from having (harmless) fun.
>
> On the other hand, unless your codes postaux are spherical (or a circular
> projection), your LOC will be at best an approximati
On 03. 05. 22 10:56, Gaurav Kansal wrote:
Or if you are ready to take some pain, then take the mirror from the
network side, parse the packets and you can achieve whaterver you want
to do, build beautiful graphs, have reports and what not.
This will also help in reducing the load on your DNS nod
Or if you are ready to take some pain, then take the mirror from the network
side, parse the packets and you can achieve whaterver you want to do, build
beautiful graphs, have reports and what not.
This will also help in reducing the load on your DNS node by disabling the
logging completely and
14 matches
Mail list logo
