privacyguides/i18n
1
0
Fork 0
mirror of https://github.com/privacyguides/i18n.git synced 2025-09-05 12:58:47 +00:00
Code Activity

New Crowdin translations by GitHub Action

Browse Source
This commit is contained in:
Crowdin Bot
2023-11-13 10:35:14 +00:00
parent 79b34bc3dc
commit afe9a83019
32 changed files with 94 additions and 94 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
i18n/ja/advanced/dns-overview.md
View File

@@ -295,20 +295,20 @@ DNSSEC implements a hierarchical digital signing policy across all layers of DNS
A QNAME is a "qualified name", for example `discuss.privacyguides.net`. In the past, when resolving a domain name your DNS resolver would ask every server in the chain to provide any information it has about your full query. In this example below, your request to find the IP address for `discuss.privacyguides.net` gets asked of every DNS server provider:
| サーバー | Question Asked | 回答 |
| ---------------------- | ------------------------------------------- | ------------------------------------------- |
| Root server | What's the IP of discuss.privacyguides.net? | I don't know, ask .net's server... |
| .netのサーバー | What's the IP of discuss.privacyguides.net? | I don't know, ask Privacy Guides' server... |
| Privacy Guides' server | What's the IP of discuss.privacyguides.net? | 5.161.195.190! |
| サーバー | 質問 | 回答 |
| ------------------- | ------------------------------------------- | ------------------------------------------- |
| Root server | What's the IP of discuss.privacyguides.net? | I don't know, ask .net's server... |
| .netのサーバー | What's the IP of discuss.privacyguides.net? | I don't know, ask Privacy Guides' server... |
| Privacy Guidesのサーバー | What's the IP of discuss.privacyguides.net? | 5.161.195.190! |
With "QNAME minimization," your DNS resolver now only asks for just enough information to find the next server in the chain. In this example, the root server is only asked for enough information to find the appropriate nameserver for the .net TLD, and so on, without ever knowing the full domain you're trying to visit:
| サーバー | Question Asked | 回答 |
| ---------------------- | ---------------------------------------------------- | --------------------------------- |
| Root server | What's the nameserver for .net? | *Provides .net's server* |
| .netのサーバー | What's the nameserver for privacyguides.net? | *Provides Privacy Guides' server* |
| Privacy Guides' server | What's the nameserver for discuss.privacyguides.net? | This server! |
| Privacy Guides' server | What's the IP of discuss.privacyguides.net? | 5.161.195.190 |
| サーバー | 質問 | 回答 |
| ------------------- | ---------------------------------------------------- | --------------------------------- |
| Root server | What's the nameserver for .net? | *Provides .net's server* |
| .netのサーバー | What's the nameserver for privacyguides.net? | *Provides Privacy Guides' server* |
| Privacy Guidesのサーバー | What's the nameserver for discuss.privacyguides.net? | This server! |
| Privacy Guidesのサーバー | What's the IP of discuss.privacyguides.net? | 5.161.195.190 |
While this process can be slightly more inefficient, in this example neither the central root nameservers nor the TLD's nameservers ever receive information about your *full* query, thus reducing the amount of information being transmitted about your browsing habits. Further technical description is defined in [RFC 7816](https://datatracker.ietf.org/doc/html/rfc7816).