11 Čen
2025
11 Čen
'25
22:05
I ultimately found that I needed to use a CH in KDIG but wonder how I/We could update the
documentation or add an alias for chaos.
Working Example:
dig +short @<dns server> version.bind chaos txt
dig +short @<dns server> version.bind CH txt
kdig +short @<dns server> version.bind CH txt
Problem Example:
kdig +short @<dns server> version.bind chaos txt
I had to read source code to find the answer in a speedy timeframe.
12 Čen
12 Čen
7:25
Hi!
The secure way is to use named arguments instead of argument autodetection. E.g.
kdig +short @<dns server> -q version.bind -c ch -t txt
Daniel
On 6/11/25 22:05, lathama(a)gmail.com wrote:
I ultimately found that I needed to use a CH in KDIG
but wonder how I/We could update the documentation or add an alias for chaos.
Working Example:
dig +short @<dns server> version.bind chaos txt
dig +short @<dns server> version.bind CH txt
kdig +short @<dns server> version.bind CH txt
Problem Example:
kdig +short @<dns server> version.bind chaos txt
I had to read source code to find the answer in a speedy timeframe.
--
14:39
Daniel
I guess I am asking a few things.
1. Can or should we add the word chaos to the documentation?
2. Can or should there be an alias for chaos to ch like in BIND's dig?
3. Where would it be best to mention RFC 4892 for someone searching for it?
On Wed, Jun 11, 2025 at 11:25 PM Daniel Salzman <daniel.salzman(a)nic.cz> wrote:
Hi!
The secure way is to use named arguments instead of argument autodetection. E.g.
kdig +short @<dns server> -q version.bind -c ch -t txt
Daniel
On 6/11/25 22:05, lathama(a)gmail.com wrote:
--
- Andrew "lathama" Latham -
I ultimately found that I needed to use a CH in
KDIG but wonder how I/We could update the documentation or add an alias for chaos.
Working Example:
dig +short @<dns server> version.bind chaos txt
dig +short @<dns server> version.bind CH txt
kdig +short @<dns server> version.bind CH txt
Problem Example:
kdig +short @<dns server> version.bind chaos txt
I had to read source code to find the answer in a speedy timeframe.
--
20:56
2. Can or should there be an alias for chaos to ch like
in BIND's dig?
The CHAOS alias in dig(1) works, but it is not documented in current versions.
Specifically dig(1) says:
| The IN and CH class names overlap with the IN and CH top-level domain names.
| Either use the -t and -c options to specify the type and class, use the -q to
| specify the domain name, or use "IN." and "CH." when looking up
these top-level
| domains.
I wasn't even aware of being able to use "CHAOS"; I don't think I'll
adopt it.
-JP
13 Čen
13 Čen
13:57
The CHAOS alias in dig(1) works, but it is not
documented in current versions.
I woke up thinking maybe only the first two characters of the class are
checked and how much fun I could have with that, but that is not the case.
BIND's source tree at lib/dns/rcode.c supports CH and CHAOS, HS and HESIOD,
ANY, NONE, RESERVED0, and IN but not INTERNET.
-JP
7:49
I believe these changes are enough
https://gitlab.nic.cz/knot/knot-dns/-/merge_requests/1785/commits
Daniel
On 6/12/25 14:39, Andrew Latham wrote:
Daniel
I guess I am asking a few things.
1. Can or should we add the word chaos to the documentation?
2. Can or should there be an alias for chaos to ch like in BIND's dig?
3. Where would it be best to mention RFC 4892 for someone searching for it?
On Wed, Jun 11, 2025 at 11:25 PM Daniel Salzman <daniel.salzman(a)nic.cz> wrote:
Hi!
The secure way is to use named arguments instead of argument autodetection. E.g.
kdig +short @<dns server> -q version.bind -c ch -t txt
Daniel
On 6/11/25 22:05, lathama(a)gmail.com wrote:
I ultimately found that I needed to use a CH in
KDIG but wonder how I/We could update the documentation or add an alias for chaos.
Working Example:
dig +short @<dns server> version.bind chaos txt
dig +short @<dns server> version.bind CH txt
kdig +short @<dns server> version.bind CH txt
Problem Example:
kdig +short @<dns server> version.bind chaos txt
I had to read source code to find the answer in a speedy timeframe.
--
16:12
Daniel
Thanks, it has been a while and I had to find the right login to comment there.
On Thu, Jun 12, 2025 at 11:49 PM Daniel Salzman <daniel.salzman(a)nic.cz> wrote:
I believe these changes are enough
https://gitlab.nic.cz/knot/knot-dns/-/merge_requests/1785/commits
Daniel
On 6/12/25 14:39, Andrew Latham wrote:
--
- Andrew "lathama" Latham -
Daniel
I guess I am asking a few things.
1. Can or should we add the word chaos to the documentation?
2. Can or should there be an alias for chaos to ch like in BIND's dig?
3. Where would it be best to mention RFC 4892 for someone searching for it?
On Wed, Jun 11, 2025 at 11:25 PM Daniel Salzman <daniel.salzman(a)nic.cz> wrote:
Hi!
The secure way is to use named arguments instead of argument autodetection. E.g.
kdig +short @<dns server> -q version.bind -c ch -t txt
Daniel
On 6/11/25 22:05, lathama(a)gmail.com wrote:
I ultimately found that I needed to use a CH in
KDIG but wonder how I/We could update the documentation or add an alias for chaos.
Working Example:
dig +short @<dns server> version.bind chaos txt
dig +short @<dns server> version.bind CH txt
kdig +short @<dns server> version.bind CH txt
Problem Example:
kdig +short @<dns server> version.bind chaos txt
I had to read source code to find the answer in a speedy timeframe.
--
2
days inactive
4
days old
7 comments
5 participants
participants (5)
-
Andrew Latham -
Daniel Salzman -
Jan-Piet Mens -
lathama＠gmail.com
-
Vladimír Čunát