From 78d339c40434f373da2e2788f1b20afb85f04c62 Mon Sep 17 00:00:00 2001 From: Charles-Henri Bruyand Date: Thu, 29 Mar 2018 15:37:34 +0200 Subject: [PATCH] fix typos --- README.md | 4 ++-- meta.md | 2 +- stub.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index c103da2..6bc4309 100644 --- a/README.md +++ b/README.md @@ -358,7 +358,7 @@ should never happen. ## Zone files Zone files are one way of storing DNS data, but these are not integral to -the operation of a nameserver. The zone file format is standardised, but it +the operation of a nameserver. The zone file format is standardized, but it is highly non-trivial to parse. It is entirely possible to write useful nameserver that does not read or write DNS zone files. When embarking on parsing zonefiles, do not do so lightly. As an example, various fields @@ -614,7 +614,7 @@ record is created on the fly. ## Truncation Without implementing the optional EDNS protocol extension, all UDP responses must fit in 512 bytes of payload. If on writing an answer a server finds -itself exceding this limit, it must truncate the packet and set the TC bit +itself exceeding this limit, it must truncate the packet and set the TC bit to 1. The originator of the query will then resend the query over TCP. diff --git a/meta.md b/meta.md index 66cbff6..84dc3d1 100644 --- a/meta.md +++ b/meta.md @@ -6,7 +6,7 @@ There are now between 1500 and 3000 pages of RFC documents describing DNS, containing around 1700 'MUST' statements. Not only are there a lot of documents, the earlier ones are not that easy to -read for newcomers, and contain a lot of obsoleted bagage that new readers +read for newcomers, and contain a lot of obsoleted baggage that new readers do not know they can skip. Inspired by the wonderful books by W. Richard Stevens (like [TCP diff --git a/stub.md b/stub.md index ded8665..03814f6 100644 --- a/stub.md +++ b/stub.md @@ -19,7 +19,7 @@ resolver a stub talks to should take care of everything. XXX - where does it say so? A few things do matter. For security purposes, the stub resolver must take -good care to fully randomise source port and ID fields. It must also guard +good care to fully randomize source port and ID fields. It must also guard against sending out multiple equivalent queries at the same time as this would allow a 'birthday attack' that could spoof in harmful answers.