[GH-ISSUE #28] Sharing some ideas about Chapter 1 #37

Open
opened 2026-03-07 21:26:50 +03:00 by kerem · 0 comments
Owner

Originally created by @smf8 on GitHub (Nov 1, 2024).
Original GitHub issue: https://github.com/EmilHernvall/dnsguide/issues/28

Hi, Thank you for the great tutorial.

I started with Chapter 1 and had some questions that I think would be great to address in the original tutorial.

  1. It's already mentioned that Question Section usually contains a single question. I think it's better to add the correlation with QDCOUNT (noting in the description that the value is usually 1).
  2. Since most of the time the Question section contains only a single record, and considering that the compression is addressed for the Record section in the original RFC. I think it might help to mention this in the tutorial. Also, I couldn't produce a DNS query with multiple Questions to test compression using dig. So I think It's just introducing a complexity in a place that doesn't require it.
  3. BTW adding the original RFC link would be great.

What do you think?

Originally created by @smf8 on GitHub (Nov 1, 2024). Original GitHub issue: https://github.com/EmilHernvall/dnsguide/issues/28 Hi, Thank you for the great tutorial. I started with Chapter 1 and had some questions that I think would be great to address in the original tutorial. 1. It's already mentioned that **Question Section** usually contains a single question. I think it's better to add the correlation with QDCOUNT (noting in the description that the value is usually 1). 2. Since most of the time the Question section contains only a single record, and considering that the compression is addressed for the **Record** section in the [original RFC](https://datatracker.ietf.org/doc/html/rfc1035#section-4.1.4). I think it might help to mention this in the tutorial. Also, I couldn't produce a DNS query with multiple Questions to test compression using `dig`. So I think It's just introducing a complexity in a place that doesn't require it. 3. BTW adding the [original RFC link](https://datatracker.ietf.org/doc/html/rfc1035) would be great. What do you think?
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dnsguide#37
No description provided.