Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some textual additions #37

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Some textual additions #37

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions auth.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,14 +214,24 @@ periodically check the master server to find out if there have been any
updates that need to be retrieved.

Since this periodic check may be far in the future, optionally master
servers can send out notifications when they load new zone data.
servers can send out notifications when they load new zone data, thus
reducing the latency in propagating changes to the contents of a zone.

Notification was not in 1034/1035 and is described well in [RFC
1996](https://tools.ietf.org/html/rfc1996).

In short, a notification is a regular DNS message, sent out as a query, but
then with OPCODE=5. Notifications are repeated until acknowledged by the
slave server.
then with OpCode=4 [Domain Name System (DNS) Parameters](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-5).
Notifications are repeated until acknowledged by the slave server.

## Replication continued: incremental zone transfers
The zone transfer mechanism (AXFR) is not an efficient means to propagate
changes to a small part of a zone, as it transfers the entire zone file.

Incremental transfer (IXFR) is a more efficient mechanism, as it transfers
only the changed portion(s) of a zone.

<< Client sends qtype=251 (IXFR) with SOA in additional section >>

# TBC

Expand Down
2 changes: 1 addition & 1 deletion basic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -453,7 +453,7 @@ answer from, which in this case is 'org'. Within the 'org' zone they then
find the 'ietf' node, which again contains an NS RRSET.

When we ask the servers named in that RRSET about 'www.ietf.org', they find
a node called 'www' with several RRSETs on it, one if which is for AAAA and
a node called 'www' with several RRSETs on it, one of which is for AAAA and
contains the IPv6 address we were looking for.

Any authoritative server which does not implement 'zones' in this way will
Expand Down