> I am also interested in understanding the reasons behind this
> behaviour, especially after reading the following snippet from the
> official knowledge base [1]:
Thank you for pointing out the official documentation.
dig didn't even implement it according to its official documentation!
Hello list,
I am also interested in understanding the reasons behind this
behaviour, especially after reading the following snippet from the
official knowledge base [1]:
When following delegation iteratively as specified with the +trace
option, dig will begin by requesting the NS records
As we all know, dig +trace can perform iterative queries, starting from the
root name server, to the top-level name server, and then to the name server of
the second-level domain name.
8 7.158512318 192.168.3.34 → 1.1.1.1 DNS 82 Standard query 0x6ab6 NS
OPT
9 7.324926676 1.1.1.1 →
3 matches
Mail list logo