Unit Instance

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolsdns/cs/?format=api",
    "source": [
        "The `RD` (recursion desired) bit is set by a client when it sends a query to a resolver. Such a query is said to be `recursive` because the resolver will recursively traverse the DNS hierarchy to retrieve the answer on behalf of the client. In the past, all resolvers were configured to perform recursive queries on behalf of any Internet host. However, this exposes the resolvers to several security risks. The simplest one is that the resolver could become overloaded by having too many recursive queries to process. Most resolvers [#f8888]_ only allow recursive queries from clients belonging to their company or network and discard all other recursive queries. The `RA` bit indicates whether the server supports recursion. The `RCODE` is used to distinguish between different types of errors. See :rfc:`1035` for additional details. The last four fields indicate the size of the `Question`, `Answer`, `Authority` and `Additional` sections of the DNS message."
    ],
    "previous_source": "",
    "target": [
        ""
    ],
    "id_hash": -3961963045371250305,
    "content_hash": -3961963045371250305,
    "location": "../../protocols/dns.rst:40",
    "context": "",
    "note": "",
    "flags": "",
    "state": 0,
    "fuzzy": false,
    "translated": false,
    "approved": false,
    "position": 10,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 153,
    "source_unit": "https://weblate.info.ucl.ac.be/api/units/34975/?format=api",
    "priority": 100,
    "id": 19966,
    "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/protocolsdns/cs/?checksum=4904479a036bf97f",
    "url": "https://weblate.info.ucl.ac.be/api/units/19966/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2019-10-14T10:41:48.495084+02:00"
}