Changes in cnp3-ebook/protocols/dns @ Weblate

None Resource update cnp3-ebook / protocols/dns — English	File `locale/pot/protocols/dns.pot` was added. a year ago
None String updated in the repository cnp3-ebook / protocols/dns — English	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. English 754 characters edited Current translation Read only 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. a year ago
None String updated in the repository cnp3-ebook / protocols/dns — English	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. English 406 characters edited Current translation Read only 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. a year ago
None String updated in the repository cnp3-ebook / protocols/dns — English	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. English 328 characters edited Current translation Read only 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. a year ago
None String updated in the repository cnp3-ebook / protocols/dns — English	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`. English 945 characters edited Current translation Read only 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`. a year ago
None String updated in the repository cnp3-ebook / protocols/dns — English	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. English 453 characters edited Current translation Read only 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. a year ago
None String updated in the repository cnp3-ebook / protocols/dns — English	English The header of DNS messages is composed of 12 bytes. The figure below presents its structure. English 92 characters edited Current translation Read only The header of DNS messages is composed of 12 bytes. The figure below presents its structure. a year ago
None String updated in the repository cnp3-ebook / protocols/dns — English	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. English 765 characters edited Current translation Read only 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. a year ago
None String updated in the repository cnp3-ebook / protocols/dns — English	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. English 491 characters edited Current translation Read only 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. a year ago
None String updated in the repository cnp3-ebook / protocols/dns — English	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`. English 157 characters edited Current translation Read only 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`. a year ago
None New alert cnp3-ebook / protocols/dns	Could not update the repository. a year ago
None New alert cnp3-ebook / protocols/dns	Repository outdated. a year ago
None New alert cnp3-ebook / protocols/dns	Repository outdated. 2 years ago
gegoa Removed translation cnp3-ebook / protocols/dns	locale/en/LC_MESSAGES/protocols/dns.po 2 years ago
gegoa Committed changes cnp3-ebook / protocols/dns — French	Committed changes 2 years ago
gegoa Translation changed cnp3-ebook / protocols/dns — French	English Footnotes French 4 characters edited Current translation Notes de ~~bas~~pied de page 2 years ago
gegoa New contributor cnp3-ebook / protocols/dns — French	New contributor 2 years ago
None New alert cnp3-ebook / protocols/dns	Repository has changes. 2 years ago
None New alert cnp3-ebook / protocols/dns	Repository has changes. 2 years ago
None New alert cnp3-ebook / protocols/dns	Repository has changes. 2 years ago

2 / 7

/ 7

Search

Project

Language

Action

Author username

Starting date

Ending date