Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English This language is used for source strings. This component is linked to the cnp3-ebook/index repository. CC-BY-SA-3.0 0 0 0 0 0 0 0
Czech This component is linked to the cnp3-ebook/index repository. CC-BY-SA-3.0 0% 15 733 4,719 15 0 0 0
French This component is linked to the cnp3-ebook/index repository. CC-BY-SA-3.0 0 0 0 0 1 0 0
Please sign in to see the alerts.

Overview

Project website www.computer-networking.info
Project maintainers User avatar obonaventure User avatar qdeconinck
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Source code repository https://github.com/cnp3/ebook
Repository branch master
Last remote commit Merge pull request #128 from aaaaalbert/fix-typos-in-preface 00ed7a4
Olivier Bonaventure authored 2 months ago
Weblate repository https://weblate.info.ucl.ac.be/git/cnp3-ebook/index/
File mask locale/*/LC_MESSAGES/protocols/dns.po

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 54 2,913 18,548
Source 24 1,447 9,110
Translated 72% 39 74% 2,180 74% 13,829
Needs editing 0% 0 0% 0 0% 0
Read-only 44% 24 49% 1,447 49% 9,110
Failing checks 1% 1 1% 1 1% 9
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 27% 15 25% 733 25% 4,719
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 1 change 1 change 15 changes 0 changes 4 changes 0 changes 3 changes 0 changes 33 changes 0 changes 8 changes 1 change 4 changes 0 changes 10 changes 0 changes 0 changes 11 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

2,913
Hosted words
54
Hosted strings
72%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar None

Resource update

cnp3-ebook / protocols/dns — English

File locale/pot/protocols/dns.pot was added. 2 months ago
User avatar None

String updated in the repository

cnp3-ebook / protocols/dns — English

An important point to note regarding the Domain Name System it that it is extensible. Thanks to the `Type` and `RDLength` fields, the format of the Resource Records can easily be extended. Furthermore, a DNS implementation that receives a new Resource Record that it does not understand can ignore the record while still being able to process the other parts of the message. This allows, for example, a DNS server that only supports IPv6 to safely ignore the IPv4 addresses listed in the DNS reply for `www.ietf.org` while still being able to correctly parse the Resource Records that it understands. This allowed the Domain Name System to evolve over the years while still preserving the backward compatibility with already deployed DNS implementations.
An important point to note regarding the Domain Name System it that it is extensible. Thanks to the `Type` and `RDLength` fields, the format of the Resource Records can easily be extended. Furthermore, a DNS implementation that receives a new Resource Record that it does not understand can ignore the record while still being able to process the other parts of the message. This allows, for example, a DNS server that only supports IPv6 to safely ignore the IPv4 addresses listed in the DNS reply for `www.ietf.org` while still being able to correctly parse the Resource Records that it understands. This allowed the Domain Name System to evolve over the years while still preserving the backward compatibility with already deployed DNS implementations.
2 months ago
User avatar None

String updated in the repository

cnp3-ebook / protocols/dns — English

Several types of DNS RR are used in practice. The `A` type encodes the IPv4 address that corresponds to the specified name. The `AAAA` type encodes the IPv6 address that corresponds to the specified name. A `NS` record contains the name of the DNS server that is responsible for a given domain. For example, a query for the `AAAA` record associated to the `www.ietf.org` name returned the following answer.
Several types of DNS RR are used in practice. The `A` type encodes the IPv4 address that corresponds to the specified name. The `AAAA` type encodes the IPv6 address that corresponds to the specified name. A `NS` record contains the name of the DNS server that is responsible for a given domain. For example, a query for the `AAAA` record associated to the `www.ietf.org` name returned the following answer.
2 months ago
User avatar None

String updated in the repository

cnp3-ebook / protocols/dns — English

In a `Resource Record` (`RR`), the `Name` indicates the name of the node to which this resource record pertains. The two-)bytes `Type` field indicates the type of resource record. The `Class` field was used to support the utilization of the DNS in other environments than the Internet. The `IN` `Class` refers to Internet names.
In a `Resource Record` (`RR`), the `Name` indicates the name of the node to which this resource record pertains. The two-)bytes `Type` field indicates the type of resource record. The `Class` field was used to support the utilization of the DNS in other environments than the Internet. The `IN` `Class` refers to Internet names.
2 months ago
User avatar None

String updated in the repository

cnp3-ebook / protocols/dns — English

The `AA` bit is set when the server that sent the response has `authority` for the domain name found in the question section. In the original DNS deployments, two types of servers were considered : `authoritative` servers and `non-authoritative` servers. The `authoritative` servers are managed by the system administrators responsible for a given domain. They always store the most recent information about a domain. `Non-authoritative` servers are servers or resolvers that store DNS information about external domains without being managed by the owners of a domain. They may thus provide answers that are out of date. From a security point of view, the `authoritative` bit is not an absolute indication about the validity of an answer. Securing the Domain Name System is a complex problem that was only addressed satisfactorily recently by the utilization of cryptographic signatures in the DNSSEC extensions to DNS described in :rfc:`4033`.
The `AA` bit is set when the server that sent the response has `authority` for the domain name found in the question section. In the original DNS deployments, two types of servers were considered : `authoritative` servers and `non-authoritative` servers. The `authoritative` servers are managed by the system administrators responsible for a given domain. They always store the most recent information about a domain. `Non-authoritative` servers are servers or resolvers that store DNS information about external domains without being managed by the owners of a domain. They may thus provide answers that are out of date. From a security point of view, the `authoritative` bit is not an absolute indication about the validity of an answer. Securing the Domain Name System is a complex problem that was only addressed satisfactorily recently by the utilization of cryptographic signatures in the DNSSEC extensions to DNS described in :rfc:`4033`.
2 months ago
User avatar None

String updated in the repository

cnp3-ebook / protocols/dns — English

The DNS header contains a series of flags. The `QR` flag is used to distinguish between queries and responses. It is set to `0` in DNS queries and `1` in DNS answers. The `Opcode` is used to specify the query type. For instance, a :term:`standard query` is used when a client sends a `name` and the server returns the corresponding `data`. An update request is used when the client sends a `name` and new `data` and the server then updates its database.
The DNS header contains a series of flags. The `QR` flag is used to distinguish between queries and responses. It is set to `0` in DNS queries and `1` in DNS answers. The `Opcode` is used to specify the query type. For instance, a :term:`standard query` is used when a client sends a `name` and the server returns the corresponding `data`. An update request is used when the client sends a `name` and new `data` and the server then updates its database.
2 months ago
User avatar None

String updated in the repository

cnp3-ebook / protocols/dns — English

The header of DNS messages is composed of 12 bytes. The figure below presents its structure.
The header of DNS messages is composed of 12 bytes. The figure below presents its structure.
2 months ago
User avatar None

String updated in the repository

cnp3-ebook / protocols/dns — English

DNS messages are composed of five parts that are named sections in :rfc:`1035`. The first three sections are mandatory and the last two sections are optional. The first section of a DNS message is its `Header`. It contains information about the message type and the content of the other sections. The second section contains the `Question` sent to the nameserver or resolver. The third section contains the `Answer` to the `Question`. When a client sends a DNS query, the `Answer` section is empty. The fourth section, named `Authority`, contains information about the servers that can provide an authoritative answer if required. The last section contains additional information that is supplied by the resolver or nameserver but was not requested in the question.
DNS messages are composed of five parts that are named sections in :rfc:`1035`. The first three sections are mandatory and the last two sections are optional. The first section of a DNS message is its `Header`. It contains information about the message type and the content of the other sections. The second section contains the `Question` sent to the nameserver or resolver. The third section contains the `Answer` to the `Question`. When a client sends a DNS query, the `Answer` section is empty. The fourth section, named `Authority`, contains information about the servers that can provide an authoritative answer if required. The last section contains additional information that is supplied by the resolver or nameserver but was not requested in the question.
2 months ago
User avatar None

String updated in the repository

cnp3-ebook / protocols/dns — English

The last component of the Domain Name System is the DNS protocol. The original DNS protocol runs above both the datagram and the bytestream services. In practice, the datagram service is used when short queries and responses are exchanged, and the bytestream service is used when longer responses are expected. In this section, we first focus on the utilization of the DNS protocol above the datagram service. We will discuss later other recently proposed protocols to carry DNS information.
The last component of the Domain Name System is the DNS protocol. The original DNS protocol runs above both the datagram and the bytestream services. In practice, the datagram service is used when short queries and responses are exchanged, and the bytestream service is used when longer responses are expected. In this section, we first focus on the utilization of the DNS protocol above the datagram service. We will discuss later other recently proposed protocols to carry DNS information.
2 months ago
User avatar None

String updated in the repository

cnp3-ebook / protocols/dns — English

We have already explained the main principles that underlie the utilization of names on the Internet and their mapping to addresses in section :ref:`naming`.
We have already explained the main principles that underlie the utilization of names on the Internet and their mapping to addresses in section :ref:`naming`.
2 months ago
Browse all component changes