Re: [dns-operations] https://secure-web.cisco.com/1ZjyzJskkYQq7sVMAaORAQUNbtLnCDdiphJXoIUgaA7_oFL6tHC8iV070aZrCZfTyULjhkVi3xJfW5opBdNn-YVZVvneE8CazN4a3cBB_5D0ERlfp-D-9kGVsbAT_XzThiOOKiL1K02Z_t969017Ug

Ah all sorted then. Thanks Duane, W On Mon, Nov 9, 2020 at 3:30 PM Wessels, Duane wrote: > > > > > On Nov 9, 2020, at 11:44 AM, Warren Kumari wrote: > > > > Erm, what sort of glitch? (seems to work for me - wondering if it is > > transient, or ...) > > > It was easily fixed. The glitch was a

Re: [dns-operations] https://secure-web.cisco.com/1ZjyzJskkYQq7sVMAaORAQUNbtLnCDdiphJXoIUgaA7_oFL6tHC8iV070aZrCZfTyULjhkVi3xJfW5opBdNn-YVZVvneE8CazN4a3cBB_5D0ERlfp-D-9kGVsbAT_XzThiOOKiL1K02Z_t969017Ug

--- Begin Message --- > On Nov 9, 2020, at 11:44 AM, Warren Kumari wrote: > > Erm, what sort of glitch? (seems to work for me - wondering if it is > transient, or ...) It was easily fixed. The glitch was a bug in the backend script such that every request led to an "Internal Server Error".

Re: [dns-operations] https://trans-trust.verisignlabs.com/

Erm, what sort of glitch? (seems to work for me - wondering if it is transient, or ...) In the meantime, you can try https://www.superficialinjurymonkey.com/ (click DNS Delegation Explorer), it might work for $whatever trans-trust didn't. Note that this was thrown together while sitting on a

Re: [dns-operations] dnstap tool

Hoan Vu wrote: > > We are learning to get query log by dnstap tool. For DNSTAP Tool we cannot > get log query continuosly and directly to the current syslog server, since > raw log need to capture and then read after stop capture. Earlier today I saw a tweet from JP Mens about this which might

Re: [dns-operations] How DNS work

On Mon, Nov 09, 2020 at 03:34:32PM +, Jim Reid wrote a message of 60 lines which said: > A well behaved resolving server will only send a handful of queries > (if that) to the root every day - ie whenever it needs to lookup a > TLD that hasn’t been cached. And may be not even so, if they

Re: [dns-operations] How DNS work

> On 9 Nov 2020, at 04:15, Hoan Vu wrote: > > We really wanna know "what is round robin of DNS" and the nature of the rule > to choose the DNS Root of Resolver, what factor, algorithm, that decide > the choice of DNS Root. Why? Nobody needs to care about this - apart from the people

Re: [dns-operations] https://secure-web.cisco.com/1QObC8qh53iR__TlqRff59E5B8JFiAV2VUGirT2kdLKo0yz-mYw9xle11YYObM5lxuamt1wUA26DRNfoRK6v8IXYl9zUeX7VkWIaBof6KLCFjBHsfqxnMrN2Muac7SkNMlWXCdqDvPKJTAORrYe1s9

--- Begin Message --- Hi Calvin, you can poke me. DW > On Nov 9, 2020, at 1:05 AM, Calvin Browne wrote: > > Caution: This email originated from outside the organization. Do not click > links or open attachments unless you recognize the sender and know the > content is safe. > > > > >

Re: [dns-operations] How DNS work

On Mon, Nov 09, 2020 at 11:15:12AM +0700, Hoan Vu wrote a message of 122 lines which said: > And we have already do lab, and then the DNS Cache work out of > order, the DNS Root is choiced rondomly. As explained in the APNIC article, it depends on the resolver. BIND, Knot, Unbound and the

Re: [dns-operations] dnstap tool

Hi! We have the dnstap binary running under daemontools' 'supervise', and pipe its output either to 'logger' for syslogging, or an 'aws logs push' process to ingest directly to Cloudwatch Logs. Since the example golang binary simply writes to standard out, it was easy to wire up. matt > On

[dns-operations] dnstap tool

Dear! We are learning to get query log by dnstap tool. For DNSTAP Tool we cannot get log query continuosly and directly to the current syslog server, since raw log need to capture and then read after stop capture. I wanna to know how to get the query log continously when using DNSTAP TOOL of your

[dns-operations] How DNS work

Dear! We are learning the operation of the DNS, we have find the document of Apnic *"The Root of the DNS"* ( https://labs.apnic.net/presentations/store/2017-03-12-root-servers-explained.pdf , *slide:18 "Which