Added "b23.tv, bilicdn1.com, bilicdn2.com" for bilibili, "douyinpic.com, douyinstatic.com, douyinvod.com" for tiktok.
Removed one redundant "||ixigua.com^" which appeared twice, also sorted tiktok.
Merge in DNS/adguard-home from upd-fmt to master
Squashed commit of the following:
commit 73d9a71feccd8256841ae5a01e4a6aae0bcb2f65
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Aug 31 18:37:39 2022 +0300
all: upd fmt
Updates #4403.
* commit 'd519929988575439c2238924ae5b1d96091445f7':
dnsforward: imp code, fmt
Also honor the user-defined UpstreamMode for the internal DNS proxy
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit d6d55a9a35a8810c6b334d19ba9747fb2b3e7f82
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Aug 19 16:44:18 2022 +0300
all: upd chlog
Merge in DNS/adguard-home from upd-dnsproxy to master
Squashed commit of the following:
commit 3c5b683e96191b9cf0abf35229c3c665370d782e
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Aug 18 18:04:13 2022 +0300
all: upd dnsproxy
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 075a81165f143d4d5886e14d14247ea57abee866
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Aug 17 18:56:38 2022 +0300
all: upd chlog
Merge in DNS/adguard-home from upd-specs to master
Squashed commit of the following:
commit d7ac1dc1ef305098ff741d557c13db8a60ffe1f9
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Mon Aug 15 19:16:51 2022 +0300
bamboo-specs: allow larger keys
Merge in DNS/adguard-home from fix-bamboo-specs to master
Squashed commit of the following:
commit e59b75ab9528bbe8fbf5e15054d848abffbae312
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Mon Aug 15 18:52:10 2022 +0300
all: fix ci frontend build
Merge in DNS/adguard-home from add-ar-i18n to master
Squashed commit of the following:
commit 6ef7c70bceb6f6ebabd81011154022a75fc91bd3
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Aug 10 20:55:39 2022 +0300
client: add ar locale
Merge in DNS/adguard-home from upd-websvc to master
Squashed commit of the following:
commit 30d6a2dc5083efd91479bcbe20f03c37baddbf94
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Aug 9 18:55:42 2022 +0300
all: upd openapi, websvc
Merge in DNS/adguard-home from udp-chlog to master
Squashed commit of the following:
commit 1c8dbff75c8377c352f6fedd18699f151a087f2b
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Aug 3 17:19:18 2022 +0300
all: upd chlog
Merge in DNS/adguard-home from 4517-warning-label to master
Updates #4517.
Squashed commit of the following:
commit 4987f63937253da2954cf20c7b99a3b8a0adf112
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Mon Aug 1 13:59:28 2022 +0300
client: imp wording
Merge in DNS/adguard-home from upd-domains-and-links to master
Squashed commit of the following:
commit 5e5ff2fec358104995877da689da24749ac470ce
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Jul 28 19:53:19 2022 +0300
all: upd urls
Update domains and URLs to make them more resistant to state blocking.
Merge in DNS/adguard-home from upd-go to master
Squashed commit of the following:
commit 132358d69178050ca2eacf8a988b4e4cb0e0ef57
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Jul 13 13:29:07 2022 +0300
all: upd go
Merge in DNS/adguard-home from upd-i18n to master
Squashed commit of the following:
commit 0d2956422f6b417b0a58da176315818a92e8c466
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Mon Jun 27 15:42:07 2022 +0300
client: upd i18n
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 1ca912f4be4a452abc0c8c95a8d6022d547b3394
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Mon Jun 6 18:35:12 2022 +0300
all: upd chlog
Merge in DNS/adguard-home from upd-dnsproxy-quic-fix to master
Squashed commit of the following:
commit a6ffa24769259c73e397e02d087dc155ed58a3e2
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Mon Jun 6 15:06:00 2022 +0300
all: fix quic reply id
Merge in DNS/adguard-home from upd-i18n to master
Squashed commit of the following:
commit 3feadfe31609ef52726b582ad6ba18bfa435a081
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Jun 3 16:34:36 2022 +0300
client: upd i18n
Merge in DNS/adguard-home from upd-go to master
Squashed commit of the following:
commit b0bec8926508fb7ee3f26c2303d9628e21f0b62f
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Jun 2 15:47:51 2022 +0300
all: upd go
Merge in DNS/adguard-home from fix-ddr-doh to master
Squashed commit of the following:
commit 53d3147b22044061d78b3bf4badca60505ac245a
Author: Dimitry Kolyshev <dkolyshev@adguard.com>
Date: Tue May 31 15:02:17 2022 +0200
all: fix doh ddr
Merge in DNS/adguard-home from 4592-doq-status to master
Squashed commit of the following:
commit 96bc041b736a45711419160aebb79296f13ff84d
Author: Dimitry Kolyshev <dkolyshev@adguard.com>
Date: Thu May 26 14:21:10 2022 +0200
all: locales
Merge in DNS/adguard-home from upd-i18n to master
Squashed commit of the following:
commit 7ddd8cb01f8136ad4690a439ee3b810043af749e
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu May 26 14:10:31 2022 +0300
client: upd i18n
Merge in DNS/adguard-home from help-wanted-stale to master
Squashed commit of the following:
commit 1c5ffcdd0153dd7d9d9bcc1e35dee4a0b3113f59
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Apr 22 20:04:01 2022 +0300
all: do not mark help-wanted issues as stale
Merge in DNS/adguard-home from 700-validate to master
Updates #700.
Squashed commit of the following:
commit 9cd9ff2d23352e00c7782cf68195809111c832e5
Author: Ildar Kamalov <ik@adguard.com>
Date: Wed Apr 6 18:50:11 2022 +0300
client: validate only enabled encryption form
Merge in DNS/adguard-home from fix-is-timeout to master
Squashed commit of the following:
commit b0fefd01f27a835a34e44beb2eb2c34027960a51
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Mar 29 15:57:06 2022 +0300
aghnet: fix catching timeout errors
Merge in DNS/adguard-home from cn-sumdb to master
Squashed commit of the following:
commit 439973292f473efa72fb6a733a32be45e634274e
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Mon Mar 28 16:51:28 2022 +0300
Makefile: add go sumdb env
Merge in DNS/adguard-home from 3142-custom-subnets to master
Updates #3142.
Squashed commit of the following:
commit 11469ade75b9dc32ee6d93e3aa35cf79dbaa28b2
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Thu Mar 17 19:56:02 2022 +0300
all: upd golibs, use subnet set
Merge in DNS/adguard-home from 2145-optimistic-ttl to master
Updates #2145.
Squashed commit of the following:
commit 81e5aba650980403d70d6756aebe73af228fe11a
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Wed Mar 9 18:34:50 2022 +0500
all: upd proxy
Merge in DNS/adguard-home from upd-go to master
Squashed commit of the following:
commit 3b6c960afe073223dd73eaf650561509f0d13019
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Mar 4 15:45:15 2022 +0300
all: upd go
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 5933ed86b41646c61a595c94068890a1675a3ad1
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Mar 1 20:31:47 2022 +0300
all: upd chlog
Merge in DNS/adguard-home from 2643-upd-i18n to master
Squashed commit of the following:
commit 1f36b960877ee2c30319e26132db892fb8a2ef71
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Mar 1 15:05:24 2022 +0300
client: upd i18n
Updates #4244.
Squashed commit of the following:
commit 20d558e9e6935555a13e1aebc7d364e6f1910e9e
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Mon Feb 28 19:01:32 2022 +0300
client: fix link in client form
Merge in DNS/adguard-home from upd-go to master
Squashed commit of the following:
commit 5540d0afd7579a2f2d543afaa96008d12ce1bf3e
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Feb 11 16:15:35 2022 +0300
all: upd go
Merge in DNS/adguard-home from imp-i18n to master
Squashed commit of the following:
commit c58c00383824a88ea8e22a845e422ba2ff7d225e
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Feb 10 20:21:00 2022 +0300
client: imp validation texts
Merge in DNS/adguard-home from upd-i18n to master
Squashed commit of the following:
commit e2f9e9f52a424b7c13beebfc2f8fea3814d3b2f4
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Feb 8 13:48:17 2022 +0300
client: upd i18n
Merge in DNS/adguard-home from 4254-fix-optimistic to master
Updates #4254.
Squashed commit of the following:
commit 652e2c2ab9405b9a6ed5d153b6b508e3b87ce66e
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Mon Feb 7 18:55:34 2022 +0300
all: upd proxy
Merge in DNS/adguard-home from chlog-ms-links to master
Squashed commit of the following:
commit 97156f1452a7713e5e8d66a9b5eeac25fb97ab04
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Feb 4 17:56:58 2022 +0300
all: add gh milestone links to chlog
Closes#4221.
Squashed commit of the following:
commit c84a5699280cf4c0b1c2ed034a44f05ffc74d30d
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Feb 1 21:13:30 2022 +0300
all: switch to SOURCE_DATE_EPOCH for source date
Merge in DNS/adguard-home from upd-quic-go to master
Squashed commit of the following:
commit c7f0ab02a54ac435b6e0040dd221d819cf3ecdd4
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Feb 1 14:33:26 2022 +0300
all: upd quic-go
Merge in DNS/adguard-home from fix-install to master
Squashed commit of the following:
commit 54c3b18c946c88def396f82a941b0b35eb6ef60d
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Jan 26 19:08:48 2022 +0300
scripts: do not require sudo where not needed
Merge in DNS/adguard-home from fix-chlog to master
Squashed commit of the following:
commit e69da2f574923b95ac3d0fa9057fffe2a716b5be
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Jan 26 14:41:04 2022 +0300
all: fix chlog, imp
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit ad258a27abfce7b1060d9937b446f6e794f8c172
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Jan 25 18:15:59 2022 +0300
all: upd chlog
Merge in DNS/adguard-home from imp-logs to master
Squashed commit of the following:
commit bff4c3757b61db63320af72e1af56649f6f70a50
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Mon Jan 24 17:25:34 2022 +0300
all: upd dnsproxy
Merge in DNS/adguard-home from upd-i18n to master
Squashed commit of the following:
commit e3dfb6cd66813d45591f74c9cdddab8b61143db3
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Mon Jan 24 14:52:19 2022 +0300
client: upd i18n
Closes#4026.
Squashed commit of the following:
commit bcd1315a10e819daee3aee323427d90a27860b4a
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Jan 18 14:57:49 2022 +0300
openapi: fix example
commit b56e27c5ac1fc7c3f595057d77607479d72ec50a
Author: Ildar Kamalov <ik@adguard.com>
Date: Tue Jan 18 14:55:51 2022 +0300
client: show version on install page
commit 95dfbfaa1235deef7b55e51457d11c677f6ef6b5
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Jan 18 14:29:08 2022 +0300
home: show version in install api
Merge in DNS/adguard-home from 4074-upstream-test to master
Updates #4074.
Squashed commit of the following:
commit 0de155b1e175a892b259791ff6d6e6f351bcfcf2
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Wed Jan 12 19:20:01 2022 +0500
dnsforward: fix upstream test
Merge in DNS/adguard-home from 4046-log-dir to master
Closes#4046.
Squashed commit of the following:
commit 05140550b14f477f52487c575f56428ce9e6fa10
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Wed Jan 5 17:54:11 2022 +0500
all: add macOS service msg
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 737525aa065bff7b1ec99876447bbc2f961a4c4d
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Dec 29 23:23:52 2021 +0300
all: upd chlog
Merge in DNS/adguard-home from 3868-changelog to master
Squashed commit of the following:
commit 92ccf7422c4c1342c160e4806cbf9fb17c22749b
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Mon Dec 27 19:22:47 2021 +0300
all: log more changes
Merge in DNS/adguard-home from 3998-fix-hosts-gen to master
Closes#3998
Squashed commit of the following:
commit b565d51afb6c292dd16accd45b7d37ed386714e8
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Thu Dec 23 16:25:02 2021 +0300
aghnet: make hosts rules match exactly
Merge in DNS/adguard-home from upd-dns-lib to master
Updates #2275.
Squashed commit of the following:
commit 54d0485157ac4f08830ad7d8ca9be49eef87d678
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Thu Dec 23 13:31:34 2021 +0300
all: upd dns lib
Merge in DNS/adguard-home from en-i18n-safe-browsing to master
Squashed commit of the following:
commit dd32a58c3761818a10386b4a1d9e6871da59c71e
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Dec 22 17:31:35 2021 +0300
client: imp en i18n
Merge in DNS/adguard-home from temp-disable-notify to master
Squashed commit of the following:
commit c7f1393668e4dfe8681c9ed1c6f2ef45aed9106b
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Dec 22 17:07:37 2021 +0300
all: temp disable gh notifications
"updated_upstream_dns_toast":"تم حفظ خوادم Upstream بنجاح",
"dns_test_ok_toast":"تعمل خوادم DNS المحددة بشكل صحيح",
"dns_test_not_ok_toast":"خادم \"{{key}}\": لا يمكن استخدامه يرجى التحقق من كتابته بشكل صحيح",
"dns_test_warning_toast":"المنبع \"{{key}}\" لا يستجيب لطلبات الاختبار وقد لا يعمل بشكل صحيح",
"unblock":"إلغاء الحظر",
"block":"حظر",
"disallow_this_client":"منع هذا العميل",
@@ -362,6 +366,7 @@
"encryption_config_saved":"تم حفظ اعدادات التشفير",
"encryption_server":"اسم الخادم",
"encryption_server_enter":"ادخل عنوان النطاق الخاص بك",
"encryption_server_desc":"من أجل استخدام HTTPS ، تحتاج إلى إدخال اسم الخادم الذي يتطابق مع شهادة SSL أو شهادة البدل. إذا لم يتم تعيين الحقل ، فسيقبل اتصالات TLS لأي مجال.",
"encryption_redirect":"إعادة التوجيه إلى HTTPS تلقائيًا",
"encryption_redirect_desc":"إذا تم تحديده ، فسيقوم AdGuard Home بإعادة توجيهك تلقائيًا من عناوين HTTP إلى عناوين HTTPS.",
"dhcp_warning":"Калі вы ўсё адно хочаце ўключыць DHCP-сервер, пераканайцеся, што ў сеціве больш няма актыўных DHCP-сервераў. Інакш гэта можа зламаць доступ у сеціва для падлучаных прылад!",
"dhcp_error":"AdGuard Home не можа вызначыць, ці ёсць у сетцы іншы актыўны DHCP-сервер",
"dhcp_static_ip_error":"Для таго, каб выкарыстоўваць DHCP-сервер, павінен быць усталяваны статычны IP-адрас. Мы не змаглі вызначыць, ці выкарыстоўвае гэты інтэрфейс сеціва статычны IP-адрас. Калі ласка, усталюйце яго ручна.",
"dhcp_dynamic_ip_found":"Ваша сістэма выкарыстоўвае дынамічны IP-адрас для інтэрфейсу <0>{{interfaceName}}</0>. Каб выкарыстоўваць DHCP-сервер трэба ўсталяваць статычны IP-адрас. Ваш бягучы IP-адрас – <0>{{ipAddress}}</0>. Мы аўтаматычна ўсталюем яго як статычны, калі вы націснеце кнопку Ўключыць DHCP.",
"dhcp_dynamic_ip_found":"Ваша сістэма выкарыстоўвае дынамічны IP-адрас для інтэрфейсу <0>{{interfaceName}}</0>. Каб выкарыстоўваць DHCP-сервер трэба ўсталяваць статычны IP-адрас. Ваш бягучы IP-адрас – <0>{{ipAddress}}</0>. Мы аўтаматычна ўсталюем яго як статычны, калі вы націснеце кнопку «Ўключыць DHCP».",
"dhcp_lease_added":"Статычная арэнда «{{key}}» паспяхова дададзена",
"dhcp_lease_deleted":"Статычная арэнда «{{key}}» паспяхова выдалена",
"dhcp_new_static_lease":"Новая статычная арэнда",
@@ -211,12 +211,14 @@
"example_comment_hash":"# І вось так таксама.",
"example_regex_meaning":"блакаваць доступ да даменаў, якія адпавядаюць зададзенаму рэгулярнаму выразу.",
"example_upstream_regular":"звычайны DNS (наўзверх UDP);",
"example_upstream_regular_port":"звычайны DNS (праз UDP, імя хаста);",
"example_upstream_udp":"звычайны DNS (праз UDP, імя хаста);",
"access_disallowed_desc":"Спіс CIDR, IP-адрасоў або <a>ClientID</a>. Калі ў гэтым спісе ёсць запісы, AdGuard Home выдаліць запыты ад гэтых кліентаў. Гэта поле ігнаруецца, калі ёсць запісы ў Дазволеныя кліенты.",
"access_blocked_title":"Заблакаваныя дамены",
"access_blocked_desc":"Не блытайце гэта з фільтрамі. AdGuard Home будзе ігнараваць DNS-запыты з гэтымі даменамі.",
"access_blocked_desc":"Не блытаць з фільтрамі. AdGuard Home выдаляе запыты DNS, якія адпавядаюць гэтым даменам, і гэтыя запыты нават не з'яўляюцца ў журнале запытаў. Вы можаце ўказаць дакладныя даменныя імёны, падстаноўныя знакі або правілы фільтрацыі URL-адрасоў, напрыклад, «example.org», «*.example.org» ці «||example.org^» адпаведна.",
"access_settings_saved":"Налады доступу паспяхова захаваны",
"updates_checked":"Даступная новая версія AdGuard Home",
"updates_version_equal":"Версія AdGuard Home актуальная",
"access_disallowed_desc":"Eine Liste von CIDRs, IP-Adressen oder <a>ClientIDs</a>. Wenn diese Liste gefüllt ist, weist AdGuard Home Anfragen von diesen Clients zurück. Dieses Feld wird ignoriert, wenn es Einträge in der Liste „Zugelassene Clients“ gibt.",
"access_blocked_desc":"Verwechseln Sie dies nicht mit Filtern. AdGuard Home verwirft DNS-Abfragen, die mit diesen Domänen übereinstimmen, und diese Abfragen erscheinen nicht einmal im Abfrageprotokoll. Hier können Sie die genauen Domain-Namen, Wildcards und URL-Filter-Regeln angeben, z.B. 'beispiel.org', '*.beispiel.org' oder '||beispiel.org^'.",
"access_blocked_desc":"Verwechseln Sie dies nicht mit Filtern. AdGuard Home verwirft DNS-Abfragen, die mit diesen Domänen übereinstimmen, und diese Abfragen erscheinen nicht einmal im Abfrageprotokoll. Hier können Sie die genauen Domain-Namen, Wildcards und URL-Filter-Regeln angeben, z.B. „example.org“, „*.example.org“ oder „||example.org^“.",
"updates_checked":"Neue Version von AdGuard Home ist jetzt verfügbar",
"updates_version_equal":"AdGuard Home ist aktuell",
@@ -625,7 +627,7 @@
"setup_config_to_enable_dhcp_server":"Einrichten der Konfiguration zur Aktivierung des DHCP-Servers",
"original_response":"Ursprüngliche Antwort",
"click_to_view_queries":"Anklicken, um Abfragen anzuzeigen",
"port_53_faq_link":"Port 53 wird oft von Diensten wie „DNSStubListener“ oder „systemresolved“ belegt. Bitte lesen Sie <0>diese Anweisung</0>, wie dies behoben werden kann.",
"port_53_faq_link":"Port 53 wird oft von Diensten wie „DNSStubListener“ oder „system-resolved“ belegt. Bitte lesen Sie <0>diese Anweisung</0>, wie dies behoben werden kann.",
"adg_will_drop_dns_queries":"AdGuard Home wird alle DNS-Abfragen von diesem Client verwerfen.",
"filter_allowlist":"Warnhinweis: Durch diese Aktion wird außerdem die Regel „{{disallowed_rule}}“ aus der Liste der zugelassenen Clients ausgeschlossen.",
"last_rule_in_allowlist":"Dieser Client kann nicht gesperrt werden, da das Ausschließen der Regel „{{disallowed_rule}}“ die Liste „Zugelassene Clients“ deaktivieren würde.",
"example_upstream_reserved":"میتوانید جریان ارسالی DNS <0> را برای یک دامنه مشخص تعیین کنید </0>",
"example_upstream_comment":"یک نظر.",
"upstream_parallel":"استفاده از جستار موازی برای سرعت دادن به تفکیک با جستار همزمان همه جریان های ارسالی",
"parallel_requests":"درخواست های موازی",
"load_balancing":"متعادل کننده بار",
"bootstrap_dns":"خودراه انداز سرورهای DNS",
"bootstrap_dns_desc":"خودراه انداز سرورهای DNS برای تفکیک آدرس آی پی تفکیک کننده های DoH/DoT که شما بعنوان جریان ارسالی تعیین کردید استفاده میشود.",
"local_ptr_title":"سرورهای خصوصی DNS",
"local_ptr_desc":"سرور یا سرور های DNS ای که AdGuard Home برای درخواست های منابع محلی ارائه شده مورد استفاده قرار خواهد داد. برای مثال، این سرور برای تعیین نام های سرویس دهنده برای سرویس گیرنده با آدرس های آی پی خصوصی مورد استفاده قرار خواهد گرفت. اگر تعیین نشود،AdGuard Home به طور خودکار از تعیین کننده ی DNS پیش فرض شما استفاده خواهد کرد.",
"local_ptr_default_resolver":"به طور پیش فرض، AdGuard Home از تعیین کننده های DNS معکوس زیر استفاده می کند: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home نتوانست برای این دستگاه تعیین کننده های DNS معکوس محرمانه مناسب را معین کند.",
"local_ptr_placeholder":"در هر خط یک آدرس سرور را وارد کنید",
@@ -207,6 +210,9 @@
"dns_test_not_ok_toast":"سرور \"{{key}}\": نمیتواند مورد استفاده قرار گیرد،لطفا بررسی کنید آن را بدرستی نوشته اید",
"unblock":"رفع انسداد",
"block":"مسدود کردن",
"disallow_this_client":"این مشتری را رد کنید",
"allow_this_client":"به این مشتری اجازه دهید",
"block_for_this_client_only":"مسدود کردن فقط برای این مشتری",
"time_table_header":"زمان",
"date":"تاریخ",
"domain_name_table_header":"نام دامنه",
@@ -320,6 +326,7 @@
"install_devices_android_list_5":"گروه مقادیر DNS 1 و DNS 2 را به آدرس سرور AdGuard Home خود تغییر دهید.",
"install_devices_ios_list_1":"از صفحه خانه،تنظیمات را فشار دهید.",
"install_devices_ios_list_2":"وای فای را از منوی چپ انتخاب کنید (پیکربندی DNS دستی برای ارتباط موبایلی غیرممکن است).",
"install_devices_ios_list_3":"روی نام شبکه فعال فعلی کلیک کنید.",
"install_devices_ios_list_4":"در فیلد DNS آدرس سرور AdGuard Home را وارد کنید",
"get_started":"شروع به کار",
"next":"بعدی",
@@ -552,6 +559,7 @@
"safe_search":"جستجوی اَمن",
"blocklist":"لیست سیاه",
"milliseconds_abbreviation":"هـ ثـ",
"cache_size":"اندازه کش",
"cache_optimistic":"حالت ویژه پردازش",
"cache_optimistic_desc":"AdGuard Home را وادار می کند که از سمت حافظه پنهان پاسخ دهد حتی وقتی که موارد وارد شده منقضی شده باشد و همچنین سعی بر تازه کردن آنها می کند.",
"dhcp_error":"AdGuard Home ne peut pas déterminer s'il y a un autre serveur DHCP actif sur le réseau.",
"dhcp_static_ip_error":"Pour utiliser un serveur DHCP, une adresse IP statique est requise. AdGuard Home n'a pas réussi à déterminer si cette interface réseau est configurée via une adresse IP statique. Veuillez définir une adresse IP statique manuellement.",
"dhcp_dynamic_ip_found":"Votre système utilise une configuration d'adresses IP dynamiques pour l'interface <0>{{interfaceName}}</0>. Pour utiliser un serveur DHCP, une adresse IP statique est requise. Votre adresse IP actuelle est <0>{{ipAddress}}</0>. AdGuard Home va automatiquement définir cette adresse IP comme statique si vous appuyez sur le bouton « Activer le serveur DHCP ».",
"dhcp_lease_added":"« {{key}} » de bail statique ajoutée avec succès",
"dhcp_lease_deleted":"« {{key}} » de bail statique supprimée avec succès",
"dhcp_lease_added":"« {{key}} » de bail statique ajoutée",
"dhcp_lease_deleted":"« {{key}} » de bail statique supprimée",
"example_upstream_sdns":"vous pouvez utiliser <0>DNS Stamps</0> pour <1>DNSCrypt</1> ou les résolveurs <2>DNS_over_HTTPS</2> ;",
"example_upstream_tcp":"DNS classique (au-dessus de TCP) ;",
"example_upstream_tcp_port":"DNS normal (sur TCP, avec port) ;",
"example_upstream_tcp_hostname":"DNS normal (sur TCP, nom d’hôte) ;",
"all_lists_up_to_date_toast":"Toutes les listes sont déjà à jour",
"updated_upstream_dns_toast":"Serveurs en amont enregistrés",
"dns_test_ok_toast":"Les serveurs DNS spécifiés fonctionnent correctement",
"dns_test_not_ok_toast":"Impossible d'utiliser le serveur « {{key}} »: veuillez vérifier si le nom saisi est bien correct",
"dns_test_warning_toast":"L'amont «{{key}}» ne répond pas aux demandes de test et peut ne pas fonctionner correctement.",
"dns_test_warning_toast":"L'amont «{{key}}» ne répond pas aux demandes de test et peut ne pas fonctionner correctement",
"unblock":"Débloquer",
"block":"Bloquer",
"disallow_this_client":"Interdire ce client",
@@ -338,7 +340,7 @@
"install_devices_router_list_4":"Vous ne pouvez pas définir un serveur DNS personnalisé sur certains types de routeurs. Dans ce cas, la configuration de AdGuard Home en tant que <0>serveur DHCP</0> peut aider. Sinon, vous devez rechercher le manuel sur la façon de personnaliser les serveurs DNS pour votre modèle de routeur particulier.",
"install_devices_windows_list_1":"Ouvrez votre Panneau de configuration depuis le menu Démarrer ou la recherche Windows.",
"install_devices_windows_list_2":"Allez dans la catégorie Réseau et Internet et ensuite dans le Centre Réseau et Partage.",
"install_devices_windows_list_3":"Dans le panneau de gauche, cliquez sur « Modifier les paramètres de l'adaptateur ».",
"install_devices_windows_list_3":"Cliquez « Modifier les paramètres de l'adaptateur » sur le panneau à gauche.",
"install_devices_windows_list_4":"Cliquez avec le bouton droit de la souris sur votre connexion active et sélectionnez Propriétés.",
"install_devices_windows_list_5":"Recherchez « Protocole Internet Version 4 (TCP/IPv4) » (soit, pour IPv6, « Protocole Internet Version 6 (TCP/IPv6) ») dans la liste, sélectionnez-la puis cliquez à nouveau sur Propriétés.",
"install_devices_windows_list_6":"Sélectionnez « Utiliser l’adresse de serveur DNS suivante » et saisissez votre adresse de serveur AdGuard Home.",
@@ -430,11 +432,11 @@
"form_client_name":"Saisissez le nom du client",
"name":"Nom",
"client_global_settings":"Utiliser les paramètres généraux",
"client_deleted":"Le client « {{key}} » a été supprimé avec succès",
"client_deleted":"Le client « {{key}} » a été supprimé",
"client_added":"Le client « {{key}} » a été ajouté",
"client_updated":"Le client « {{key}} » a été mis à jour",
"clients_not_found":"Aucun client trouvé",
"client_confirm_delete":"Voulez-vous vraiment supprimer le client « {{key}} »?",
"client_confirm_delete":"Voulez-vous vraiment supprimer le client « {{key}} »?",
"list_confirm_delete":"Voulez-vous vraiment supprimer cette liste ?",
"auto_clients_title":"Clients d'exécution",
"auto_clients_desc":"Appareils ne figurant pas sur la liste des clients persistants qui peuvent encore utiliser AdGuard Home.",
@@ -472,7 +474,7 @@
"rewrite_deleted":"Réécriture DNS pour « {{key}} » supprimée",
"rewrite_add":"Ajouter une réécriture DNS",
"rewrite_not_found":"Aucune réécriture DNS trouvée",
"rewrite_confirm_delete":"Voulez-vous vraiment supprimer la réécriture DNS pour « {{key}} »?",
"rewrite_confirm_delete":"Voulez-vous vraiment supprimer la réécriture DNS pour « {{key}} »?",
"rewrite_desc":"Permet de configurer facilement la réponse DNS personnalisée pour un nom de domaine spécifique.",
"rewrite_applied":"Règle de réécriture appliquée",
"rewrite_hosts_applied":"Réécrit par la règle du fichier d’hôtes",
@@ -553,11 +555,11 @@
"disable_ipv6_desc":"Abandonner toutes les requêtes DNS pour les adresses IPv6 (type AAAA).",
"fastest_addr":"Adresse IP la plus rapide",
"fastest_addr_desc":"Rechercher tous les serveurs DNS et renvoyer l’adresse IP la plus rapide parmi toutes les réponses. Cela ralentit les requêtes DNS car AdGuard Home doit attendre les réponses de tous les serveurs DNS, mais la connectivité globale s'améliore.",
"autofix_warning_text":"Si vous cliquez sur « Réparer », AdGuardHome configurera votre système pour utiliser le serveur DNS AdGuardHome.",
"autofix_warning_text":"Si vous cliquez sur « Réparer », AdGuardHome configurera votre système pour utiliser le serveur DNS AdGuardHome.",
"autofix_warning_list":"Ceci effectuera les tâches suivantes : <0>Désactiver le système DNSStubListener</0> <0>Définir l’adresse du serveur DNS à 127.0.0.1 </0> <0>Remplacer la cible du lien symbolique de /etc/resolv.conf par /run/systemd/resolve/resolv.conf</0> <0>Arrêter DNSStubListener (recharger le service résolu par systemd)</0>",
"autofix_warning_result":"Par conséquent, toutes les demandes DNS de votre système seront traitées par AdGuardHome par défaut.",
"tags_title":"Mots clés",
"tags_desc":"Vous pouvez sélectionner les mots clés qui correspondent au client. Les mots clés peuvent être inclus dans les règles de filtrage et vous permettent de les appliquer plus précisément. <0>En savoir plus</0>.",
"tags_desc":"Vous pouvez sélectionner les mots clés qui correspondent au client. Les mots clés peuvent être inclus dans les règles de filtrage et vous permettent de les appliquer plus précisément. <0>En savoir plus</0>.",
"form_select_tags":"Sélectionner les mots clés du client",
"check_title":"Vérification du filtrage",
"check_desc":"Vérifier si le nom d’hôte est filtré .",
@@ -573,10 +575,10 @@
"check_service":"Nom du service : {{service}}",
"service_name":"Nom du service",
"check_not_found":"Introuvable dans vos listes de filtres",
"client_confirm_block":"Voulez-vous vraiment bloquer le client « {{ip}} »?",
"client_confirm_unblock":"Voulez-vous vraiment débloquer le client « {{ip}} »?",
"client_blocked":"Client « {{ip}} » bloqué avec succès",
"client_unblocked":"Client « {{ip}} » débloqué avec succès",
"client_confirm_block":"Voulez-vous vraiment bloquer le client « {{ip}} »?",
"client_confirm_unblock":"Voulez-vous vraiment débloquer le client « {{ip}} »?",
"client_blocked":"Client « {{ip}} » bloqué",
"client_unblocked":"Client « {{ip}} » débloqué",
"static_ip":"Adresse IP statique",
"static_ip_desc":"AdGuard Home est un serveur, il a donc besoin d’une adresse IP statique pour fonctionner correctement. Autrement, à un moment donné, votre routeur pourrait attribuer une adresse IP différente à cet appareil.",
"set_static_ip":"Définir une adresse IP statique",
"example_upstream_tcp_port":"DNS regolare (su TCP, con porta);",
"example_upstream_tcp_hostname":"DNS regolare (over TCP, nome host);",
"all_lists_up_to_date_toast":"Tutti gli elenchi sono aggiornati",
"updated_upstream_dns_toast":"I server upstream sono stati salvati correttamente",
@@ -327,7 +329,7 @@
"install_step":"Passo",
"install_devices_title":"Configura i tuoi dispositivi",
"install_devices_desc":"Affinché AdGuard Home inizi a funzionare, è necessario configurare i dispositivi per utilizzarlo.",
"install_submit_title":"Congratulazioni!",
"install_submit_title":"Felicitazioni!",
"install_submit_desc":"La procedura di configurazione è completa e ora sei pronto per iniziare ad utilizzare AdGuard Home.",
"install_devices_router":"Router",
"install_devices_router_desc":"Questa configurazione copre automaticamente tutti i dispositivi collegati al router di casa, non è necessario configurarli manualmente.",
@@ -341,7 +343,7 @@
"install_devices_windows_list_3":"Sul lato sinistro dello schermo, clicca su \"Cambia impostazioni adattatore\".",
"install_devices_windows_list_4":"Fai clic destro sulla tua connessione attiva e seleziona Proprietà.",
"install_devices_windows_list_5":"Trova \"Protocollo Internet versione 4 (TCP/IPv4)\" (o, per IPv6, \"Protocollo Internet versione 6 (TCP/IPv6)\" nell'elenco, selezionalo e quindi clicca nuovamente su Proprietà.",
"install_devices_windows_list_6":"Scegli \"Utilizza i seguenti indirizzi server DNS\" ed inserisci i tuoi indirizzi server AdGuard Home.",
"install_devices_windows_list_6":"Scegli \"Utilizza i seguenti indirizzi server DNS\" e inserisci i tuoi indirizzi server AdGuard Home.",
"install_devices_macos_list_1":"Fai clic sull'icona Apple e dirigiti sulle Preferenze di Sistema.",
"install_devices_macos_list_2":"Clicca su Rete.",
"install_devices_macos_list_3":"Seleziona la prima connessione nel tuo elenco e clicca su Avanzate.",
"form_error_client_id_format":"ClientID는 숫자, 소문자 및 붙임표(-)만 포함해야 합니다",
"form_error_server_name":"유효하지 않은 서버 이름",
"form_error_subnet":"서브넷 \"{{cidr}}\"에 \"{{ip}}\" IP 주소가 없습니다",
"form_error_subnet":"서브넷 '{{cidr}}'에 '{{ip}}' IP 주소가 없습니다",
"form_error_positive":"0보다 커야 합니다",
"form_error_gateway_ip":"임대는 게이트웨이의 IP 주소를 가질 수 없습니다",
"out_of_range_error":"\"{{start}}\"-\"{{end}}\" 범위 밖이어야 합니다",
"out_of_range_error":"'{{start}}'-'{{end}}' 범위 밖이어야 합니다",
"lower_range_start_error":"범위 시작보다 작은 값이어야 합니다",
"greater_range_start_error":"범위 시작보다 큰 값이어야 합니다",
"greater_range_end_error":"범위 종료보다 큰 값이어야 합니다",
@@ -71,8 +71,8 @@
"dhcp_error":"AdGuard Home이 네트워크에 다른 활성 DHCP 서버가 있는지 확인할 수 없습니다",
"dhcp_static_ip_error":"DHCP 서버를 사용하려면 고정 IP 주소를 설정해야 합니다. AdGuard Home이 이 네트워크 인터페이스가 고정 IP 주소를 사용하는지 확인할 수 없습니다. 고정 IP 주소를 수동으로 설정하십시오.",
"dhcp_dynamic_ip_found":"시스템은 <0>{{interfaceName}}</0> 인터페이스에 동적 IP 주소를 사용합니다. DHCP 서버를 사용하려면 고정 IP 주소를 설정해야 합니다. 현재 IP 주소는 <0>{{ipAddress}}</0>입니다. 'DHCP 서버 활성화' 버튼을 누르면 AdGuard Home이 이 IP 주소를 고정 IP 주소로 자동 설정합니다.",
"dhcp_lease_added":"\"{{key}}\" 고정 임대 정상적으로 추가되었습니다",
"dhcp_lease_deleted":"\"{{key}}\" 고정 임대 정상적으로 삭제되었습니다",
"dhcp_lease_added":"'{{key}}' 고정 임대 정상적으로 추가되었습니다",
"dhcp_lease_deleted":"'{{key}}' 고정 임대 정상적으로 삭제되었습니다",
"dhcp_new_static_lease":"새 고정 임대",
"dhcp_static_leases_not_found":"DHCP 고정 임대를 찾을 수 없음",
"dhcp_add_static_lease":"고정 임대 추가",
@@ -82,7 +82,7 @@
"dhcp_reset":"정말로 DHCP 설정을 초기화할까요?",
"country":"지역",
"city":"도시",
"delete_confirm":"\"{{key}}\"을 삭제하시겠습니까?",
"delete_confirm":"'{{key}}'을(를) 삭제하시겠습니까?",
"form_enter_hostname":"호스트 이름을 입력해주세요",
"error_details":"오류 상세 정보",
"response_details":"응답 정보",
@@ -211,17 +211,19 @@
"example_comment_hash":"# 이것 또한 댓글입니다.",
"example_regex_meaning":"특정 정규 표현식에 맞는 도메인 접근을 차단합니다.",
"example_upstream_regular":"일반 DNS (UDP을 통한 접속);",
"example_upstream_regular_port":"일반 DNS (UDP 이용, 포트 포함);",
"example_upstream_sdns":"<1>DNSCrypt</1> 또는 <2>DNS-over-HTTPS</2> 리졸버를 위한 <0>DNS 스탬프</0>;",
"example_upstream_tcp":"일반 DNS (TCP를 통한 접속);",
"example_upstream_tcp_port":"일반 DNS (TCP 이용, 포트 포함);",
"example_upstream_tcp_hostname":"일반 DNS (TCP를 통한, 호스트명);",
"all_lists_up_to_date_toast":"모든 리스트가 이미 최신입니다",
"updated_upstream_dns_toast":"업스트림 서버가 성공적으로 저장되었습니다",
"dns_test_ok_toast":"특정 DNS 서버들은 정상적으로 동작 중입니다",
"dns_test_not_ok_toast":"서버 \"{{key}}\": 사용할 수 없습니다, 제대로 작성했는지 확인하세요.",
"dns_test_not_ok_toast":"서버 '{{key}}': 사용할 수 없습니다, 제대로 작성했는지 확인하세요",
"dns_test_warning_toast":"업스트림 '{{key}}'이(가) 테스트 요청에 응답하지 않으며 제대로 작동하지 않을 수 있습니다",
"unblock":"차단 해제",
"block":"차단",
@@ -423,18 +425,18 @@
"ip_address":"IP 주소",
"client_identifier_desc":"클라이언트는 IP 주소, CIDR, MAC 주소 또는 ClientID(DoT/DoH/DoQ에 사용 가능)로 식별할 수 있습니다. <0>여기에서</0> 클라이언트를 식별하는 방법에 대한 자세한 내용은 확인하실 수 있습니다.",
"form_enter_ip":"IP 입력",
"form_enter_subnet_ip":"서브넷 \"{{cidr}}\" 내의 IP 주소 입력",
"form_enter_subnet_ip":"서브넷 '{{cidr}}' 내의 IP 주소 입력",
"auto_clients_desc":"AdGuard Home을 계속 사용할 수 있는 영구 클라이언트 목록에 없는 디바이스입니다",
@@ -468,11 +470,11 @@
"setup_dns_privacy_other_5":"<0>이곳이나</0> <1>이곳을</1> 클릭하여 더 많은 구현에 대한 정보를 확인하세요.",
"setup_dns_privacy_ioc_mac":"iOS 및 macOS 설정",
"setup_dns_notice":"<1>DNS-over-HTTPS</1> 또는 <1>DNS-over-TLS를</1> 사용하려면 AdGuard Home 설정에서 <0>암호화를 구성해야 합니다.</0>",
"rewrite_added":"\"{{key}}\"에 대한 DNS 수정 정보를 성공적으로 추가 됩니다.",
"rewrite_deleted":"\"{{key}}\"에 대한 DNS 수정 정보를 성공적으로 삭제 됩니다.",
"rewrite_added":"'{{key}}'에 대한 DNS 수정 정보를 성공적으로 추가 됩니다",
"rewrite_deleted":"'{{key}}'에 대한 DNS 수정 정보를 성공적으로 삭제 됩니다",
"rewrite_add":"DNS 변환 정보를 추가합니다",
"rewrite_not_found":"DNS 변경 정보를 찾을 수 없습니다",
"rewrite_confirm_delete":"\"{{key}}\"에 대한 DNS 변경 정보를 삭제하시겠습니까?",
"rewrite_confirm_delete":"'{{key}}'에 대한 DNS 변경 정보를 삭제하시겠습니까?",
"rewrite_desc":"특정 도메인 이름에 대한 사용자 지정 DNS 응답을 쉽게 구성할 수 있습니다.",
"rewrite_applied":"리디렉션 규칙이 적용됩니다",
"rewrite_hosts_applied":"호스트 파일 규칙에 따라 재작성",
@@ -553,7 +555,7 @@
"disable_ipv6_desc":"IPv6 주소(타입 AAAA)의 모든 DNS 쿼리가 무시됩니다.",
"fastest_addr":"가장 빠른 IP 주소",
"fastest_addr_desc":"모든 DNS 서버에 쿼리를 수행한 다음 반응이 가장 빠른 IP주소를 반송합니다. AdGuard Home이 모든 DNS 서버의 응답을 기다려야 하기 때문에 DNS 쿼리 속도가 느려지지만 전반적인 연결이 향상됩니다.",
"autofix_warning_text":"\"Fix\"를 클릭한다면 AdGuard Home은 시스템이 AdGuard Home의 DNS 서버를 사용하도록 설정합니다.",
"autofix_warning_text":"'수정'을 클릭하면 AdGuard Home이 AdGuard Home DNS 서버를 사용하도록 시스템을 설정합니다.",
"autofix_warning_list":"다음 작업을 진행합니다: <0>DNSStubListener 시스템 비활성화</0> <0>DNS 서버 주소를 127.0.0.1로 설정</0> <0>/etc/resolv.conf의 심볼릭 링크 타겟을 /run/systemd/resolve/resolv.conf로 변경</0> <0>DNSStubListener 중지 (systemd-resolved 서비스 새로고침)</0>",
"autofix_warning_result":"결과적으로 시스템의 모든 DNS 요청은 기본적으로 AdGuard Home에 의해 처리됩니다.",
"example_upstream_sdns":"<0>DNS Stamps</0> para o <1>DNSCrypt</1> ou usar os resolvedores <2>DNS-sobre-HTTPS</2>;",
"example_upstream_tcp":"DNS regular (através do TCP);",
"example_upstream_tcp_port":"dNS normal (através do TCP, com porta);",
"example_upstream_tcp_hostname":"DNS normal (através do TCP, nome do servidor);",
"all_lists_up_to_date_toast":"Todas as listas já estão atualizadas",
"updated_upstream_dns_toast":"Servidores DNS primário guardados com sucesso",
@@ -254,7 +256,7 @@
"query_log_filtered":"Filtrado por {{filter}}",
"query_log_confirm_clear":"Tem a certeza de que deseja limpar todo o registo de consulta?",
"query_log_cleared":"O registo de consulta foi limpo com sucesso",
"query_log_updated":"O registro da consulta foi atualizado com sucesso",
"query_log_updated":"O registo da consulta foi atualizado com sucesso",
"query_log_clear":"Limpar registos de consulta",
"query_log_retention":"Retenção de registos de consulta",
"query_log_enable":"Ativar registo",
@@ -263,7 +265,7 @@
"query_log_strict_search":"Usar aspas duplas para uma pesquisa rigorosa",
"query_log_retention_confirm":"Tem a certeza de que deseja alterar a retenção do registo de consulta? Se diminuir o valor do intervalo, alguns dados serão perdidos",
"anonymize_client_ip":"Tornar anónimo o IP do cliente",
"anonymize_client_ip_desc":"Não gurda o endereço de IP completo do cliente em registros ou estatísticas",
"anonymize_client_ip_desc":"Não gurda o endereço de IP completo do cliente em registo ou estatísticas",
"dns_config":"Definição do servidor DNS",
"dns_cache_config":"Definição de cache DNS",
"dns_cache_config_desc":"Aqui você pode configurar o cache do DNS",
@@ -289,7 +291,7 @@
"form_enter_rate_limit":"Insira o limite de taxa",
"rate_limit":"Limite de taxa",
"edns_enable":"Ativar a sub-rede do cliente EDNS",
"edns_cs_desc":"Adicione a opção de sub-rede de cliente EDNS (ECS) às solicitações de servidor DNS primário e registre os valores enviados pelos clientes no registro de consulta.",
"edns_cs_desc":"Adicione a opção de sub-rede de cliente EDNS (ECS) às solicitações de servidor DNS primário e registre os valores enviados pelos clientes no registo de consulta.",
"rate_limit_desc":"O número de solicitações por segundo permitido por cliente. Configurando para 0 significa sem limite.",
"blocking_ipv4_desc":"Endereço IP a ser devolvido para uma solicitação A bloqueada",
"blocking_ipv6_desc":"Endereço IP a ser devolvido para uma solicitação AAAA bloqueada",
@@ -410,7 +412,7 @@
"manual_update":"Por favor, <a>siga estes passos</a> para atualizar manualmente.",
"processing_update":"Por favor espere, o AdGuard Home está a atualizar-se",
"clients_title":"Clientes persistentes",
"clients_desc":"Configure registros de cliente persistentes para dispositivos conectados ao AdGuard Home",
"clients_desc":"Configure registos de cliente persistentes para dispositivos conectados ao AdGuard Home",
"settings_global":"Global",
"settings_custom":"Personalizar",
"table_client":"Cliente",
@@ -445,7 +447,7 @@
"access_disallowed_title":"Clientes não permitidos",
"access_disallowed_desc":"Uma lista de CIDRs, endereços IP ou <a>IDs de cliente</a>. Se essa lista tiver entradas, o AdGuard Home descartará as solicitações desses clientes. Este campo é ignorado se houver entradas em clientes permitidos.",
"access_blocked_title":"Domínios bloqueados",
"access_blocked_desc":"Não deve ser confundido com filtros. O AdGuard Home elimina as consultas DNS que correspondem a esses domínios, e essas consultas nem aparecem no registro de consultas. Você pode especificar nomes de domínio exatos, caracteres curinga ou regras de filtro de URL, por exemplo \"exemplo.org\", \"*.exemplo.org\", ou \"||exemplo.org^\" correspondentemente.",
"access_blocked_desc":"Não deve ser confundido com filtros. O AdGuard Home elimina as consultas DNS que correspondem a esses domínios, e essas consultas nem aparecem no registo de consultas. Você pode especificar nomes de domínio exatos, caracteres curinga ou regras de filtro de URL, por exemplo \"exemplo.org\", \"*.exemplo.org\", ou \"||exemplo.org^\" correspondentemente.",
"access_settings_saved":"Definições de acesso foram guardadas com sucesso",
"updates_checked":"Uma nova versão do AdGuard Home está disponível\n",
"updates_version_equal":"O AdGuard Home está atualizado",
@@ -546,9 +548,9 @@
"example_rewrite_domain":"reescrever resposta apenas para este domínio.",
"example_rewrite_wildcard":"reescrever resposta para todos <0>example.org</0> sub-domínios.",
"rewrite_ip_address":"Endereço IP: use esse IP em uma resposta A ou AAAA",
"rewrite_domain_name":"Nome de domínio: adicione um registro CNAME",
"rewrite_A":"<0>A</0>: valor especial, mantenha <0>A</0> nos registros do upstream",
"rewrite_AAAA":"<0>AAAA</0>: valor especial, mantenha <0>AAAA</0> nos registros do servidor DNS primário",
"rewrite_domain_name":"Nome de domínio: adicione um registo CNAME",
"rewrite_A":"<0>A</0>: valor especial, mantenha <0>A</0> nos registos do upstream",
"rewrite_AAAA":"<0>AAAA</0>: valor especial, mantenha <0>AAAA</0> nos registos do servidor DNS primário",
"disable_ipv6":"Desativar resolução de endereços IPv6",
"disable_ipv6_desc":"Descarta todas as consultas DNS para endereços IPv6 (tipo AAAA).",
"example_upstream_sdns":"<0>DNS Stamps</0> для <1>DNSCrypt</1> или <2>DNS-over-HTTPS</2> серверов;",
"example_upstream_tcp":"обычный DNS (поверх TCP);",
"example_upstream_tcp_port":"обычный DNS (поверх TCP, с портом);",
"example_upstream_tcp_hostname":"обычный DNS (поверх TCP, с именем хоста);",
"all_lists_up_to_date_toast":"Все списки уже обновлены",
"updated_upstream_dns_toast":"DNS-серверы успешно обновлены",
@@ -626,7 +628,7 @@
"original_response":"Первоначальный ответ",
"click_to_view_queries":"Нажмите, чтобы просмотреть запросы",
"port_53_faq_link":"Порт 53 часто занят службами «DNSStubListener» или «systemd-resolved». Ознакомьтесь с <0>инструкцией</0> о том, как это разрешить.",
"adg_will_drop_dns_queries":"AdGuard Home AdGuard Home сбросит все DNS-запросы от этого клиента.",
"adg_will_drop_dns_queries":"AdGuard Home сбросит все DNS-запросы от этого клиента.",
"filter_allowlist":"ВНИМАНИЕ: Это действие также исключит правило «{{disallowed_rule}}» из списка разрешённых клиентов.",
"last_rule_in_allowlist":"Нельзя заблокировать этого клиента, так как исключение правила «{{disallowed_rule}}» ОТКЛЮЧИТ режим белого списка.",
"use_saved_key":"Использовать сохранённый ранее ключ",
"updated_upstream_dns_toast":"Üst sunucular başarıyla kaydedildi",
@@ -384,8 +386,8 @@
"encryption_enable_desc":"Şifrelemeyi etkinleştirirseniz, AdGuard Home yönetici arayüzü HTTPS üzerinden çalışır ve DNS sunucusu, DNS-over-HTTPS ve DNS-over-TLS üzerinden gelen istekleri dinler.",
"example_upstream_sdns":"<0>DNS Stamps</0> для <1>DNSCrypt-</1> або <2>DNS-over-HTTPS-</2>вирішувачів;",
"example_upstream_tcp":"звичайний DNS (через TCP);",
"example_upstream_tcp_port":"звичайний DNS (поверх TCP, з портом);",
"example_upstream_tcp_hostname":"звичайний DNS (поверх TCP, з назвою вузла);",
"all_lists_up_to_date_toast":"Всі списки вже оновлені",
"updated_upstream_dns_toast":"DNS-сервери успішно збережено",
@@ -445,7 +447,7 @@
"access_disallowed_title":"Заборонені клієнти",
"access_disallowed_desc":"Перелік CIDR, IP-адрес та <a>ClientIDs</a>. Якщо налаштовано, AdGuard Home буде скасовувати запити від цих клієнтів. Проте якщо налаштовано список Дозволених клієнтів, то це поле проігнорується.",
"access_blocked_title":"Заборонені домени",
"access_blocked_desc":"Не плутайте з фільтрами. AdGuard Home буде ігнорувати DNS-запити з цими доменами, такі запити навіть не будуть записані до журналу. Ви можете вказати точні доменні імена, замінні знаки та правила фільтрування URL-адрес, наприклад, 'example.org', '*.example.org'або'||example.org^' відповідно.",
"access_blocked_desc":"Не плутайте з фільтрами. AdGuard Home буде ігнорувати DNS-запити з цими доменами, такі запити навіть не будуть записані до журналу. Ви можете вказати точні доменні імена, замінні знаки та правила фільтрування URL-адрес, наприклад, «example.org», «*.example.org»або«||example.org^» відповідно.",
"access_settings_saved":"Налаштування доступу успішно збережено",
"updates_checked":"Доступна нова версія AdGuard Home",
"updates_version_equal":"AdGuard Home останньої версії",
"dhcp_error":"AdGuard Home 无法确定在当前网络中是否存在其它 DHCP 服务器",
"dhcp_static_ip_error":"要使用 DHCP 服务器，则必须设置静态 IP 地址。AdGuard Home 无法确定此网络接口是否已被配置为使用静态 IP 地址。请手动为此网络接口设置静态 IP 地址。",
"dhcp_dynamic_ip_found":"您的系统对网络接口 <0>{{interfaceName}}</0> 使用了动态 IP 地址配置。要使用 DHCP 服务器，则必须对此网络接口使用静态 IP 地址配置。此网络接口当前的 IP 地址为 <0>{{ipAddress}}</0>。如您点击“启用 DHCP 服务器” 按钮，AdGuard Home 将自动修改此网络接口以使用静态 IP 地址。",
"dhcp_dynamic_ip_found":"您的系统对网络接口 <0>{{interfaceName}}</0> 使用了动态 IP 地址配置。要使用 DHCP 服务器，则必须对此网络接口使用静态 IP 地址配置。此网络接口当前的 IP 地址为 <0>{{ipAddress}}</0>。如您点击「启用 DHCP 服务器」按钮，AdGuard Home 将自动修改此网络接口以使用静态 IP 地址。",
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
