<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.1" version="1.1">
  <file original="NoName" source-language="en" datatype="plaintext" target-language="en">
    <body>
      <trans-unit xml:space="preserve" approved="no" id="cf2e26085914ec6f" weblate-flags="read-only">
        <source>Application layer</source>
        <target state="translated">Application layer</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">7</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="9b6f337142a69384" weblate-flags="read-only">
        <source>This is an unpolished draft of the third edition of this e-book. If you find any error or have suggestions to improve the text, please create an issue via https://github.com/CNP3/ebook/issues?milestone=5 or help us by providing pull requests to close the existing issues.</source>
        <target state="translated">This is an unpolished draft of the third edition of this e-book. If you find any error or have suggestions to improve the text, please create an issue via https://github.com/CNP3/ebook/issues?milestone=5 or help us by providing pull requests to close the existing issues.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">11</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="fb3f867d7950123d" weblate-flags="read-only">
        <source>The DNS</source>
        <target state="translated">The DNS</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">15</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="d24b48e1a8137f17" weblate-flags="read-only">
        <source>The Domain Name System (DNS) plays a key role in the Internet today as it allows applications to use fully qualified domain names (FQDN) instead of IPv4 or IPv6 addresses. When using the DNS, it is important to remember the role of the different types of DNS records.</source>
        <target state="translated">The Domain Name System (DNS) plays a key role in the Internet today as it allows applications to use fully qualified domain names (FQDN) instead of IPv4 or IPv6 addresses. When using the DNS, it is important to remember the role of the different types of DNS records.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">17</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="5865a4de15a4b905" weblate-flags="read-only">
        <source>Several software tools can be used to send queries to DNS servers. For this exercise, we use dig_ which is installed on most Unix/Linux systems.</source>
        <target state="translated">Several software tools can be used to send queries to DNS servers. For this exercise, we use dig_ which is installed on most Unix/Linux systems.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">25</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2f875ccc4ffcd3f6" weblate-flags="read-only">
        <source>A typical usage of dig is as follows:</source>
        <target state="translated">A typical usage of dig is as follows:</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">27</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="48c5823507c1ba62" weblate-flags="read-only">
        <source>where</source>
        <target state="translated">where</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">33</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2a01379176c9156f" weblate-flags="read-only">
        <source>`server` is the IP address or the name of a DNS server or resolver</source>
        <target state="translated">`server` is the IP address or the name of a DNS server or resolver</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">35</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c580e26be89952d5" weblate-flags="read-only">
        <source>`type` is the type of DNS record that is requested by the query such as `NS` for a nameserver, `A` for an IPv4 address, `AAAA` for an IPv6 address, `MX` for a mail relay, ...</source>
        <target state="translated">`type` is the type of DNS record that is requested by the query such as `NS` for a nameserver, `A` for an IPv4 address, `AAAA` for an IPv6 address, `MX` for a mail relay, ...</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">36</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c3f7142a1b2b7191" weblate-flags="read-only">
        <source>`fqdn` is the fully qualified domain name being queried</source>
        <target state="translated">`fqdn` is the fully qualified domain name being queried</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">37</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="596c8380bb36ec77" weblate-flags="read-only">
        <source>dig_ also contains some additional parameters and flags that are described in the man page. Among these, the `+trace` flag allows to trace all requests that are sent when recursively contacting DNS servers.</source>
        <target state="translated">dig_ also contains some additional parameters and flags that are described in the man page. Among these, the `+trace` flag allows to trace all requests that are sent when recursively contacting DNS servers.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">39</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ef30a4037e0835f5" weblate-flags="read-only">
        <source>What are the IP addresses of the resolvers that the `dig` implementation you are using relies on [#fdig]_ ?</source>
        <target state="translated">What are the IP addresses of the resolvers that the `dig` implementation you are using relies on [#fdig]_ ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">41</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="704fe554928b64c8" weblate-flags="read-only">
        <source>What are the nameservers that are responsible for the `info` top-level domain ? Is it possible to use IPv6 to query them ?</source>
        <target state="translated">What are the nameservers that are responsible for the `info` top-level domain ? Is it possible to use IPv6 to query them ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">43</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="e47ccaf7e9ddc736" weblate-flags="read-only">
        <source>What is the IPv6 address that corresponds to `www.computer-networking.info` ? Which type of DNS query does `dig` send to obtain this information ?</source>
        <target state="translated">What is the IPv6 address that corresponds to `www.computer-networking.info` ? Which type of DNS query does `dig` send to obtain this information ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">45</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c06ecaac2e038af9" weblate-flags="read-only">
        <source>When run without any parameter, `dig` queries one of the root DNS servers and retrieves the list of the names of all root DNS servers. For technical reasons, there are only 13 different root DNS servers. This information is also available as a text file from http://www.internic.net/zones/named.root. What are the IPv6 addresses of all these servers?</source>
        <target state="translated">When run without any parameter, `dig` queries one of the root DNS servers and retrieves the list of the names of all root DNS servers. For technical reasons, there are only 13 different root DNS servers. This information is also available as a text file from http://www.internic.net/zones/named.root. What are the IPv6 addresses of all these servers?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">48</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="01b496d2e4884070" weblate-flags="read-only">
        <source>Assume now that you are residing in a network where there is no DNS resolver and that you need to perform your query manually starting from the DNS root.</source>
        <target state="translated">Assume now that you are residing in a network where there is no DNS resolver and that you need to perform your query manually starting from the DNS root.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">50</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="9814b4379bb8f9fb" weblate-flags="read-only">
        <source>Use `dig` to send a query to one of these root servers to find the IPv6 address of the DNS server(s) (NS record) responsible for the `org` top-level domain</source>
        <target state="translated">Use `dig` to send a query to one of these root servers to find the IPv6 address of the DNS server(s) (NS record) responsible for the `org` top-level domain</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">52</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="4d3333a5477c97f6" weblate-flags="read-only">
        <source>Use `dig` to send a query to one of these DNS servers to find the IP address of the DNS server(s) (NS record) responsible for `root-servers.org`</source>
        <target state="translated">Use `dig` to send a query to one of these DNS servers to find the IP address of the DNS server(s) (NS record) responsible for `root-servers.org`</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">53</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ac12f8abcfeba662" weblate-flags="read-only">
        <source>Continue until you find the server responsible for `www.root-servers.org`</source>
        <target state="translated">Continue until you find the server responsible for `www.root-servers.org`</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">54</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="5c577fdf5f17ce94" weblate-flags="read-only">
        <source>What is the lifetime associated to this IPv6 address ?</source>
        <target state="translated">What is the lifetime associated to this IPv6 address ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">55</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="092fdf3f62c20ab8" weblate-flags="read-only">
        <source>Perform the same analysis for a popular website such as `www.google.com`. What is the lifetime associated to the corresponding IPv6 address ? If you perform the same request several times, do you always receive the same answer ? Can you explain why a lifetime is associated to the DNS replies ?</source>
        <target state="translated">Perform the same analysis for a popular website such as `www.google.com`. What is the lifetime associated to the corresponding IPv6 address ? If you perform the same request several times, do you always receive the same answer ? Can you explain why a lifetime is associated to the DNS replies ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">57</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="abc22df97a0d873e" weblate-flags="read-only">
        <source>Use `dig` to find the mail relays used by the `uclouvain.be` and `student.uclouvain.be` domains. What is the `TTL` of these records ? Can you explain the preferences used by the `MX` records. You can find more information about the MX records in :rfc:`5321`.</source>
        <target state="translated">Use `dig` to find the mail relays used by the `uclouvain.be` and `student.uclouvain.be` domains. What is the `TTL` of these records ? Can you explain the preferences used by the `MX` records. You can find more information about the MX records in :rfc:`5321`.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">59</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="d7a0a3bf16971af4" weblate-flags="read-only">
        <source>When `dig` is run, the header section in its output indicates the `id` the DNS identifier used to send the query. Does your implementation of `dig` generates random identifiers ?</source>
        <target state="translated">When `dig` is run, the header section in its output indicates the `id` the DNS identifier used to send the query. Does your implementation of `dig` generates random identifiers ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">61</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c44725fbacd0d8f6" weblate-flags="read-only">
        <source>A DNS implementation such as `dig`, and more importantly a name resolver such as bind_ or unbound_, always checks that the received DNS reply contains the same identifier as the DNS request that it sent. Why is this so important ?</source>
        <target state="translated">A DNS implementation such as `dig`, and more importantly a name resolver such as bind_ or unbound_, always checks that the received DNS reply contains the same identifier as the DNS request that it sent. Why is this so important ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">73</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="4aeefbe4ceebecab" weblate-flags="read-only">
        <source>Imagine an attacker who is able to send forged DNS replies to, for example, associate `www.bigbank.com` to his own IP address. How could he attack a DNS implementation that</source>
        <target state="translated">Imagine an attacker who is able to send forged DNS replies to, for example, associate `www.bigbank.com` to his own IP address. How could he attack a DNS implementation that</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">75</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="6ff6583b102f7b40" weblate-flags="read-only">
        <source>sends DNS requests containing always the same identifier</source>
        <target state="translated">sends DNS requests containing always the same identifier</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">77</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="13e89adde7cc1fd5" weblate-flags="read-only">
        <source>sends DNS requests containing identifiers that are incremented by one after each request</source>
        <target state="translated">sends DNS requests containing identifiers that are incremented by one after each request</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">78</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="83ad5e555c5d5774" weblate-flags="read-only">
        <source>sends DNS requests containing random identifiers</source>
        <target state="translated">sends DNS requests containing random identifiers</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">79</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="db32137a801bef56" weblate-flags="read-only">
        <source>The DNS protocol can run over UDP and over TCP. Most DNS servers prefer to use UDP because it consumes fewer resources on the server. However, TCP is useful when a large answer is expected. Compare `time dig +tcp` and `time dig` to query a root DNS server. Is it faster to receive an answer via TCP or via UDP ?</source>
        <target state="translated">The DNS protocol can run over UDP and over TCP. Most DNS servers prefer to use UDP because it consumes fewer resources on the server. However, TCP is useful when a large answer is expected. Compare `time dig +tcp` and `time dig` to query a root DNS server. Is it faster to receive an answer via TCP or via UDP ?</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">81</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="40abc37d478bca53" weblate-flags="read-only">
        <source>Besides `dig`, another way to analyze the DNS is to look at packet traces with tools such as `wireshark &lt;https://www.wireshark.org&gt;`_ or `tcpdump &lt;https://www.tcpdump.org&gt;`_ These tools can capture packets in a network and also display and analyze their content. `Wireshark &lt;https://www.wireshark.org&gt;`_  provides a flexible Graphical User Interface that eases the analysis of the captured packets. The three questions below should help you to better understand the important fields of DNS messages.</source>
        <target state="translated">Besides `dig`, another way to analyze the DNS is to look at packet traces with tools such as `wireshark &lt;https://www.wireshark.org&gt;`_ or `tcpdump &lt;https://www.tcpdump.org&gt;`_ These tools can capture packets in a network and also display and analyze their content. `Wireshark &lt;https://www.wireshark.org&gt;`_  provides a flexible Graphical User Interface that eases the analysis of the captured packets. The three questions below should help you to better understand the important fields of DNS messages.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">84</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="9c8e645596dd9240" weblate-flags="read-only">
        <source>The next three questions ask you to go one step further by predicting the values of specific fields in the DNS messages.</source>
        <target state="translated">The next three questions ask you to go one step further by predicting the values of specific fields in the DNS messages.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">93</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="5d3f58c4267aca46" weblate-flags="read-only">
        <source>When a client requests the mapping of a domain name into an IP address to its local resolver, the resolver may need to query a large number of nameservers starting from the root nameserver. The three exercises below show packet traces collected while the resolver was resolving the following names: `www.example.com`, `www.google.com` and `www.computer-networking.info`. If you understand how the DNS operates, you should be able to correctly reorder those packet traces.</source>
        <target state="translated">When a client requests the mapping of a domain name into an IP address to its local resolver, the resolver may need to query a large number of nameservers starting from the root nameserver. The three exercises below show packet traces collected while the resolver was resolving the following names: `www.example.com`, `www.google.com` and `www.computer-networking.info`. If you understand how the DNS operates, you should be able to correctly reorder those packet traces.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">101</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="c463aea6549199a2" weblate-flags="read-only">
        <source>Footnotes</source>
        <target state="translated">Footnotes</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">112</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="02827427a667a8b4" weblate-flags="read-only">
        <source>On a Linux machine, the *Description* section of the `dig` man page tells you where `dig` finds the list of nameservers to query.</source>
        <target state="translated">On a Linux machine, the *Description* section of the `dig` man page tells you where `dig` finds the list of nameservers to query.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">113</context>
        </context-group>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="faeb691b0b2cb1bc" weblate-flags="read-only">
        <source>You may obtain additional information about the root DNS servers from http://www.root-servers.org</source>
        <target state="translated">You may obtain additional information about the root DNS servers from http://www.root-servers.org</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">../../exercises/dns.rst</context>
          <context context-type="linenumber">115</context>
        </context-group>
      </trans-unit>
    </body>
  </file>
</xliff>
