Merge in DNS/adguard-home from 7555-fix-ra-packets to master
* commit '0ed2cd04b22a7b447380ee863bc908603720877d':
dhcpd: imp docs
all: fix changelog
dhcpd: imp docs
all: imp code & test, log changes
Change comment message to match implementation
dhcpd: Fix slaac configuration which was not working due to invalid icmp packet
Merge in DNS/adguard-home from ADG-9715 to master
Squashed commit of the following:
commit d972608ad5429810e0f5ad430f11e037cd05ee40
Author: Ildar Kamalov <ik@adguard.com>
Date: Thu Mar 6 12:46:29 2025 +0300
ADG-9715 formatting of elapsed times less than one millisecond
Merge in DNS/adguard-home from AGDNS-2686-client-manager-clock to master
Squashed commit of the following:
commit 1d3cafa7f1036a72b766feaee1db00398e51c364
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Tue Mar 4 20:52:39 2025 +0300
all: client manager clock
Updates #7583.
* commit 'e9d4e76828261622dfb424c760246a21b73040e8':
all: upd chlog
refactor: Format value requests_count on client table
refactor: Format value clientstats
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 3937386d8afdf5e04cddec5e0bd5ac47dad7034d
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Feb 20 18:14:30 2025 +0300
all: upd chlog
Merge in DNS/adguard-home from AGDNS-2690-global-context to master
Squashed commit of the following:
commit 58d5999e5d9112b3391f988ed76e87eff2919d6b
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Wed Feb 19 18:51:41 2025 +0300
home: imp naming
commit cfb371df59c816be1022d499cc41ffaf2b72d124
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Wed Feb 19 18:42:52 2025 +0300
home: global context
Merge in DNS/adguard-home from fix-chlog to master
Squashed commit of the following:
commit 3f209c99936f40ec67acd70e64f53368adac83dd
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Feb 18 19:45:25 2025 +0300
all: fix chlog
Merge in DNS/adguard-home from upd-i18n to master
Squashed commit of the following:
commit da6c09136c3e2495a6117f92752f18b190ce4f7b
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Feb 18 17:53:36 2025 +0300
client: upd i18n
Merge in DNS/adguard-home from upd-deps to master
Squashed commit of the following:
commit 40d509625c0099c34e6ff14f69b0ab1535b9c51f
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Feb 7 13:19:24 2025 +0300
all: upd go, deps
Merge in DNS/adguard-home from ADG-9565 to master
Squashed commit of the following:
commit ef92c2e891
Merge: a4364ff7e91270d0b6
Author: Ildar Kamalov <ik@adguard.com>
Date: Wed Jan 29 13:42:29 2025 +0300
Merge branch 'master' into ADG-9565
commit a4364ff7ed
Author: Ildar Kamalov <ik@adguard.com>
Date: Wed Jan 29 13:39:14 2025 +0300
ADG-9565 format large numbers in the upstream table and query log
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit ea263dbf3e2d409ae9a982b89ee7976de96138b1
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Jan 28 20:53:44 2025 +0300
all: upd chlog
Merge in DNS/adguard-home from fix-test to master
Squashed commit of the following:
commit cddaed40273e81677eec33e2ededfd4556c5b99f
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Mon Jan 20 18:33:43 2025 +0300
filtering: fix test
Merge in DNS/adguard-home from upd-go to master
Squashed commit of the following:
commit 58aad666b56d7100c7b5291fb8a100fe635e6d62
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Fri Jan 17 19:02:06 2025 +0300
all: upd go
Merge in DNS/adguard-home from AGDNS-2622-fix-race to master
Squashed commit of the following:
commit 28170e67655048d7356d6cfce07e04017a933163
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Mon Dec 23 17:24:28 2024 +0300
all: upd proxy
commit 3bd9458220e04041c5135fa97d55e6e6e6c29071
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Fri Dec 20 21:19:20 2024 +0300
all: upd proxy
Merge in DNS/adguard-home from more-md-lint to master
Squashed commit of the following:
commit 39e7ea3b441ebf48c5b0d5c2b5b85620515bbea3
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Dec 19 17:03:36 2024 +0300
all: imp docs more
commit 7aa08036b239d7eb19f674a6c4bfaf1325ff4bff
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Dec 19 16:08:13 2024 +0300
all: add more docs to lint
Merge in DNS/adguard-home from upd-go-deps to master
Squashed commit of the following:
commit 2c0b63da2ec8bbf19bc7dbb03c0166f6f9a5d822
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Dec 12 14:42:31 2024 +0300
all: upd go deps, tools
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 305ae5823fa2f61b5f58759a29330a65599c19ba
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Dec 11 17:19:51 2024 +0300
all: upd and fmt chlog
When I clicked the link aliased as wiki-start, the article had a banner at the top redirecting readers to a newer version on the wiki. This commit replaces the link to the outdated version with the link it redirects to, to save future visitors a click.
Squashed commit of the following:
commit 257bd542f78d6e06a6b4783a050b573240a2b5ca
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Mon Sep 2 17:33:12 2024 +0300
scripts: slog
Merge in DNS/adguard-home from ADG-8776 to master
Squashed commit of the following:
commit d9f3acf7298c1cd39c980b9d6743624e18cdd8bf
Author: Igor Lobanov <bniwredyc@gmail.com>
Date: Wed Jul 3 17:55:18 2024 +0200
clear query log filter fix
Squashed commit of the following:
commit 1f7be03896a6eaf0a292e4c7e9a7ef7c712ed734
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Mar 21 13:35:37 2024 +0300
all: use standard md style in some docs
Squashed commit of the following:
commit 0a54ca2746dac7a21d05265f26c161df763af7d8
Merge: 1d30c0995 5565b9e1c
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Wed Mar 6 16:19:36 2024 +0300
Merge branch 'master' into AG-30904-fix-ip-in-logs
commit 1d30c099577bda192609049bab4510cf6f69a972
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Tue Mar 5 17:14:02 2024 +0300
all: missing ip in logs
Squashed commit of the following:
commit 8fd3ef24725d48cff41cec8762f397f3b9a524f9
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Jan 19 16:08:37 2024 +0300
all: rm outdated link from readme
Squashed commit of the following:
commit 4767b7bf61a277f20d8326783cc44de1b736de3d
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Wed Dec 27 14:30:10 2023 +0300
all: fix non-anonymized ips in stats
v0.5.0 only supports Go 1.21+[1], and no dependencies require v0.5.0.
This fixes building with Go 1.21.
[1]: 18f45b55db/CHANGELOG.md (v050)Closes#6446.
Merge in DNS/adguard-home from custom-ups-cache-conf-fix to master
Squashed commit of the following:
commit 01a728e74b2e2e709c496794ca7ceb90703a02fc
Author: Dimitry Kolyshev <dkolyshev@adguard.com>
Date: Mon Nov 20 11:48:01 2023 +0200
home: fix client dns cache
Merge in DNS/adguard-home from fix-windows-migr-test to master
Squashed commit of the following:
commit be0550f0d6b99f2f18a2bdc9b8e330600c224ea4
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Thu Sep 7 17:42:12 2023 +0300
confmigrate: fix windows tests
Updates #6160
Squashed commit of the following:
commit f0fecc1f4a1c14ddbf6ea68f5fcc3b3e2fd8784b
Author: Ildar Kamalov <ik@adguard.com>
Date: Tue Sep 5 13:00:19 2023 +0300
client: fix link color in dark mode for query log
Updates #6158.
Squashed commit of the following:
commit 763292f9cf5796574b4b79fc32874fb9acefb500
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Thu Aug 31 12:54:08 2023 +0300
dnsforward: fix dns filter
Squashed commit of the following:
commit f48a92c6240cdd88905f396e08a4bc5fac01b97f
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Aug 30 13:29:07 2023 +0300
.github: set node version
Merge in DNS/adguard-home from fix-hosts-windows to master
Squashed commit of the following:
commit 8e080ade8980f73006eb33de930749b91d203915
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Aug 22 17:49:23 2023 +0300
aghnet: fix src path
Squashed commit of the following:
commit 8ac1f14e422ad9a7cc0186e5ea18988613639240
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Jul 18 17:04:36 2023 +0300
.github: do not use md
Merge in DNS/adguard-home from cmdline-flag-docs to master
Updates #4235.
Squashed commit of the following:
commit 1d68255b3d3003207eed535f9491fedb1d839e8b
Author: Dimitry Kolyshev <dkolyshev@adguard.com>
Date: Fri Jun 23 16:04:15 2023 +0400
all: docs
Merge in DNS/adguard-home from AG-23334-fix-snap-plan to master
Squashed commit of the following:
commit 5d632d1d63c56911e005d0e772e82a509302e948
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Jun 21 17:42:36 2023 +0300
bamboo-specs: fix snap build; fmt
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit feef14c20617f664832e4b99f9854e1fc7faba9f
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Jun 13 17:47:44 2023 +0300
all: upd chlog
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit dafdadea12f9c2324649ed06973d7bd818d4b815
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Jun 8 20:04:38 2023 +0300
all: upd chlog
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 73e90eb68edeb82d99637b51bd99ff12cf590e25
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Jun 7 20:45:45 2023 +0300
all: upd chlog
Merge in DNS/adguard-home from upd-go to master
Squashed commit of the following:
commit 688019427edac3346bbf49bb3d58a5df3c4f30d6
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Jun 7 18:19:17 2023 +0300
all: upd go, deps, tools
Merge in DNS/adguard-home from upd-proxy to master
Squashed commit of the following:
commit b258697cdac6a6ac83c94814dbe8551c5685fa3b
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Jun 6 13:22:17 2023 +0300
all: upd proxy
Merge in DNS/adguard-home from upd-proxy to master
Squashed commit of the following:
commit abb1f27954bf8c20461d86b382f59479a75a9958
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Fri Jun 2 16:57:53 2023 +0300
all: upd dnsproxy
Merge in DNS/adguard-home from fix-5858 to master
Closes#5858
Squashed commit of the following:
commit 3a5866bdff9bd087c6165b0356fa05bcd5e9d88d
Author: Andrey Meshkov <am@adguard.com>
Date: Wed May 31 14:28:37 2023 +0300
doc: add AdGuardian-Term to readme
Closes#5858
Merge in DNS/adguard-home from upd-golang-ubuntu-2 to master
Squashed commit of the following:
commit 9fdd86a0d352cd3a046bca19d6acf0f549adfc53
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Mon May 22 17:36:06 2023 +0300
all: upd golang-ubuntu again
Merge in DNS/adguard-home from upd-golang-ubuntu to master
Squashed commit of the following:
commit d4c79a1ddbf732f2d8500830b9f53f547ce33f23
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Mon May 22 16:29:48 2023 +0300
all: upd golang-ubuntu
Merge in DNS/adguard-home from fix-snap to master
Squashed commit of the following:
commit 4a12b2709229150e1b896b71b2b0a99249f94fde
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Sat May 20 11:51:25 2023 +0300
bamboo-specs: upd snap script
Merge in DNS/adguard-home from AG-21324-update-dhcp to master
Squashed commit of the following:
commit 20499d71ffe62f34576f9328db5dc6fb5c929c28
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Wed May 17 14:23:09 2023 +0300
dhcpd: imp tests
commit fa6add1410a98d1b9dfd833bcb20ef9fb7ff57ca
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Tue May 16 09:52:38 2023 +0100
all: update dhcp
Merge in DNS/adguard-home from AG-21462-safebrowsing-parental-http-tests to master
Squashed commit of the following:
commit 22a83ebad08a27939a443530137a7c195f512ee4
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Wed May 3 17:39:46 2023 +0300
filtering: fix test
commit c3ca8b4987245cdd552f6f09759804e716bcae80
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Wed May 3 16:43:35 2023 +0300
filtering: imp tests even more
commit 7643bfae350373b5b6dfb61b64e57da66c6ab952
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Wed May 3 16:17:42 2023 +0300
filtering: imp tests more
commit 399c05ee4d479a727b61378b7a07158a568d0181
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Wed May 3 14:45:41 2023 +0300
filtering: imp tests
commit f361df39e784ec9c5191666736a6c64b332928e8
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Tue May 2 12:49:26 2023 +0300
filtering: add tests
Merge in DNS/adguard-home from 5714-fix-docker-health to master
Updates #5714.
Squashed commit of the following:
commit 61251bffd7a21f1ceb867cc89de0a171645ca4c2
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Thu Apr 13 16:45:41 2023 +0300
docker: use localhost for unspecified
Merge in DNS/adguard-home from AG-21291-web-races to master
Squashed commit of the following:
commit 1134013f928aa5e186db3b6d0450e425cb053e9c
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Apr 11 16:52:52 2023 +0300
home: fix web api races
Merge in DNS/adguard-home from fix-chlog to master
Squashed commit of the following:
commit 47f6b33780d7c1d99a6fc36ddf435db068938174
Author: Stanislav Chzhen <s.chzhen@adguard.com>
Date: Tue Apr 11 16:38:04 2023 +0300
all: fix chlog
Merge in DNS/adguard-home from upd-golibs to master
Squashed commit of the following:
commit cde42a72c2140245f345681cbb936ed3bc4645a1
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Apr 7 13:57:02 2023 +0300
all: upd golibs, use hdrs
Merge in DNS/adguard-home from fix-openapi-chlog to master
Squashed commit of the following:
commit cc8a7526a230edffd0eb86a5a69c565c221996f1
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Mar 24 15:19:57 2023 +0300
openapi: fix chlog
Merge in DNS/adguard-home from 5584-invalid-host-panic to master
Updates #5584.
Squashed commit of the following:
commit a09b59e279089c86b785b3c839dff10b3f327779
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Mar 14 17:05:12 2023 +0300
all: upd golibs, add test
Merge in DNS/adguard-home from fix-chlog to master
Squashed commit of the following:
commit a0d765ab0b6e6f621bc610d29a95c3331f48d83b
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Mon Mar 13 18:06:43 2023 +0300
all: fix chlog
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 7834babfb513c47878087bd3710e3b6e61cd2a76
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Mar 9 16:42:49 2023 +0300
all: upd chlog
Merge in DNS/adguard-home from fix-updater to master
Squashed commit of the following:
commit 8103b0988b59a916fd84a5ca041b9a9fea606ebc
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Mar 1 14:28:54 2023 +0300
updater: fix max size
Merge in DNS/adguard-home from imp-filtering-cyclo to master
Squashed commit of the following:
commit ca97d7acc9893c489800bbbc41e71ccf686c8f07
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Feb 28 15:16:34 2023 +0300
filtering: imp cyclo
Merge in DNS/adguard-home from chlog-and-proj-skel to master
Squashed commit of the following:
commit 8e7c3e2eb50c559bdcd5862e72c16511dd8272da
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Feb 21 16:52:10 2023 +0300
all: upd proj skel
Merge in DNS/adguard-home from upd-sorting to master
Squashed commit of the following:
commit 7bd21de65c50168d5ad83ff46e63f4cbca365d23
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Feb 21 10:57:17 2023 +0300
all: upd sorting, go-lint
Merge in DNS/adguard-home from docker-spec-no-make to master
Squashed commit of the following:
commit 897edba3bc23cdc105bc0f4017c862d84128fd71
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Feb 16 16:57:31 2023 +0300
bamboo-specs: do not require make where not needed
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 8938eb2b601f46ed52cff7da91d5f647999a1594
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Feb 15 20:50:44 2023 +0300
all: upd chlog
Merge in DNS/adguard-home from imp-specs to master
Squashed commit of the following:
commit 56eeda8fa3315b31304400da9c97d8cbbe042343
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Feb 8 15:07:13 2023 +0300
all: imp specs
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit ce9ebccf73e2418503cd905eebd62b95fdb7a71e
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Feb 1 16:39:20 2023 +0300
all: upd chlog; imp go-lint
Merge in DNS/adguard-home from use-mathutil to master
Squashed commit of the following:
commit cfe2c02a7bb727e81fcd91674aa777df37413a8e
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Jan 24 18:12:32 2023 +0300
all: use mathutil
Merge in DNS/adguard-home from remove-client2 to master
Squashed commit of the following:
commit 0a0923494b0d1003e4f02f3a5f93d5248f0f2ded
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Jan 20 17:14:29 2023 +0300
all: rm old experimental beta (dir client2/)
This project was unfortunately abandoned. v0.108.0 will have a
different front-end and new APIs.
Merge in DNS/adguard-home from upd-all to master
Squashed commit of the following:
commit 107fd015c773494a1eb5970708807238644dbb40
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Jan 19 14:30:34 2023 +0300
all: upd i18n, blocked svcs
Merge in DNS/adguard-home from reduce-build-parallelism to master
Squashed commit of the following:
commit 3c26331185f8402441334078eb73ad2615edd5e5
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Jan 11 14:40:46 2023 +0300
all: reduce build parallelism
Merge in DNS/adguard-home from 5270-updater-package-url to master
Squashed commit of the following:
commit 50ee8edb6270e750ed82b14c174f88922aff86bb
Author: Dimitry Kolyshev <dkolyshev@adguard.com>
Date: Wed Dec 28 12:21:24 2022 +0700
updater: package url
Merge in DNS/adguard-home from 5258-changelog to master
Updates #5258.
Squashed commit of the following:
commit a46f9435b91cfdd9f1da6132526707fe81004e51
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Dec 20 18:36:41 2022 +0400
all: log changes
Merge in DNS/adguard-home from unignore-snap to master
Squashed commit of the following:
commit 2901080c92d5316bcbf536ebdfeaff88cea0edd4
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Dec 15 19:08:46 2022 +0300
all: unignore snap
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 6d99abd2144219393be3997b723288c36ee72faf
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Dec 15 18:14:07 2022 +0300
all: upd chlog
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 9117b734bfea2bcb5993c340c474f8c894902b70
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Dec 7 17:41:24 2022 +0300
all: upd chlog
Merge in DNS/adguard-home from use-download-url to master
Squashed commit of the following:
commit d665794ef0594b87044c7a1aadac6ac9dc31722a
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Nov 24 18:06:36 2022 +0300
all: use download url for vetted lists
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 659e3a5bd217190195d31205b471f3540403715f
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Nov 23 17:23:58 2022 +0300
all: upd chlog
Merge in DNS/adguard-home from upd-data to master
Squashed commit of the following:
commit 2f4c6747ea1d6dadc0e522dc639ae655e59678d9
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Nov 23 15:21:54 2022 +0300
all: upd i18n, services
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit efe2d95b870e413af4f91be5de7c7b97970e1dd5
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Nov 8 18:08:03 2022 +0300
all: upd chlog
Merge in DNS/adguard-home from upd-before-release to master
Squashed commit of the following:
commit 71f36273a55f63d389188fd7df2950a6207549a9
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Nov 8 14:35:18 2022 +0300
all: upd deps, tools, filters
Merge in DNS/adguard-home from imp-pprof to master
Squashed commit of the following:
commit cd6c2ec15342ef55957ab65e1599733c2ee57b7b
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Mon Nov 7 19:45:12 2022 +0300
home: imp pprof handling, field alignment
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit d148e3db4f432cfb447eeda2f56f1df2fb512a50
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Nov 2 18:33:21 2022 +0300
all: upd chlog
Merge in DNS/adguard-home from upd-i18n to master
Squashed commit of the following:
commit 1460df0f7c07f49f056068a6b01ab6e01566a087
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Nov 2 14:43:23 2022 +0300
client: upd i18n
Merge in DNS/adguard-home from upd-go to master
Squashed commit of the following:
commit 9548937ef70f195bbd9b6d19093bb88e9d5f0330
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Nov 2 14:09:46 2022 +0300
all: upd go, tools
Merge in DNS/adguard-home from rm-jsonutil to master
Squashed commit of the following:
commit dec746d321adbeb41bfd0c44e71d198809c4731e
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Oct 28 18:41:39 2022 +0300
querylog: rm jsonutil
Merge in DNS/adguard-home from upd-pkgs-tools to master
Squashed commit of the following:
commit 114c1ee94ff20339709e3ed66941d46692ab062c
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Oct 28 17:17:03 2022 +0300
all: upd go pkgs, tools
Merge in DNS/adguard-home from imp-tests to master
Squashed commit of the following:
commit ea5b4e7a93359ae4800f75e77d02944a4f5d2df8
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Thu Oct 27 15:12:45 2022 +0300
all: imp tests, use testutil
Merge in DNS/adguard-home from http3-tls-fix to master
Squashed commit of the following:
commit 4b4ac9f91d6a36654674c5e7037d2bf35a6b211a
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Oct 26 15:35:07 2022 +0300
dnsforward: add crutch for quic-go bug
Merge in DNS/adguard-home from upd-proxy to master
Squashed commit of the following:
commit ba7c3595d7a0747b18f16e418473cb633b09200c
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date: Tue Oct 25 18:15:15 2022 +0300
all: upd dnsproxy
Merge in DNS/adguard-home from upd-twosky to master
Squashed commit of the following:
commit aba02252dc754aa25a7ea117c0310f990d45eeed
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Oct 21 19:13:24 2022 +0300
all: upd twosky
Merge in DNS/adguard-home from upd-companiesdb to master
Squashed commit of the following:
commit c38ccd89a46193b24393c00b4a83ed439f6d7469
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Wed Oct 19 12:00:58 2022 +0300
client: upd trackers
Merge in DNS/adguard-home from cve-id to master
Squashed commit of the following:
commit 5a5418db1992e49402a44a3c1cf9cffc132c8074
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Oct 18 17:28:49 2022 +0300
all: upd cve id
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 8885f3f2291947d76203873dce0ccfd5c270fa7f
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Fri Oct 7 16:56:38 2022 +0300
all: upd chlog
Merge in DNS/adguard-home from websvc-config-manager to master
Squashed commit of the following:
commit 2143b47c6528030dfe059172888fddf9061e42da
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Tue Oct 4 14:50:47 2022 +0300
next: add config manager
Merge in DNS/adguard-home from upd-chlog to master
Squashed commit of the following:
commit 368025b27cb74fc5b6acbfd9382adeebc4ca6cbd
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date: Mon Oct 3 19:23:32 2022 +0300
all: upd chlog
Merge in DNS/adguard-home from 4983-fix-custom-svcs to master
Updates #4945.
Updates #4982.
* commit '739e0098ec127045197ea697bae78acb2bd2c729':
all: imp code, wording
home: fix empty svcs
bugfix: Fixed bug which was causing clients to continue following global service blocks even when user opted to not do that
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
#### <a href="#building-node" id="building-node" name="building-node">Building with Node.js 17 and later</a>
In order to build AdGuard Home with Node.js 17 and later, specify `--openssl-legacy-provider` option.
```sh
exportNODE_OPTIONS=--openssl-legacy-provider
```
> [!WARNING]
> The non-standard `-j` flag is currently not supported, so building with `make -j 4` or setting your `MAKEFLAGS` to include, for example, `-j 4` is likely to break the build. If you do have your `MAKEFLAGS` set to that, and you don't want to change it, you can override it by running `make -j 1`.
@@ -299,6 +290,22 @@ When you need to debug the frontend without recompiling the production version e
You are welcome to fork this repository, make your changes and [submit a pull request][pr]. Please make sure you follow our [code guidelines][guide] though.
"example_multiple_upstreams_reserved":"منابع متعددة <0>لمجالات محددة</0>;",
"example_upstream_comment":"تعليق.",
"upstream_parallel":"استخدم الاستعلامات المتوازية لتسريع عملية الحل عن طريق الاستعلام عن جميع الخوادم المنبع في وقت واحد.",
"parallel_requests":"الطلبات الموازية",
"load_balancing":"موازنة الأحمال",
"load_balancing_desc":"الاستعلام عن خادم واحد في كل مرة سيستخدم AdGuard الرئيسية الخوارزمية العشوائية الموزونة لاختيار الخادم بحيث يتم استخدام أسرع خادم في كثير من الأحيان",
"bootstrap_dns":"خوادم Bootstrap DNS",
"bootstrap_dns_desc":"عناوين IP لخوادم DNS المستخدمة لحل عناوين IP الخاصة بمحللات DoH/DoT التي تحددها كمصدرين رئيسيين. التعليقات غير مسموح بها.",
"fallback_dns_title":"خوادم DNS الاحتياطية",
"fallback_dns_desc":"قائمة الخوادم الاحتياطية المستخدمة في حالة عدم الاستجابة من خوادم DNS الرئيسية. تمتلك تلك الخوادم والخوادم الرئيسية نفس الأوامر.",
"fallback_dns_placeholder":"أدخل خادم DNS احتياطي واحد لكل سطر",
"local_ptr_title":"خوادم DNS العكسية الخاصة",
"local_ptr_desc":"خوادم DNS التي يستخدمها AdGuard Home لاستعلامات PTR المحلية. تُستخدم هذه الخوادم لحل أسماء المضيفين للعملاء بعناوين IP خاصة ، على سبيل المثال \"192.168.12.34\" ، باستخدام DNS العكسي. في حالة عدم التعيين ، يستخدم AdGuard Home عناوين محللات DNS الافتراضية لنظام التشغيل الخاص بك باستثناء عناوين AdGuard Home نفسها.",
"local_ptr_default_resolver":"بشكل افتراضي ، يستخدم AdGuard Home محللات DNS العكسية التالية: {{ip}}.",
"local_ptr_no_default_resolver":"لم يتمكن AdGuard Home من تحديد محللات DNS العكسية المناسبة لهذا النظام.",
"local_ptr_placeholder":"أدخل عنوان خادم واحد لكل سطر",
"local_ptr_placeholder":"أدخل عنوان IP واحد لكل سطر",
"resolve_clients_title":"تفعيل التحليل العكسي لعناوين IP للعملاء",
"resolve_clients_desc":"حل عكسيًا لعناوين IP للعملاء في أسماء مضيفيهم عن طريق إرسال استعلامات PTR إلى أدوات الحل المقابلة (خوادم DNS الخاصة للعملاء المحليين ، والخوادم الأولية للعملاء الذين لديهم عناوين IP عامة).",
"use_private_ptr_resolvers_title":"استخدم محللات DNS العكسية الخاصة",
@@ -34,7 +38,7 @@
"dhcp_leases_not_found":"لم يتم العثور على عقود إيجار DHCP",
"form_error_ip4_gateway_format":"عنوان IPv4 غير صالح للبوابة",
@@ -63,14 +67,16 @@
"dhcp_ip_addresses":"عناوين الـIP",
"ip":"IP",
"dhcp_table_hostname":"اسم المضيف",
"dhcp_table_expires":"يتنهي في",
"dhcp_table_expires":"تنتهي",
"dhcp_warning":"إذا كنت تريد تمكين خادم DHCP على أي حال ، فتأكد من عدم وجود خادم DHCP نشط آخر في شبكتك. خلاف ذلك ، يمكن أن يعطل خدمة الإنترنت للأجهزة المتصلة!",
"dhcp_error":"لم نتمكن من تحديد ما إذا كان هناك خادم DHCP آخر في الشبكة.",
"dhcp_static_ip_error":"من أجل استخدام خادم DHCP ، يجب تعيين عنوان IP ثابت. فشلنا في تحديد ما إذا تم تكوين واجهة الشبكة هذه باستخدام عنوان IP ثابت. يرجى تعيين عنوان IP ثابت يدويًا.",
"dhcp_dynamic_ip_found":"يستخدم نظامك عنوان IP الديناميكي للواجهة <0>{{interfaceName}}</0>. من أجل استعمال خادم DHCP ، يجب تعيين عنوان IP ثابت. عنوان IP الحالي الخاص بك هو <0>{{ipAddress}}</0>. إذا ضغطت على زر تفعيل DHCP سنقوم تلقائيًا بتعيين عنوان الIP هذا على أنه ثابت.",
"dhcp_lease_added":"تمت أضافة مدة الايجار \"{{key}}\" بنجاح",
"dhcp_lease_deleted":"تمت ازالة مدة الايجار \"{{key}}\" بنجاح",
"query_log_retention_confirm":"هل أنت متأكد من أنك تريد تغيير الاحتفاظ بسجل الاستعلام؟ إذا قمت بتقليل قيمة الفاصل الزمني سيتم فقدان بعض البيانات",
"query_log_retention_confirm":"هل أنت متيقِّن من أنك تريد تغيير دوران سجل الاستعلام؟ إذا قمت بتقليل قيمة الفاصل الزمني، ستفقد بعض البيانات",
"anonymize_client_ip":"إخفاء عنوان IP العميل",
"anonymize_client_ip_desc":"لا تقم بحفظ كامل عنوان IP العميل في السجلات والإحصائيات",
"dns_config":"إعداد خادم DNS",
@@ -278,7 +291,9 @@
"custom_ip":"عنوان IP مخصص",
"blocking_ipv4":"حجب عنوان IPv4",
"blocking_ipv6":"حجب عنوان IPv6",
"blocked_response_ttl":"زمن حظر الاستجابة",
"blocked_response_ttl":"حظر استجابة TTL",
"blocked_response_ttl_desc":"تحديد عدد الثواني التي يجب على العملاء تخزين الاستجابة التي تمت تصفيتها مؤقتًا",
"form_enter_blocked_response_ttl":"أدخل وقت الاستجابة المحظورة TTL (بالثواني)",
"dnscrypt":"DNSCrypt",
"dns_over_https":"DNS-over-HTTPS",
"dns_over_tls":"DNS-over-TLS",
@@ -294,7 +309,19 @@
"rate_limit":"حدود التقييم",
"edns_enable":"فعل EDNS client subnet",
"edns_cs_desc":"أضف EDNS الشبكة الفرعية للعميل (ECS) إلى الطلبات الأولية وقم بتسجيل القيم المرسلة من قبل العملاء في سجل الاستعلام.",
"edns_use_custom_ip":"استخدام IP مخصص لـ EDNS",
"edns_use_custom_ip_desc":"السماح باستخدام IP مخصص لـ EDNS",
"rate_limit_desc":"عدد الطلبات في الثانية المسموح بها لكل عميل. جعله على 0 يعني عدم وجود حد.",
"rate_limit_subnet_len_ipv4":"طول بادئة الشبكة لعناوين IPv4",
"rate_limit_subnet_len_ipv4_desc":"طول بادئة الشبكة لعناوين IPv4 المستخدمة لتحديد معدل الحد الأقصى. الافتراضي هو 24",
"rate_limit_subnet_len_ipv4_error":"يجب أن يكون طول بادئة الشبكة IPv4 بين 0 و 32",
"rate_limit_subnet_len_ipv6":"طول بادئة الشبكة لعناوين IPv6",
"rate_limit_subnet_len_ipv6_desc":"طول بادئة الشبكة لعناوين IPv6 المستخدمة لتحديد معدل الحد الأقصى. الافتراضي هو 56",
"rate_limit_subnet_len_ipv6_error":"يجب أن يكون طول بادئة الشبكة IPv6 بين 0 و 128",
"form_enter_rate_limit_subnet_len":"أدخل طول بادئة الشبكة الفرعية لتحديد معدل الحد الأقصى",
"rate_limit_whitelist":"قائمة السماح بتحديد معدل الحد الأقصى",
"rate_limit_whitelist_desc":"عناوين IP المستبعدة من تحديد معدل الحد الأقصى",
"rate_limit_whitelist_placeholder":"أدخل عنوان IP واحد لكل سطر",
"blocking_ipv4_desc":"سيتم إرجاع عنوان IP لطلب محظور",
"blocking_ipv6_desc":"سيتم إرجاع عنوان IP لطلب AAAA محظور",
"blocking_mode_default":"الافتراضي: الرد بعنوان IP صفري (0.0.0.0 لـ A ؛ :: لـ AAAA) عند حظره بواسطة قاعدة نمط Adblock ؛ الرد بعنوان IP المحدد في القاعدة عند حظره بواسطة / etc / hosts-style rule",
@@ -302,14 +329,15 @@
"blocking_mode_nxdomain":"NXDOMAIN: الرد باستخدام رمز NXDOMAIN",
"blocking_mode_null_ip":"IP Null: الاستجابة بعنوان IP صفري (0.0.0.0 لـ A ؛ :: لـ AAAA)",
"blocking_mode_custom_ip":"استجابة IP مخصصة بعنوان IP تم تعيينه يدويًا",
"theme_auto":"تلقائي",
"theme_light":"فاتح",
"theme_dark":"ليلي",
"theme_dark":"داكن",
"upstream_dns_client_desc":"إذا احتفظت بهذا الحقل فارغًا ، فسيستخدم AdGuard Home الخوادم التي تم تكوينها في<0>DNS إعدادات</0>.",
"tracker_source":"مصدر المتعقب",
"source_label":"المصدر",
"found_in_known_domain_db":"تم العثور عليه في قاعدة بيانات دومينات معروفة.",
"category_label":"الفئة",
"rule_label":"قواعد",
"rule_label":"قاعدة (قواعد)",
"list_label":"قائمه",
"unknown_filter":"فلتر غير معروف {{filterId}}",
"known_tracker":"متعقب معروف",
@@ -320,14 +348,14 @@
"install_settings_port":"المنفذ",
"install_settings_interface_link":"ستكون واجهة الويب الخاصة بمسؤول AdGuard Home متاحة على العناوين التالية:",
"form_error_port":"أدخل رقم منفذ صالح",
"install_settings_dns":"خادم DNS",
"install_settings_dns":"خَادِم DNS",
"install_settings_dns_desc":"ستحتاج إلى ضبط أجهزتك أو جهاز التوجيه الخاص بك لاستخدام خادم DNS على العناوين التالية:",
"install_auth_desc":"يجب إعداد مصادقة كلمة المرور لواجهة ويب مسؤول AdGuard Home. في حال كان AdGuard Home لا يمكن الوصول إليه إلا في شبكتك المحلية ، فلا يزال من المهم حمايته من الوصول غير المقيد.",
"install_auth_username":"اسم المستخدم",
"install_auth_password":"الكلمة السرية",
"install_auth_confirm":"تاكيد كلمه المرور",
"install_auth_confirm":"تأكيد كلمة المرور",
"install_auth_username_enter":"أدخل اسم المستخدم",
"install_auth_password_enter":"أدخل كلمة المرور",
"install_step":"خطوة",
@@ -397,6 +425,9 @@
"encryption_hostnames":"اسم المستضيف",
"encryption_reset":"هل أنت متأكد أنك تريد إعادة تعيين إعدادات التشفير؟",
"encryption_warning":"تحذير",
"encryption_plain_dns_enable":"تمكين DNS العادي",
"encryption_plain_dns_desc":"الـDNS العادي مفعل افتراضيًا. يمكنك تعطيله لإجبار جميع الأجهزة على استخدام DNS المشفر. للقيام بذلك، يجب عليك تفعيل بروتوكول DNS المشفر على الأقل",
"encryption_plain_dns_error":"لتعطيل DNS العادي، قم بتمكين بروتوكول DNS المشفر على الأقل",
"topline_expiring_certificate":"شهادة SSL الخاصة بك على وشك الانتهاء. قم بتحديث <0>إعدادات التشفير</0>.",
"topline_expired_certificate":"انتهت صلاحية شهادة SSL الخاصة بك. قم بتحديث <0>إعدادات التشفير</0>.",
"form_error_port_range":"أدخل رقم المنفذ في النطاق 80-65535",
"client_confirm_delete":"هل أنت متأكد من أنك تريد حذف العميل \"{{key}}\"?",
"list_confirm_delete":"هل أنت متأكد أنك تريد حذف هذه القائمة؟",
"auto_clients_title":"Runtime clients",
"auto_clients_desc":"الأجهزة غير المدرجة في قائمة العملاء الدائمين الذين قد لا يزالون يستخدمون AdGuard Home",
"auto_clients_desc":"معلومات حول عناوين IP للأجهزة التي تستخدم أو قد تستخدم AdGuard Home. يتم جمع هذه المعلومات من عدة مصادر، بما في ذلك ملفات المضيفين، و DNS العكسي، إلخ.",
"access_title":"إعدادات الوصول",
"access_desc":"هنا يمكنك ضبط قواعد الوصول لخادم AdGuard Home DNS",
"access_allowed_title":"العملاء المسموحين",
@@ -457,6 +489,7 @@
"updates_checked":"يتوفر إصدار جديد من AdGuard Home",
"updates_version_equal":"AdGuard Home محدث",
"check_updates_now":"تحقق من وجود تحديثات الآن",
"version_request_error":"فشل التحقق من التحديث. يرجى التحقق من اتصالك بالإنترنت.",
"dns_privacy":"خصوصية DNS",
"setup_dns_privacy_1":"<0> DNS-over-TLS: </0> استخدم سلسلة <1> {{address}} </1>.",
"setup_dns_privacy_2":"<0> DNS-over-HTTPS: </0> استخدم سلسلة <1> {{address}} </1>.",
@@ -477,7 +510,9 @@
"setup_dns_notice":"من أجل استخدام <0> DNS-over-HTTPS </0> أو <1> DNS-over-TLS </1> ، تحتاج إلى <1> تكوين التشفير </1> في إعدادات AdGuard Home.",
"rewrite_added":"تمت إضافة إعادة كتابة DNS لـ \"{{key}}\" بنجاح",
"rewrite_deleted":"تم حذف إعادة كتابة DNS لـ \"{{key}}\" بنجاح",
"rewrite_updated":"تم تحديث إعادة كتابة DNS بنجاح",
"rewrite_add":"إضافة إعادة كتابة DNS",
"rewrite_edit":"تحرير إعادة كتابة DNS",
"rewrite_not_found":"لم يتم العثور على إعادة كتابة DNS",
"rewrite_confirm_delete":"هل أنت متأكد من أنك تريد حذف إعادة كتابة DNS لـ \"{{key}}\"؟",
"rewrite_desc":"يسمح بتكوين استجابة DNS المخصصة بسهولة لاسم نطاق معين.",
"schedule_modal_description":"سيحل هذا الجدول الزمني محل أي جداول موجودة لنفس اليوم من الأسبوع. يمكن أن يكون لكل يوم من أيام الأسبوع مدّة خمول واحدة فقط.",
"schedule_modal_time_off":"لا يوجد حظر للخدمة:",
"schedule_new":"جدول زمني جديد",
"schedule_edit":"تحرير الجدول الزمني",
"schedule_save":"حفظ الجدول الزمني",
"schedule_add":"إضافة جدول زمني",
"schedule_remove":"إزالة الجدول الزمني",
"schedule_from":"من",
"schedule_to":"إلى",
"sunday":"الأحد",
"monday":"الإثنين",
"tuesday":"الثلاثاء",
"wednesday":"الأربعاء",
"thursday":"الخميس",
"friday":"الجمعة",
"saturday":"السبت",
"sunday_short":"الأحد",
"monday_short":"الإثنين",
"tuesday_short":"الثلاثاء",
"wednesday_short":"الاربعاء",
"wednesday_short":"الأربعاء",
"thursday_short":"الخميس",
"friday_short":"الجمعة",
"saturday_short":"السبت"
"saturday_short":"السبت",
"upstream_dns_cache_configuration":"تهيئة ذاكرة التخزين المؤقت لنظام أسماء النطاقات المستقبلي",
"enable_upstream_dns_cache":"تمكين التخزين المؤقت لنظام أسماء النطاقات DNS لتكوين المنبع المخصص لهذا العميل",
"dns_cache_size":"حجم ذاكرة التخزين المؤقت لنظام أسماء النطاقات، بالبايت"
"found_in_known_domain_db":"Намерен в списъците с домейни.",
"category_label":"Категория",
@@ -282,6 +284,14 @@
"blocklist":"Черен списък",
"filter_category_general":"General",
"filter_category_security":"Сигурност",
"filter_category_other":"Друго",
"port_53_faq_link":"Порт 53 често е зает от \"DNSStubListener\" или \"systemd-resolved\" услуги. Моля, прочетете <0>тази инструкция</0> как да решите това.",
"upstream_parallel":"Použijte paralelní požadavky na urychlení řešení simultánním dotazováním na všechny navazující servery.",
"parallel_requests":"Paralelní požadavky",
"load_balancing":"Optimalizace vytížení",
"load_balancing_desc":"Optimalizovaný dotaz na odchozí server. AdGuard Home použije vážený náhodný algoritmus k výběru serveru, takže nejrychlejší server je používán častěji.",
"load_balancing_desc":"Dotazy jednoho odchozího serveru ve stejný čas.<br/>AdGuard Home používá náhodný algoritmus pro výběr serverů s nejnižším počtem neúspěšných vyhledávání a nejnižší průměrnou dobou vyhledávání.",
"bootstrap_dns":"Bootstrap DNS servery",
"bootstrap_dns_desc":"IP adresy DNS serverů používaných k překladu IP adres řešitelů DoH/DoT, které zadáte jako odchozí servery. Komentáře nejsou povoleny.",
"fallback_dns_title":"Záložní DNS servery",
"fallback_dns_desc":"Seznam záložních DNS serverů používaných v případě, že odchozí DNS servery neodpovídají. Syntaxe je stejná jako v hlavním poli pro odchozí servery výše.",
"fallback_dns_placeholder":"Zadejte jeden záložní DNS server na řádek",
"local_ptr_title":"Soukromé reverzní DNS servery",
"local_ptr_desc":"Servery DNS, které AdGuard Home používá pro lokální dotazy PTR. Tyto servery se používají k řešení požadavků PTR na adresy v soukromých rozmezích IP, například \"192.168.12.34\", pomocí reverzního DNS. Pokud není nastaveno, AdGuard Home automaticky použije výchozí řešitele vašeho OS s výjimkou adres samotného AdGuard Home.",
"local_ptr_desc":"DNS servery používané AdGuard Home pro soukromé požadavky PTR, SOA a NS. Požadavek je považován za soukromý, pokud požaduje doménu ARPA obsahující podsíť v rámci soukromých IP rozsahů (například \"192.168.12.34\") a pochází od klienta se soukromou IP adresou. Pokud není nastaveno, budou použity výchozí DNS řešitele vašeho operačního systému, s výjimkou IP adres AdGuard Home.",
"local_ptr_default_resolver":"Ve výchozím nastavení používá AdGuard Home následující reverzní DNS řešitele: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home nemohl určit vhodné soukromé reverzní DNS řešitele pro tento systém.",
"local_ptr_placeholder":"Zadejte jednu IP adresu na řádek",
"resolve_clients_title":"Povolit zpětné řešení IP adres klientů",
"resolve_clients_desc":"Obráceně vyřešit IP adresy klientů na jejich názvy hostitelů zasláním dotazů PTR příslušným řešitelům (soukromé DNS servery pro místní klienty, odchozí servery pro klienty s veřejnou IP adresou).",
"use_private_ptr_resolvers_desc":"Realizuje reverzní DNS vyhledávání pro lokální adresy pomocí těchto odchozích serverů. Pokud je funkce vypnuta, Adguard Home reaguje s NXDOMAIN na všechny takové PTR dotazy kromě klientů známých z DHCP, /etc/hosts, atd.",
"use_private_ptr_resolvers_desc":"Řešení požadavků PTR, SOA a NS pro domény ARPA obsahující soukromé IP adresy prostřednictvím soukromých odchozích serverů, DHCP, /etc/hosts atd. Pokud je zakázáno, AdGuard Home bude na všechny takové požadavky odpovídat pomocí NXDOMAIN.",
"check_dhcp_servers":"Zkontrolovat DHCP servery",
"save_config":"Uložit konfiguraci",
"enabled_dhcp":"DHCP server zapnutý",
@@ -154,7 +154,7 @@
"use_adguard_parental":"Použít službu AdGuard Rodičovská kontrola",
"use_adguard_parental_hint":"AdGuard Home zkontroluje, zda doména obsahuje materiály pro dospělé. Používá stejné API přátelské k ochraně osobních údajů jako služba Bezpečnost prohlížení.",
"enforce_save_search_hint":"AdGuard Home vynutí bezpečné vyhledávání v následujících vyhledávačích: Google, YouTube, Bing, DuckDuckGo, Yandex, Pixabay.",
"enforce_save_search_hint":"AdGuard Home vynutí bezpečné vyhledávání v následujících vyhledávačích: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay.",
"no_servers_specified":"Nebyly specifikovány žádné servery",
"general_settings":"Obecná nastavení",
"dns_settings":"Nastavení DNS",
@@ -294,6 +294,9 @@
"blocked_response_ttl":"TTL blokované odezvy",
"blocked_response_ttl_desc":"Určuje, na kolik sekund by měli klienti ukládat filtrovanou odezvu do mezipaměti",
"form_enter_blocked_response_ttl":"Zadejte TTL blokované odezvy (v sekundách)",
"upstream_timeout_desc":"Určuje počet sekund čekání na odpověď od odchozího serveru",
"form_enter_upstream_timeout":"Zadejte dobu časového limitu odchozího serveru v sekundách",
"dnscrypt":"DNSCrypt",
"dns_over_https":"DNS skrze HTTPS",
"dns_over_tls":"DNS skrze TLS",
@@ -598,7 +601,7 @@
"disable_ipv6":"Zakázat řešení IPv6 adres",
"disable_ipv6_desc":"Odstranění všech dotazů DNS na adresy IPv6 (typ AAAA) a odstranění náznaků IPv6 z odpovědí HTTPS.",
"fastest_addr":"Nejrychlejší IP adresa",
"fastest_addr_desc":"Dotazovat všechny DNS servery a vrátit nejrychlejší IP adresu ze všech odpovědí. To zpomalí dotazy DNS, protože AdGuard Home musí čekat na odpovědi ze všech serverů DNS, ale celková konektivita se zlepší.",
"fastest_addr_desc":"Počká na odpovědi <b>všech</b> serverů DNS, změří rychlost připojení TCP pro každý server a vrátí IP adresu serveru s nejvyšší rychlostí připojení.<br/>Tento režim může výrazně zpomalit dotazy DNS, pokud jeden nebo více odchozích serverů neodpovídá. Ujistěte se, že vaše odchozí servery jsou stabilní a že časový limit odchozích serverů je nízký.",
"autofix_warning_text":"Pokud kliknete na „Opravit“, AdGuard Home nakonfiguruje váš systém tak, aby používal DNS server AdGuard Home.",
"autofix_warning_list":"Jsou prováděny následující úlohy: <0>Deaktivace systému DNSStubListener</0> <0>Nastavení adresy serveru DNS na 127.0.0.1</0> <0>Nahrazení cíle symbolického odkazu z /etc/resolv.conf do /run/systemd/resolve/resolv.conf</0> <0>Zastavení služby DNSStubListener (znovu načtení služby systemd-resolved)</0>",
"autofix_warning_result":"Výsledkem je, že všechny požadavky DNS z vašeho systému jsou ve výchozím nastavení zpracovány službou AdGuard Home.",
"upstream_parallel":"Brug parallelforespørgsler til at accelerere fortolkningen ved at forespørge alle upstream-servere samtidigt.",
"parallel_requests":"Parallelle forespørgsler",
"load_balancing":"Belastningsfordeling",
"load_balancing_desc":"Forespørg én server ad gangen.AdGuard Home vil bruge en vægtet randomiseringsalgoritme til valg af server, så den hurtigste server oftere anvendes.",
"load_balancing_desc":"Forespørg én upstream-server ad gangen.<br/>AdGuard Home bruger en vægtet tilfældighedsalgoritme til vælg af servere med det laveste antal fejlslagne opslag og den laveste gennemsnitlige opslagstid.",
"bootstrap_dns":"Bootstrap DNS-servere",
"bootstrap_dns_desc":"IP-adresser på DNS-servere, som bruges til at opløse IP-adresser på de DoH/DoT-opløsere, som angives som upstreams. Kommentarer er ikke tilladt.",
"fallback_dns_title":"Reserve DNS-servere",
"fallback_dns_desc":"Liste over reserve (fallback) DNS-servere, som bruges, når upstream DNS-servere ikke reagerer. Samme syntaks som i upstream-hovedfeltet ovenfor.",
"fallback_dns_placeholder":"Angiv én reserve DNS-server pr. linje",
"local_ptr_title":"Private reverse DNS-servere",
"local_ptr_desc":"DNS-servere brugt af AdGuard Home til lokale PTR-forespørgsler. Disse servere bruges til at opløse PTR-forespørgsler fra private IP-adresseområder, f.eks. \"192.168.12.34\", vha. reverse DNS. Hvis ikke opsat, bruger AdGuard Home operativsystems standard DNS-opløsere undtagen for sine egne adresser.",
"local_ptr_desc":"DNS-serverne brugt af AdGuard Home til private PTR-, SOA- og NS-forespørgsler. En forespørgsel anses som privat, hvis den omhandler et ARPA-domæne indeholdende et undernet i et privat IP-områder, (såsom \"192.168.12.34\") og kommer fra en klient med en privat adresse. Hvis ikke opsat, bruger AdGuard Home OS'ets adresser på standard DNS-opløserne, bortset fra AdGuard Home-adresserne.",
"local_ptr_default_resolver":"AdGuard Home bruger som standard flg. reverse DNS-opløsere: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home kunne ikke fastslå egnede private reverse DNS-opløsere for dette system.",
"local_ptr_placeholder":"Angiv én IP-adresse pr. linje",
"resolve_clients_title":"Aktivér omvendt løsning af klienters IP-adresser",
"resolve_clients_desc":"Opløs klienters IP-adresser reverseret til deres værtsnavne ved at sende PTR-forespørgsler til korresponderende opløsere (private DNS-servere til lokale klienter, upstream-servere til klienter med offentlige IP-adresser).",
"use_private_ptr_resolvers_desc":"Udfør reverse DNS-opslag for lokalt leverede adresser vha. disse upstream-servere. Hvis deaktiveret, svarer AdGuard Home med NXDOMAIN på alle sådanne PTR-forespørgsler bortset fra for klienter kendt via DHCP, /etc/hosts mv.",
"use_private_ptr_resolvers_desc":"Opløs PTR-, SOA- og NS-forespørgsler til ARPA-domæner indeholdende private adresser vha. private upstream-servere, DHCP, /etc/hosts mv. Hvis deaktiveret, besvarer AdGuard Home sådanne forespørgsler med NXDOMAIN.",
"use_adguard_parental_hint":"AdGuard Home vil tjekke, om domænet indeholder voksenindhold vha. den samme fortrolighedsvenlige API som browsingsikkerhedswebtjenesten.",
"enforce_safe_search":"Brug sikker søgning",
"enforce_save_search_hint":"AdGuard Home vil håndhæve sikker søgning i flg. søgemaskiner: Google, YouTube, Bing, DuckDuckGo, Yandex og Pixabay.",
"enforce_save_search_hint":"AdGuard Home vil håndhæve sikker søgning i flg. søgemaskiner: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay.",
"no_servers_specified":"Ingen servere angivet",
"general_settings":"Generelle indstillinger",
"dns_settings":"DNS-indstillinger",
@@ -294,6 +294,9 @@
"blocked_response_ttl":"Blokeret svar TTL",
"blocked_response_ttl_desc":"Angiver, i hvor mange sekunder klienterne skal cache-lagre et filtreret svar",
"upstream_timeout_desc":"Angiver antallet af sekunder, der skal ventes på et svar fra upstream-serveren",
"form_enter_upstream_timeout":"Angiv varigheden af upstream-server timeout i sekunder",
"dnscrypt":"DNSCrypt",
"dns_over_https":"DNS-over-HTTPS",
"dns_over_tls":"DNS-over-TLS",
@@ -598,7 +601,7 @@
"disable_ipv6":"Deaktivér IPv6-adresseopløsning",
"disable_ipv6_desc":"Drop alle DNS-forespørgsler for IPv6-adresser (type AAAA), og fjern IPv6-tips fra HTTPS-svar.",
"fastest_addr":"Hurtigste IP-adresse",
"fastest_addr_desc":"Forespørger alle DNS-servere og returner den hurtigste IP-adresse blandt alle svar. Dette vil gøre DNS-forespørgslerne langsommere grundet afventning af svar fra alle DNS-servere, men forbedrer samlet set forbindelsen.",
"fastest_addr_desc":"Vent på svar fra <b>alle</b> DNS-servere, mål TCP-forbindelseshastigheden for hver server, og returner IP-adressen på serveren med den hurtigste forbindelseshastighed.<br/>Denne tilstand kan sinke DNS-forespørgsler, betydeligt hvis en eller flere upstream-servere ikke svarer. Sørg for, at upstream-serverene er stabile, og at upstream-timeouten er lav.",
"autofix_warning_text":"Klikker du på \"Reparér\", opsætter AdGuard Home dit system til brug med AdGuard Home DNS-server.",
"autofix_warning_list":"Den vil udføre disse opgaver: <0>Deaktivere system DNSStubListener</0> <0>Opsætte DNS-serveradressen til 127.0.0.1</0> <0>Erstatte symbolsk linkmål for /etc/resolv.conf med /run/systemd/resolve/resolv.conf</0> <0>Stoppe DNSStubListener (genindlæs systemd-opløst tjeneste)</0>",
"autofix_warning_result":"Det betyder, at alle DNS-forespørgsler fra dit system som standard behandles af AdGuard Home.",
"upstream_parallel":"Parallele Abfragen verwenden, um das Auflösen zu beschleunigen, indem alle Upstream-Server gleichzeitig abgefragt werden.",
"parallel_requests":"Paralleles Abfragen",
"load_balancing":"Lastverteilung",
"load_balancing_desc":"Einen Server nach dem anderen abfragen. AdGuard Home verwendet den gewichteten Zufallsalgorithmus, um den Server so auszuwählen, dass der schnellste Server häufiger verwendet wird.",
"load_balancing_desc":"Es wird jeweils ein Upstream-Server abgefragt.<br/> AdGuard Home verwendet einen gewichteten Zufallsalgorithmus, um die Server mit der geringsten Anzahl an fehlgeschlagenen Suchvorgängen und der niedrigsten durchschnittlichen Suchzeit auszuwählen.",
"bootstrap_dns":"Bootstrap-DNS-Server",
"bootstrap_dns_desc":"IP-Adressen der DNS-Server, die zum Auflösen der IP-Adressen von DoH/DoT Upstream-Servern verwendet werden, die Sie angegeben haben. Kommentare sind nicht erlaubt.",
"fallback_dns_title":"Fallback-DNS-Server",
"fallback_dns_desc":"Liste der Fallback-DNS-Server, die verwendet werden, wenn die Upstream-DNS-Server nicht antworten. Die Syntax ist die gleiche wie im Hauptfeld für Upstream-Server oben.",
"fallback_dns_placeholder":"Geben Sie einen Fallback-DNS-Server pro Zeile ein",
"local_ptr_title":"Private inverse DNS-Server",
"local_ptr_desc":"Die DNS-Server, die AdGuard Home für lokale PTR-Abfragen verwendet. Diese Server werden verwendet, um die Hostnamen von Clients mit privaten IP-Adressen, z. B. „192.168.12.34“, per inverse DNS-Anfragen aufzulösen. Wenn nicht festgelegt, verwendet AdGuard Home die Adressen der Standard-DNS-Auflöser Ihres Betriebssystems mit Ausnahme der Adressen von AdGuard Home selbst.",
"local_ptr_desc":"Von AdGuard Home verwendete DNS-Server für private PTR-, SOA- und NS-Anfragen. Eine Anfrage gilt als privat, wenn sie nach einer ARPA-Domain fragt, die ein Subnetz innerhalb privater IP-Bereiche enthält (z. B. „192.168.12.34“) und von einem Client mit privater IP-Adresse stammt. Wenn nicht eingestellt, werden die Standard-DNS-Auflöser Ihres Betriebssystems verwendet, außer für die IP-Adressen von AdGuard Home.",
"local_ptr_default_resolver":"Standardmäßig verwendet AdGuard Home die folgenden inversen DNS-Resolver: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home konnte keine geeigneten privaten Invers-DNS-Resolver für dieses System ermitteln.",
"local_ptr_placeholder":"Geben Sie eine IP-Adresse pro Zeile ein",
"resolve_clients_title":"Hostnamenauflösung der Clients aktivieren",
"resolve_clients_desc":"Inverses Auflösen der IP-Adressen der Clients in ihre Hostnamen durch Senden von PTR-Anfragen an die entsprechenden Resolver (private DNS-Server für lokale Kunden, Upstream-Server für Kunden mit öffentlichen IP-Adressen).",
"use_private_ptr_resolvers_desc":"Führt inverse DNS-Abfragen für lokal bereitgestellte Adressen mit diesen Upstream-Servern durch. Wenn deaktiviert, antwortet AdGuard Home mit NXDOMAIN auf alle solchen PTR-Anfragen, außer für Clients, die über DHCP, /etc/hosts usw. bekannt sind.",
"use_private_ptr_resolvers_desc":"Löst PTR-, SOA- und NS-Anfragen für ARD-Domains mit privaten IP-Adressen über private Upstream-Server, DHCP, /etc/hosts usw. auf. Ist diese Option deaktiviert, antwortet AdGuard Home auf alle derartigen Anfragen mit NXDOMAIN.",
"check_dhcp_servers":"Auf DHCP-Server prüfen",
"save_config":"Konfiguration speichern",
"enabled_dhcp":"DHCP-Server aktiviert",
@@ -154,7 +154,7 @@
"use_adguard_parental":"AdGuard Webservice für Kindersicherung verwenden",
"use_adguard_parental_hint":"AdGuard Home wird prüfen, ob die Domain jugendgefährdende Inhalte enthält. Zum Schutz Ihrer Privatsphäre wird die selbe API wie für den Webservice für Internetsicherheit verwendet.",
"enforce_safe_search":"Sichere Suche verwenden",
"enforce_save_search_hint":"AdGuard kann Sichere Suche für folgende Suchmaschinen erzwingen: Google, YouTube, Bing, DuckDuckGo, Yandex und Pixabay.",
"enforce_save_search_hint":"AdGuard kann Sichere Suche für folgende Suchmaschinen erzwingen: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex und Pixabay.",
"no_servers_specified":"Keine Server festgelegt",
"general_settings":"Allgemeine Einstellungen",
"dns_settings":"DNS-Einstellungen",
@@ -294,6 +294,9 @@
"blocked_response_ttl":"Gültigkeitsdauer der blockierten Antwort",
"blocked_response_ttl_desc":"Gibt an, wie viele Sekunden lang die Clients eine gefilterte Antwort zwischenspeichern sollen",
"form_enter_blocked_response_ttl":"Geben Sie die Gültigkeitsdauer für blockierte Antworten ein (in Sekunden)",
"upstream_timeout":"Upstream-Timeout",
"upstream_timeout_desc":"Gibt die Anzahl der Sekunden an, die auf eine Antwort des Upstream-Servers gewartet werden soll",
"form_enter_upstream_timeout":"Geben Sie die Timeout-Dauer des Upstream-Servers in Sekunden ein",
"dnscrypt":"DNSCrypt",
"dns_over_https":"DNS-over-HTTPS",
"dns_over_tls":"DNS-over-TLS",
@@ -598,7 +601,7 @@
"disable_ipv6":"IPv6 deaktivieren",
"disable_ipv6_desc":"Alle DNS-Anfragen für IPv6-Adressen (Typ AAAA) verwerfen und IPv6-Hinweise aus HTTPS-Antworten entfernen.",
"fastest_addr":"Schnellste IP-Adresse",
"fastest_addr_desc":"Fragen Sie alle DNS-Server ab und geben Sie die schnellste IP-Adresse unter allen Antworten zurück. Dies verlangsamt DNS-Abfragen, da AdGuard Home auf Antworten von allen DNS-Servern warten muss, verbessert jedoch die Gesamtkonnektivität.",
"fastest_addr_desc":"Auf Antworten von <b>allen</b> DNS-Servern warten, die TCP-Verbindungsgeschwindigkeit für jeden Server messen und die IP-Adresse des Servers mit der schnellsten Verbindungsgeschwindigkeit zurückgeben.<br/>Dieser Modus kann DNS-Anfragen erheblich verlangsamen, wenn ein oder mehrere Server nicht antworten. Stellen Sie sicher, dass Ihre Server stabil laufen und das Upstream-Timeout niedrig ist.",
"autofix_warning_text":"Wenn Sie auf „Beheben“ klicken, konfiguriert AdGuardHome Ihr System für die Verwendung des AdGuardHome-DNS-Servers.",
"autofix_warning_list":"Es werden folgende Aufgaben ausgeführt: <0>Deaktivieren des DNSStubListener-Systems</0> <0>Festlegen der DNS-Server-Adresse auf 127.0.0.1</0> <0>Ersetzen des symbolischen Linkziels von /etc/resolv.conf auf /run/systemd/resolve/resolv.conf</0> <0>Anhalten des DNSStubListener (systemseitig aufgelöster Dienst wird nachladen)</0>",
"autofix_warning_result":"Als Folge daraus werden alle DNS-Anforderungen von Ihrem System standardmäßig von AdGuardHome verarbeitet.",
"upstream_parallel":"Use parallel queries to speed up resolving by querying all upstream servers simultaneously.",
"parallel_requests":"Parallel requests",
"load_balancing":"Load-balancing",
"load_balancing_desc":"Query one upstream server at a time.AdGuard Home uses its weighted random algorithm to pick the server so that the fastest server is used more often.",
"load_balancing_desc":"Query one upstream server at a time.<br/>AdGuard Home uses a weighted random algorithm to select servers with the lowest number of failed lookups and the lowest average lookup time.",
"bootstrap_dns":"Bootstrap DNS servers",
"bootstrap_dns_desc":"IP addresses of DNS servers used to resolve IP addresses of the DoH/DoT resolvers you specify as upstreams. Comments are not permitted.",
"fallback_dns_title":"Fallback DNS servers",
"fallback_dns_desc":"List of fallback DNS servers used when upstream DNS servers are not responding. The syntax is the same as in the main upstreams field above.",
"fallback_dns_placeholder":"Enter one fallback DNS server per line",
"local_ptr_title":"Private reverse DNS servers",
"local_ptr_desc":"The DNS servers that AdGuard Home uses for local PTR queries. These servers are used to resolve PTR requests for addresses in private IP ranges, for example \"192.168.12.34\", using reverse DNS. If not set, AdGuard Home uses the addresses of the default DNS resolvers of your OS except for the addresses of AdGuard Home itself.",
"local_ptr_desc":"DNS servers used by AdGuard Home for private PTR, SOA, and NS requests. A request is considered private if it asks for an ARPA domain containing a subnet within private IP ranges (such as \"192.168.12.34\") and comes from a client with a private IP address. If not set, the default DNS resolvers of your OS will be used, except for the AdGuard Home IP addresses.",
"local_ptr_default_resolver":"By default, AdGuard Home uses the following reverse DNS resolvers: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home could not determine suitable private reverse DNS resolvers for this system.",
"local_ptr_placeholder":"Enter one IP address per line",
"resolve_clients_title":"Enable reverse resolving of clients' IP addresses",
"resolve_clients_desc":"Reversely resolve clients' IP addresses into their hostnames by sending PTR queries to corresponding resolvers (private DNS servers for local clients, upstream servers for clients with public IP addresses).",
"use_private_ptr_resolvers_title":"Use private reverse DNS resolvers",
"use_private_ptr_resolvers_desc":"Perform reverse DNS lookups for locally served addresses using these upstream servers. If disabled, AdGuard Home responds with NXDOMAIN to all such PTR requests except for clients known from DHCP, /etc/hosts, and so on.",
"use_private_ptr_resolvers_desc":"Resolve PTR, SOA, and NS requests for ARPA domains containing private IP addresses through private upstream servers, DHCP, /etc/hosts, etc. If disabled, AdGuard Home will respond to all such requests with NXDOMAIN.",
"check_dhcp_servers":"Check for DHCP servers",
"save_config":"Save configuration",
"enabled_dhcp":"DHCP server enabled",
@@ -154,7 +154,7 @@
"use_adguard_parental":"Use AdGuard parental control web service",
"use_adguard_parental_hint":"AdGuard Home will check if domain contains adult materials. It uses the same privacy-friendly API as the browsing security web service.",
"enforce_safe_search":"Use Safe Search",
"enforce_save_search_hint":"AdGuard Home will enforce safe search in the following search engines: Google, YouTube, Bing, DuckDuckGo, Yandex, Pixabay.",
"enforce_save_search_hint":"AdGuard Home will enforce safe search in the following search engines: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay.",
"no_servers_specified":"No servers specified",
"general_settings":"General settings",
"dns_settings":"DNS settings",
@@ -294,6 +294,9 @@
"blocked_response_ttl":"Blocked response TTL",
"blocked_response_ttl_desc":"Specifies for how many seconds the clients should cache a filtered response",
"upstream_timeout_desc":"Specifies the number of seconds to wait for a response from the upstream server",
"form_enter_upstream_timeout":"Enter the upstream server timeout duration in seconds",
"dnscrypt":"DNSCrypt",
"dns_over_https":"DNS-over-HTTPS",
"dns_over_tls":"DNS-over-TLS",
@@ -598,7 +601,7 @@
"disable_ipv6":"Disable resolving of IPv6 addresses",
"disable_ipv6_desc":"Drop all DNS queries for IPv6 addresses (type AAAA) and remove IPv6 hints from HTTPS responses.",
"fastest_addr":"Fastest IP address",
"fastest_addr_desc":"Query all DNS servers and return the fastest IP address among all responses. This slows down DNS queries as AdGuard Home has to wait for responses from all DNS servers, but improves the overall connectivity.",
"fastest_addr_desc":"Wait for responses from <b>all</b> DNS servers, measure the TCP connection speed for each server, and return the IP address of the server with the fastest connection speed.<br/>This mode can significantly slow down DNS queries, if one or more upstream servers are not responding. Make sure that your upstream servers are stable and your upstream timeout is low.",
"autofix_warning_text":"If you click \"Fix\", AdGuard Home will configure your system to use AdGuard Home DNS server.",
"autofix_warning_list":"It will perform these tasks: <0>Deactivate system DNSStubListener</0> <0>Set DNS server address to 127.0.0.1</0> <0>Replace symbolic link target of /etc/resolv.conf with /run/systemd/resolve/resolv.conf</0> <0>Stop DNSStubListener (reload systemd-resolved service)</0>",
"autofix_warning_result":"As a result all DNS requests from your system will be processed by AdGuard Home by default.",
"upstream_parallel":"Usar consultas paralelas para acelerar la resolución al consultar simultáneamente a todos los servidores DNS de subida.",
"parallel_requests":"Consultas paralelas",
"load_balancing":"Balanceo de carga",
"load_balancing_desc":"Consulta un servidor DNS de subida a la vez.AdGuard Home utiliza su algoritmo aleatorio ponderado para elegir el servidor más rápido y sea utilizado con más frecuencia.",
"load_balancing_desc":"Consulta un servidor Dns upstream a la vez.<br/>AdGuard Home utiliza un algoritmo aleatorio ponderado para seleccionar los servidores con el menor número de fallos y el menor tiempo medio de búsqueda.",
"bootstrap_dns":"Servidores DNS de arranque",
"bootstrap_dns_desc":"Direcciones IP de servidores DNS utilizadas para resolver direcciones IP de los solucionadores DoH/DoT que especifiques como ascendentes. No se permiten comentarios.",
"fallback_dns_title":"Servidores DNS alternativos",
"fallback_dns_desc":"Lista de servidores DNS alternativos utilizados cuando los servidores DNS de subida no responden. La sintaxis es la misma que en el campo de los principales DNS de subida anterior.",
"fallback_dns_placeholder":"Ingresa un servidor DNS alternativo por línea",
"local_ptr_title":"Servidores DNS inversos y privados",
"local_ptr_desc":"Los servidores DNS que AdGuard Home utiliza para las consultas PTR locales. Estos servidores se utilizan para resolver las peticiones PTR de direcciones en rangos de IP privadas, por ejemplo \"192.168.12.34\", utilizando DNS inverso. Si no está establecido, AdGuard Home utilizará los resolutores DNS predeterminados de tu sistema operativo, excepto las direcciones del propio AdGuard Home.",
"local_ptr_desc":"Los servidores DNS que AdGuard Home utiliza para consultas PTR, SOA y NS privadas. La petición se considera privada si solicita un dominio ARPA que contiene una subred dentro de rangos IP privados, por ejemplo \"192.168.12.34\", y procede de un cliente con dirección privada. Si no se configura, AdGuard Home utiliza las direcciones de los resolvedores DNS predeterminados de tu sistema operativo, excepto las direcciones del propio AdGuard Home.",
"local_ptr_default_resolver":"Por defecto, AdGuard Home utiliza los siguientes resolutores DNS inversos: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home no pudo determinar los resolutores DNS inversos y privados adecuados para este sistema.",
"local_ptr_placeholder":"Ingresa una dirección IP por línea",
"resolve_clients_title":"Habilitar la resolución inversa de las direcciones IP de clientes",
"resolve_clients_desc":"Resolve de manera inversa las direcciones IP de los clientes a sus nombres de hosts enviando consultas PTR a los resolutores correspondientes (servidores DNS privados para clientes locales, servidores DNS de subida para clientes con direcciones IP públicas).",
"use_private_ptr_resolvers_title":"Usar resolutores DNS inversos y privados",
"use_private_ptr_resolvers_desc":"Realiza búsquedas DNS inversas para direcciones servidas localmente utilizando estos servidores DNS de subida. Si está deshabilitado, AdGuard Home responderá con NXDOMAIN a todas las peticiones PTR de este tipo, excepto para los clientes conocidos por DHCP, /etc/hosts, etc.",
"use_private_ptr_resolvers_desc":"Resolver las peticiones PTR, SOA y NS para dominios ARPA que contienen direcciones privadas utilizando servidores upstream privados, DHCP, /etc/hosts, etc. Si se desactiva, AdGuard Home responde a todas estas consultas con NXDOMAIN.",
"check_dhcp_servers":"Comprobar si hay servidores DHCP",
"save_config":"Guardar configuración",
"enabled_dhcp":"Servidor DHCP habilitado",
@@ -154,7 +154,7 @@
"use_adguard_parental":"Usar el control parental de AdGuard",
"use_adguard_parental_hint":"AdGuard Home comprobará si el dominio contiene materiales para adultos. Utiliza la misma API amigable con la privacidad del servicio web de seguridad de navegación.",
"enforce_safe_search":"Usar búsqueda segura",
"enforce_save_search_hint":"AdGuard Home reforzará la búsqueda segura en los siguientes motores de búsqueda: Google, YouTube, Bing, DuckDuckGo, Yandex y Pixabay.",
"enforce_save_search_hint":"AdGuard Home reforzará la búsqueda segura en los siguientes motores de búsqueda: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex y Pixabay.",
"no_servers_specified":"No hay servidores especificados",
"general_settings":"Configuración general",
"dns_settings":"Configuración del DNS",
@@ -294,6 +294,9 @@
"blocked_response_ttl":"Respuesta TTL bloqueada",
"blocked_response_ttl_desc":"Especifica durante cuántos segundos los clientes deben almacenar en cache una respuesta filtrada",
"form_enter_blocked_response_ttl":"Ingresa el TTL de respuesta bloqueada (segundos)",
"upstream_timeout":"Tiempo de espera del upstream",
"upstream_timeout_desc":"Especifica el número de segundos que se debe esperar para recibir una respuesta del servidor upstream",
"form_enter_upstream_timeout":"Ingresa la duración del tiempo de espera del servidor DNS upstream en segundos",
"dnscrypt":"DNSCrypt",
"dns_over_https":"DNS mediante HTTPS",
"dns_over_tls":"DNS mediante TLS",
@@ -598,7 +601,7 @@
"disable_ipv6":"Deshabilitar resolución de direcciones IPv6",
"disable_ipv6_desc":"Descarta todas las consultas de DNS para direcciones IPv6 (tipo AAAA) y elimina las sugerencias de IPv6 de las respuestas HTTPS.",
"fastest_addr":"Dirección IP más rápida",
"fastest_addr_desc":"Consulta todos los servidores DNS y devuelve la dirección IP más rápida de todas las respuestas. Esto ralentiza las consultas DNS ya que AdGuard Home tiene que esperar las respuestas de todos los servidores DNS, pero mejora la conectividad general.",
"fastest_addr_desc":"Espera a que respondan <b>todos</b> los servidores DNS, mide la velocidad de conexión TCP de cada servidor y devuelve la Dirección IP del servidor con la velocidad de conexión más rápida.<br/>Este modo puede ralentizar significativamente las consultas DNS, si uno o más servidores DNS de upstream no están respondiendo. Asegúrate de que tus servidores DNS upstream sean estables y tu tiempo de espera de upstream sea bajo.",
"autofix_warning_text":"Si haces clic en \"Corregir\", AdGuard Home configurará tu sistema para utilizar el servidor DNS de AdGuard Home.",
"autofix_warning_list":"Realizará estas tareas: <0>Deshabilitar el sistema DNSStubListener</0> <0>Establecer la dirección del servidor DNS en 127.0.0.1</0> <0>Reemplazar el destino del enlace simbólico de /etc/resolv.conf por /run/systemd/resolve/resolv.conf</0> <0>Detener DNSStubListener (recargar el servicio systemd-resolved)</0>",
"autofix_warning_result":"Como resultado, todas las peticiones DNS de tu sistema serán procesadas por AdGuard Home de manera predeterminada.",
"cache_optimistic_desc":"AdGuard Home را وادار می کند که از سمت حافظه پنهان پاسخ دهد حتی وقتی که موارد وارد شده منقضی شده باشد و همچنین سعی بر تازه کردن آنها می کند.",
"filter_category_general":"General",
"filter_category_security":"مسدودسازی بدافزار و فیشینگ",
"filter_category_regional":"منطقهای",
"filter_category_other":"ساير",
"use_saved_key":"از کلید ذخیره شده قبلی استفاده کنید",
"upstream_parallel":"Käytä rinnakkaisia pyyntöjä ja nopeuta selvitystä käyttämällä kaikkia ylävirtapalvelimia samanaikaisesti.",
"parallel_requests":"Rinnakkaiset pyynnöt",
"load_balancing":"Kuormantasaus",
"load_balancing_desc":"Lähetä pyyntö yhdelle ylävirtapalvelimelle kerrallaan. AdGuard Home pyrkii valitsemaan nopeimman palvelimen painotetun satunnaisalgoritminsa avulla.",
"load_balancing_desc":"Lähetä kysely kerrallaan yhdelle ylävirtapalvelimelle. AdGuard Home valitsee painotetun satunnaisalgoritmin avulla palvelimet, joilla on vähiten epäonnistuneita hakuja ja keskimääräisesti lyhin hakuaika.",
"fallback_dns_desc":"Listaus DNS-varapalvelimista, joita käytetään kun lähtevät DNS-palvelimet eivät vastaa. Syntaksi on sama kuin yllä olevassa pääylävirrat-kentässä.",
"fallback_dns_placeholder":"Syötä yksi DNS-varapalvelin per rivi",
"local_ptr_desc":"DNS-palvelimet, joita AdGuard Home käyttää paikallisille PTR-pyynnöille. Näitä palvelimia käytetään yksityistä IP-osoitetta käyttävien PTR-pyyntöjen osoitteiden, kuten \"192.168.12.34\", selvitykseen käänteis-DNS:n avulla. Jos ei käytössä, AdGuard Home käyttää käyttöjärjestelmän oletusarvoisia DNS-resolvereita, poislukien AdGuard Homen omat osoitteet.",
"local_ptr_desc":"AdGuard Homen yksityisille PTR-, SOA- ja NS-pyynnöille käyttämät DNS-palvelimet. Pyyntöä luokitellaan yksityiseksi, jos se pyytää yksityistä IP-aluetta (kuten \"192.168.12.34\") käyttävän aliverkon sisältävää ARPA-verkkotunnusta ja on lähtöisin päätteeltä, jolla on yksityinen IP-osoite. Jos tätä ei ole määritetty, käytetään käyttöjärjestelmän oletusarvoisia DNS-resolvereita (AdGuard Homen IP-osoitteet pois lukien).",
"local_ptr_default_resolver":"Oletusarvoisesti AdGuard Home käyttää seuraavia käänteis-DNS-resolvereita: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home ei voinut määrittää tälle järjestelmälle sopivaa yksityistä käänteis-DNS-resolveria.",
"local_ptr_placeholder":"Syötä yksi IP-osoite per rivi",
"use_private_ptr_resolvers_desc":"Suorita käänteis-DNS-selvitykset paikallisesti tarjotuille osoitteille käyttäen näitä ylävirtapalvelimia. Jos ei käytössä, vastaa AdGuard Home kaikkiin sen tyyppisiin PTR-pyyntöihin NXDOMAIN-arvolla, pois lukien DHCP, /etc/hosts, yms. -tiedoista tunnistettut päätelaitteet.",
"use_private_ptr_resolvers_desc":"Selvitä yksityisiä IP-osoitteita sisältävien ARPA-verkkotunnusten PTR-, SOA- ja NS-pyynnöt käyttäen yksityisiä ylävirtapalvelimia, DHCP:tä, /etc/hosts-määrityksiä, yms. Jos tämä ei ole käytössä, AdGuard Home vastaa tällaisiin pyyntöihin NXDOMAIN-tiedolla.",
"use_adguard_parental_hint":"AdGuard Home tarkistaa, sisältääkö verkkotunnus aikuisille tarkoitettua sisältöä. Se käyttää samaa tietosuojapainotteista rajapintaa, kuin turvallisen selauksen palvelu.",
"enforce_safe_search":"Käytä turvallista hakua",
"enforce_save_search_hint":"AdGuard Home voi pakottaa turvallisen haun käyttöön seuraavissa hakukoneissa: Google, YouTube, Bing, DuckDuckGo, Yandex, Pixabay.",
"enforce_save_search_hint":"AdGuard Home pakottaa turvallisen haun käyttöön seuraavissa hakukoneissa: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex ja Pixabay.",
"no_servers_specified":"Palvelimia ei ole määritetty",
"blocking_mode_default":"Oletus: Vastaa IP-nollaosoitteella (0.0.0.0 korvaa A; :: korvaa AAAA) kun estetään mainoseston säännöllä; vastaa säännön määrittämällä IP-osoitteella kun estetään /etc/hosts-tyyppisellä säännöllä",
"blocking_mode_refused":"REFUSED: Vastaa REFUSED-koodilla",
"blocking_mode_nxdomain":"NXDOMAIN: Vastaa NXDOMAIN-koodilla",
"blocking_mode_nxdomain":"NXDOMAIN: Vastaa NXDOMAIN-tiedolla",
"blocking_mode_null_ip":"Tyhjä IP: Vastaa IP-nollaosoitteella (0.0.0.0 korvaa A; :: korvaa AAAA)",
"blocking_mode_custom_ip":"Mukautettu IP: Vastaa manuaalisesti määritetyllä IP-osoitteella",
"theme_auto":"Automaattinen",
@@ -501,8 +501,8 @@
"setup_dns_privacy_ios_1":"<0>DNSCloak</0> tukee <1>DNS-over-HTTPS</1>, mutta oman palvelimen käyttö' varten sille on luotava <2>DNS Stamp</2> -merkintä.",
"setup_dns_privacy_ios_2":"<0>AdGuard iOS:lle</0> tukee <1>DNS-over-HTTPS</1> ja <1>DNS-over-TLS</1> -toteutuksia.",
"upstream_parallel":"Utilisez des requêtes parallèles pour accélérer la résolution en requêtant simultanément tous les serveurs en amont.",
"parallel_requests":"Requêtes en parallèle",
"load_balancing":"Équilibrage de charge",
"load_balancing_desc":"Interroger un serveur en amont à la fois.AdGuard Home utilise son algorithme aléatoire pondéré pour choisir le serveur de sorte que le serveur le plus rapide soit utilisé plus souvent.",
"load_balancing_desc":"Une requête par serveur en amont à la fois.<br/>AdGuard Home utilise un algorithme aléatoire pondéré pour sélectionner les serveurs avec le plus petit nombre d'échecs de recherche et le temps de recherche moyen le plus bas.",
"bootstrap_dns":"Serveurs DNS d'amorçage",
"bootstrap_dns_desc":"Les adresses IP des serveurs DNS utilisées pour résoudre les adresses IP des résolveurs DoH/DoT que vous spécifiez comme en amont. Les commentaires ne sont pas autorisés.",
"fallback_dns_title":"Serveurs DNS de repli",
"fallback_dns_desc":"Liste des serveurs DNS de repli utilisés lorsque les serveurs DNS en amont ne répondent pas. La syntaxe est la même que dans le champ principal en amont ci-dessus.",
"fallback_dns_placeholder":"Saisissez un serveur DNS de repli par ligne",
"local_ptr_title":"Serveurs DNS privés inverses",
"local_ptr_desc":"Les serveurs DNS que AdGuard Home utilise pour les requêtes PTR locales. Ces serveurs sont utilisés pour résoudre les noms d'hôte des clients avec des adresses IP privées, par exemple « 192.168.12.34 », en utilisant le DNS inversé. Si ce paramètre n'est pas défini, AdGuard Home utilise les adresses des résolveurs DNS par défaut de votre système d'exploitation, à l'exception des adresses d'AdGuard Home lui-même.",
"local_ptr_desc":"Les serveurs DNS utilisés par AdGuard Home pour les requêtes privées PTR, SOA et NS. Une requête est considérée privée si elle demande un domaine ARPA contenant un sous-réseau entre les plages IP privées (par exemple \"192.168.12.34\") et provient d'un client avec une adresse IP privée. Sans réglages additionnels, les résolveurs DNS par défaut de votre système d'exploitation seront utilisés, sauf pour les adresses IP d'AdGuard Home.",
"local_ptr_default_resolver":"Par défaut, AdGuard Home utilise les résolveurs DNS inversés suivants : {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home n'a pas pu déterminer de résolveurs DNS inversés privés appropriés pour ce système.",
"local_ptr_placeholder":"Saisissez une adresse IP par ligne",
"resolve_clients_title":"Activer la résolution inverse des adresses IP des clients",
"resolve_clients_desc":"Résoudre inversement les adresses IP des clients en leurs noms d'hôtes en envoyant des requêtes PTR aux résolveurs correspondants (serveurs DNS privés pour les clients locaux, serveurs en amont pour les clients ayant une adresse IP publique).",
"use_private_ptr_resolvers_title":"Utiliser des résolveurs DNS inversés privés",
"use_private_ptr_resolvers_desc":"Effectuer des recherches DNS inversées pour les adresses servies localement en utilisant ces serveurs en amont. S'il est désactivé, AdGuard Home répond avec NXDOMAIN à toutes les requêtes PTR de ce type, sauf pour les clients connus par DHCP, /etc/hosts, etc.",
"use_private_ptr_resolvers_desc":"Résolvez les requêtes PTR, SOA et NS pour les domaines ARPA contenant des adresses IP privées par aide des serveurs privés en amont, DHCP, /etc/hosts, etc. S'il est désactivé, AdGuard Home répondra à toutes ces requêtes avec NXDOMAIN.",
"check_dhcp_servers":"Rechercher les serveurs DHCP",
"save_config":"Sauvegarder la configuration",
"enabled_dhcp":"Serveur DHCP activé",
@@ -154,7 +154,7 @@
"use_adguard_parental":"Utiliser le contrôle parental d'AdGuard",
"use_adguard_parental_hint":"AdGuard Home va vérifier s'il y a du contenu pour adultes sur le domaine. Ce sera fait par aide du même API discret que celui utilisé par le service de Sécurité de navigation.",
"enforce_safe_search":"Utiliser la Recherche Sécurisée",
"enforce_save_search_hint":"AdGuard Home appliquera la recherche sécurisée dans les moteurs de recherche suivants : Google, YouTube, Bing, DuckDuckGo, Yandex, Pixabay.",
"enforce_save_search_hint":"AdGuard Home appliquera la recherche sécurisée dans les moteurs de recherche suivants : Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay.",
"no_servers_specified":"Pas de serveurs spécifiés",
"general_settings":"Paramètres généraux",
"dns_settings":"Paramètres DNS",
@@ -294,6 +294,9 @@
"blocked_response_ttl":"Réponse bloquée TTL",
"blocked_response_ttl_desc":"Spécifie pendant combien de secondes les clients doivent mettre en cache une réponse filtrée",
"form_enter_blocked_response_ttl":"Saisir le TTL de la réponse bloquée (secondes)",
"upstream_timeout":"Délai d'attente en amont",
"upstream_timeout_desc":"Spécifie le nombre de secondes à attendre pour une réponse du serveur en amont",
"form_enter_upstream_timeout":"Saisir le délai d'attente du serveur en amont en secondes",
"dnscrypt":"DNSCrypt",
"dns_over_https":"DNS-over-HTTPS",
"dns_over_tls":"DNS-over-TLS",
@@ -598,7 +601,7 @@
"disable_ipv6":"Désactiver la résolution des adresses IPv6",
"disable_ipv6_desc":"Supprimer toutes les requêtes DNS pour les adresses IPv6 (type AAAA) et supprimer les indices IPv6 des réponses HTTPS.",
"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.",
"fastest_addr_desc":"Attente les réponses de <b>tous</b> les serveurs DNS, mesure de la vitesse de connexion TCP pour chaque serveur et renvoi de l'adresse IP du serveur avec la vitesse de connexion la plus rapide.<br/>Ce mode peut considérablement ralentir les requêtes DNS, si un ou plusieurs serveurs en amont ne répondent pas. Assurez-vous que vos serveurs en amont sont stables et que votre délai dépassé en amont est faible.",
"autofix_warning_text":"Si vous cliquez sur « Réparer », AdGuard Home configurera votre système pour utiliser le serveur DNS AdGuard Home.",
"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.",
@@ -676,7 +679,7 @@
"filter_allowlist":"ATTENTION: Cette action exclura également la règle « {{disallowed_rule}} » de la liste des clients autorisés.",
"last_rule_in_allowlist":"Impossible d’interdire ce client, car l’exclusion de la règle « {{disallowed_rule}} » DÉSACTIVERA la liste des « clients autorisés ».",
"use_saved_key":"Utiliser la clef précédemment enregistrée",
"parental_control":"Contrôle parental",
"parental_control":"Contrôle Parental",
"safe_browsing":"Navigation sécurisée",
"served_from_cache_label":"Servi depuis le cache",
"form_error_password_length":"Le mot de passe doit comporter entre {{min}} et {{max}} caractères",
"fallback_dns_desc":"Popis rezervnih DNS poslužitelja koji se koriste kada uzvodni DNS poslužitelji ne odgovaraju. Sintaksa je ista kao u gornjem polju glavnog uzvodnog toka.",
"fallback_dns_placeholder":"Unesite jedan rezervni DNS poslužitelj po retku",
"local_ptr_title":"Privatni obrnuti DNS poslužitelji",
"local_ptr_desc":"DNS poslužitelji koje AdGuard Home koristi za lokalne PTR upite. Ti se poslužitelji koriste za razrješavanje naziva glavnog računala klijenata s privatnim IP adresama, na primjer \"192.168.12.34\", koristeći obrnuti DNS. Ako nije postavljeno, AdGuard Home koristi adrese zadanih DNS razrješivača vašeg OS-a, osim za adrese samog AdGuard Homea.",
"local_ptr_desc":"DNS poslužitelji koje koristi AdGuard Home za privatne PTR, SOA i NS zahtjeve. Zahtjev se smatra privatnim ako traži ARPA domenu koja sadrži podmrežu unutar privatnih IP raspona (kao što je \"192.168.12.34\") i dolazi od klijenta s privatnom IP adresom. Ako nije postavljeno, koristit će se zadani DNS rezolveri vašeg OS-a, osim za AdGuard Home IP adrese.",
"local_ptr_default_resolver":"Prema zadanim postavkama AdGuard Home koristi sljedeće obrnute DNS razrješivače: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home nije mogao odrediti prikladne privatne obrnute DNS razrješivače za ovaj sustav.",
"local_ptr_placeholder":"Unesite jednu adresu poslužitelja po retku",
"resolve_clients_title":"Omogući obrnuto rješavanje IP adresa klijenata",
"resolve_clients_desc":"Obrnuto razriješite IP adrese klijenata u nazive glavnih računala slanjem PTR upita odgovarajućim razrješivačima (privatni DNS poslužitelji za lokalne klijente, uzvodni poslužitelji za klijente s javnim IP adresama).",
"use_private_ptr_resolvers_title":"Koristi privatne reverzne DNS razrješivače",
"use_private_ptr_resolvers_desc":"Izvršite obrnuta DNS traženja za lokalno poslužene adrese pomoću ovih uzlaznih poslužitelja. Ako je onemogućen, AdGuard Home odgovara S NXDOMAIN-om na sve takve PTR zahtjeve osim za klijente poznate iz DHCP-a, /etc/hosts i tako dalje.",
"use_private_ptr_resolvers_desc":"Razriješi PTR, SOA i NS zahtjeve za ARPA domene koje sadrže privatne IP adrese putem privatnih uzvodnih poslužitelja, DHCP-a, /etc/hostova itd. Ako je onemogućeno, AdGuard Home će na sve takve zahtjeve odgovoriti s NXDOMAIN.",
"encryption_plain_dns_desc":"Obični DNS je omogućen prema zadanim postavkama. Možete ga onemogućiti kako biste prisilili sve uređaje da koriste šifrirani DNS. Da biste to učinili, morate omogućiti barem jedan kriptirani DNS protokol",
"encryption_plain_dns_error":"Da biste onemogućili obični DNS, omogućite barem jedan kriptirani DNS protokol",
"topline_expiring_certificate":"Vaš SSL certifikat uskoro ističe. Ažurirajte <0>Postavke šifriranja</0>.",
"topline_expired_certificate":"Vaš SSL certifikat je istekao. Ažurirajte <0>Postavke šifriranja</0>.",
"form_error_port_range":"Unesite broj porta od 80 do 65536",
@@ -675,7 +678,7 @@
"use_saved_key":"Korištenje prethodno spremljenog ključa",
"parental_control":"Roditeljska zaštita",
"safe_browsing":"Sigurno surfanje",
"served_from_cache":"{{value}} <i>(dohvaćeno iz predmemorije)</i>",
"served_from_cache_label":"Posluženo iz predmemorije",
"form_error_password_length":"Lozinka mora sadržavati od {{min}} do {{max}} znakova",
"anonymizer_notification":"<0>Napomena:</0>IP anonimizacija je omogućena. Možete ju onemogućiti u <1>općim postavkama</1>.",
"confirm_dns_cache_clear":"Jeste li sigurni da želite očistiti DNS predmemoriju?",
"example_multiple_upstreams_reserved":"beberapa hulu <0>untuk domain tertentu</0>;",
"example_upstream_comment":"komentar.",
"upstream_parallel":"Gunakan kueri paralel untuk mempercepat resoluasi dengan menanyakan semua server upstream secara bersamaan",
"upstream_parallel":"Gunakan kueri paralel untuk mempercepat penyelesaian dengan mengkueri seluruh server hulu secara bersamaan.",
"parallel_requests":"Permintaan paralel",
"load_balancing":"Penyeimbang beban",
"load_balancing_desc":"Permintaan satu server pada satu waktu. AdGuard Home akan menggunakan algoritma acak tertimbang untuk memilih server sehingga server tercepat akan lebih sering digunakan.",
"bootstrap_dns":"Server DNS bootstrap",
"bootstrap_dns_desc":"Alamat IP server DNS yang digunakan untuk menyelesaikan alamat IP resolver DoH/DoT yang Anda tentukan sebagai upstream. Komentar tidak diizinkan.",
"bootstrap_dns_desc":"Alamat IP server DNS yang digunakan untuk menyelesaikan alamat IP penyelesai DoH/DoT yang Anda tentukan sebagai hulu. Tidak diizinkan untuk berkomentar.",
"fallback_dns_title":"Server DNS cadangan",
"fallback_dns_desc":"Daftar server DNS cadangan yang digunakan ketika server hulu DNS tidak merespons. Sintaksnya sama dengan kolom hulu utama di atas.",
"fallback_dns_placeholder":"Masukkan satu server DNS cadangan per baris",
"local_ptr_title":"Server pembalik DNS pribadi",
"local_ptr_desc":"Server DNS yang digunakan AdGuard Home untuk kueri PTR lokal. Server ini digunakan untuk menyelesaikan nama host klien dengan alamat IP pribadi, misalnya \"192.168.12.34\", menggunakan DNS terbalik. Jika tidak disetel, AdGuard Home menggunakan alamat resolver DNS default OS Anda kecuali untuk alamat AdGuard Home itu sendiri.",
"local_ptr_desc":"Server DNS yang digunakan oleh AdGuard Home untuk permintaan PTR, SOA, dan NS pribadi. Permintaan dianggap pribadi jika meminta domain ARPA yang berisi subnet dalam rentang IP pribadi (seperti \"192.168.12.34\") dan berasal dari klien dengan alamat IP pribadi. Jika tidak ditetapkan, standar pemecah DNS milik OS Anda akan digunakan, kecuali untuk alamat IP AdGuard Home.",
"local_ptr_default_resolver":"Secara bawaan, AdGuard Home menggunakan pemecah DNS terbalik: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home tidak dapat menentukan pemecah DNS terbalik yang sesuai untuk sistem ini.",
"local_ptr_placeholder":"Masukkan satu alamat IP per baris",
"resolve_clients_desc":"Menyelesaikan alamat IP klien secara terbalik ke nama host mereka dengan mengirimkan kueri PTR ke resolver yang sesuai (server DNS pribadi untuk klien lokal, server upstream untuk klien dengan alamat IP publik).",
"resolve_clients_desc":"Selesaikan alamat IP klien secara terbalik ke dalam nama host mereka dengan mengirimkan kueri PTR ke penyelesai yang sesuai (server DNS pribadi untuk klien lokal, server hulu untuk klien dengan alamat IP publik).",
"use_private_ptr_resolvers_title":"Gunakan server pembalik DNS pribadi",
"use_private_ptr_resolvers_desc":"Lakukan pencarian DNS terbalik untuk alamat yang disajikan secara lokal menggunakan server hulu ini. Jika dinonaktifkan, Adguard Home merespons dengan NXDOMAIN untuk semua permintaan PTR tersebut kecuali untuk klien yang diketahui dari DHCP, /etc/hosts, dan seterusnya.",
"use_private_ptr_resolvers_desc":"Menyelesaikan permintaan PTR, SOA, dan NS untuk domain ARPA yang berisi alamat IP pribadi melalui server hulu pribadi, DHCP, /etc/hosts, dll. Jika dinonaktifkan, AdGuard Home akan merespons semua permintaan tersebut dengan NXDOMAIN.",
"check_dhcp_servers":"Cek untuk server DHCP",
"save_config":"Simpan pengaturan",
"enabled_dhcp":"Server DHCP diaktifkan",
@@ -49,12 +49,12 @@
"form_error_server_name":"Nama server tidak valid",
"form_error_subnet":"Subnet \"{{cidr}}\" tidak berisi alamat IP \"{{ip}}\"",
"form_error_positive":"Harus lebih dari 0",
"form_error_gateway_ip":"Sewa tidak dapat memiliki alamat IP gateway",
"form_error_gateway_ip":"Lease tidak dapat memiliki gerbang alamat IP",
"out_of_range_error":"Harus di luar rentang \"{{start}}\"-\"{{end}}\"",
"lower_range_start_error":"Harus lebih rendah dari rentang awal",
"greater_range_start_error":"Harus lebih besar dari rentang awal",
"subnet_error":"Alamat harus dalam satu subnet",
"gateway_or_subnet_invalid":"Subnet mask tidak valid",
"gateway_or_subnet_invalid":"Subnet samaran tidak valid",
"dhcp_form_gateway_input":"IP gateway",
"dhcp_form_subnet_input":"Subnet mask",
"dhcp_form_range_title":"Rentang alamat IP",
@@ -132,8 +132,8 @@
"top_clients":"Klien teratas",
"no_clients_found":"Tidak ditemukan klien",
"general_statistics":"Statistik umum",
"top_upstreams":"Top servers upstream",
"no_upstreams_data_found":"Tidak ada data server upstream yang ditemukan",
"top_upstreams":"Hulu teratas",
"no_upstreams_data_found":"Tidak ada data hulu yang ditemukan",
"number_of_dns_query_days":"Jumlah kueri DNS diproses selama {{value}} hari terakhir",
"number_of_dns_query_days_plural":"Jumlah kueri DNS yang diproses selama {{count}} hari terakhir",
"number_of_dns_query_hours":"Jumlah kueri DNS diproses selama {{{count}} jam terakhir",
@@ -147,14 +147,14 @@
"average_upstream_response_time":"Rata-rata waktu respons hulu",
"response_time":"Waktu respons",
"average_processing_time_hint":"Rata-rata waktu dalam milidetik untuk pemrosesan sebuah permintaan DNS",
"block_domain_use_filters_and_hosts":"Blokir domain menggunakan filter dan file hosts",
"block_domain_use_filters_and_hosts":"Blokir domain menggunakan filter dan berkas host",
"filters_block_toggle_hint":"Anda dapat menyiapkan aturan pemblokiran dalam pengaturan <a>Filter</a>.",
"use_adguard_browsing_sec":"Gunakan layanan web Keamanan Penjelajahan AdGuard",
"use_adguard_browsing_sec_hint":"AdGuard Home akan memeriksa apakah domain diblokir oleh layanan web keamanan penjelajahan. Ini akan menggunakan API pencarian yang ramah privasi untuk melakukan pemeriksaan: hanya awalan singkat dari hash nama domain SHA256 yang dikirim ke server.",
"use_adguard_parental":"Gunakan layanan web kontrol orang tua AdGuard",
"use_adguard_parental_hint":"AdGuard Home akan mengecek jika domain mengandung materi dewasa. Akan menggunakan API yang ramah privasi yang sama sebagai layanan web keamanan penjelajahan.",
"enforce_safe_search":"Pakai pencarian aman",
"enforce_save_search_hint":"AdGuard Home dapat memaksa penelusuran aman pada mesin pencari berikut: Google, Youtube, Bing, DuckDuckGo, Yandex, dan Pixabay.",
"enforce_save_search_hint":"AdGuard Home akan memberlakukan pencarian yang aman di mesin pencari berikut ini: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay.",
"no_servers_specified":"Sever tidak disebutkan",
"general_settings":"Pengaturan umum",
"dns_settings":"Pengaturan DNS",
@@ -169,8 +169,8 @@
"upstream_dns_help":"Masukkan satu alamat server per baris. <a>Pelajari lebih lanjut</a> mengenai cara mengonfigurasi server DNS hulu.",
"upstream_dns_configured_in_file":"Diatur dalam {{path}}",
"example_upstream_sdns":"<0>Stempel DNS</0> untuk <1>DNSCrypt</1> atau pengarah <2>DNS melalui HTTPS</2>;",
"example_upstream_tcp":"DNS biasa (melalui TCP);",
"example_upstream_tcp_port":"DNS biasa (melalui TCP, dengan port);",
"example_upstream_tcp_hostname":"DNS biasa (lebih dari TCP, nama host);",
"example_upstream_tcp_hostname":"DNS biasa (melalui TCP, nama host);",
"all_lists_up_to_date_toast":"Semua daftar sudah diperbarui",
"updated_upstream_dns_toast":"Server upstream berhasil disimpan",
"updated_upstream_dns_toast":"Server hulu berhasil disimpan",
"dns_test_ok_toast":"Server DNS yang ditentukan bekerja dengan benar",
"dns_test_not_ok_toast":"Server \"{{key}}\": tidak dapat digunakan, mohon cek bahwa Anda telah menulisnya dengan benar",
"dns_test_parsing_error_toast":"Bagian {{section}}: baris {{line}}: tidak dapat digunakan, mohon cek bahwa Anda telah menulisnya dengan benar",
"dns_test_warning_toast":"Upstream \"{{key}}\" tidak menanggapi permintaan pengujian dan mungkin tidak berfungsi dengan baik",
"dns_test_warning_toast":"Hulu \"{{key}}\" tidak menanggapi permintaan pengujian dan mungkin tidak berfungsi dengan benar",
"unblock":"Buka Blokir",
"block":"Blok",
"disallow_this_client":"Cabut ijin untuk klien ini",
@@ -268,18 +268,18 @@
"rule_added_to_custom_filtering_toast":"Aturan ditambah ke aturan penyaringan khusus: {{rule}}",
"query_log_response_status":"Status: {{value}}",
"query_log_filtered":"Difilter oleh {{filter}}",
"query_log_confirm_clear":"Apakah Anda yakin ingin menghapus seluruh kueri log?",
"query_log_cleared":"Kueri log telah berhasil dihapus",
"query_log_updated":"Log permintaan telah berhasil diperbarui",
"query_log_clear":"Hapus kueri log",
"query_log_confirm_clear":"Apakah Anda yakin ingin menghapus seluruh catatan kueri?",
"query_log_cleared":"Catatan kueri berhasil dihapus",
"query_log_updated":"Catatan kueri berhasil diperbarui",
"query_log_clear":"Hapus catatan kueri",
"query_log_retention":"Rotasi kueri log",
"query_log_enable":"Aktifkan log",
"query_log_configuration":"Konfigurasi log",
"query_log_disabled":"Kueri log dinonaktifkan dan dapat dikonfigurasi di <0>pengaturan</0>",
"query_log_enable":"Aktifkan catatan",
"query_log_configuration":"Konfigurasi catatan",
"query_log_disabled":"Catatan kueri dinonaktifkan dan dapat dikonfigurasi di <0>pengaturan</0>",
"query_log_strict_search":"Gunakan tanda kutip ganda untuk pencarian ketat",
"query_log_retention_confirm":"Apakah Anda yakin ingin mengubah rotasi kueri log? Jika Anda menurunkan nilai interval, beberapa data akan hilang",
"anonymize_client_ip":"Anonim IP klien",
"anonymize_client_ip_desc":"Jangan simpan alamat lengkap IP klien dalam log dan statistik",
"anonymize_client_ip_desc":"Jangan simpan alamat lengkap IP klien dalam catatan atau statistik",
"dns_config":"Konfigurasi server DNS",
"dns_cache_config":"Konfigurasi cache DNS",
"dns_cache_config_desc":"Disini Anda bisa mengonfigurasi cache DNS",
@@ -308,8 +308,8 @@
"form_enter_rate_limit":"Masukkan batas nilai",
"rate_limit":"Batas nilai",
"edns_enable":"Aktifkan EDNS Klien Subnet",
"edns_cs_desc":"Tambahkan opsi EDNS Client Subnet (ECS) ke permintaan upstream dan catat nilai yang dikirim oleh klien di log kueri.",
"edns_use_custom_ip":"Gunakan IP khusus untuk EDNS",
"edns_cs_desc":"Tambahkan opsi EDNS Client Subnet (ECS) ke permintaan hulu dan catat nilai yang dikirim oleh klien dalam catatan kueri.",
"edns_use_custom_ip":"Gunakan IP kustom untuk EDNS",
"edns_use_custom_ip_desc":"Izinkan untuk menggunakan IP kustom untuk EDNS",
"rate_limit_desc":"Jumlah permintaan per detik yang diperbolehkan untuk satu klien. Atur ke 0 untuk tidak terbatas.",
"rate_limit_subnet_len_ipv4":"Panjang awalan subnet untuk alamat IPv4",
@@ -329,13 +329,13 @@
"blocking_mode_nxdomain":"NXDOMAIN: Respon pakai kode NXDOMAIN",
"blocking_mode_null_ip":"Null IP: Respon pakai alamat IP kosong (0.0.0.0 untuk A; :: untuk AAAA)",
"blocking_mode_custom_ip":"IP kustom: respon dengan alamat IP yang diset secara manual",
"theme_auto":"Auto",
"theme_auto":"Otomatis",
"theme_light":"Terang",
"theme_dark":"Gelap",
"upstream_dns_client_desc":"Jika Anda biarkan kolom ini kosong, AdGuard Home akan menggunakan server yang dikonfigurasi di <0>pengaturan DNS</0>.",
"tracker_source":"Sumber pelacak",
"source_label":"Sumber",
"found_in_known_domain_db":"Ditemukan di database domain dikenal",
"found_in_known_domain_db":"Ditemukan di basis data domain yang dikenal.",
"category_label":"Kategori",
"rule_label":"Atura(n)",
"list_label":"Daftar",
@@ -366,18 +366,18 @@
"install_devices_router":"Router",
"install_devices_router_desc":"Penyiapan ini secara otomatis mencakup semua perangkat yang terhubung ke router rumah Anda, tidak perlu mengkonfigurasi masing-masing perangkat secara manual.",
"install_devices_address":"Server DNS AdGuard Home akan menggunakan alamat berikut",
"install_devices_router_list_1":"Buka preferensi untuk router Anda. Biasanya, Anda dapat mengaksesnya dari browser Anda melalui URL, seperti http://192.168.0.1/ atau http://192.168.1.1/. Anda mungkin diminta untuk memasukkan kata sandi. Jika Anda tidak mengingatnya, Anda sering kali dapat mengatur ulang kata sandi dengan menekan tombol pada perute itu sendiri, tetapi perlu diketahui bahwa jika prosedur ini dipilih, Anda mungkin akan kehilangan seluruh konfigurasi perute. Jika router Anda memerlukan aplikasi untuk menyiapkannya, instal aplikasi tersebut di ponsel atau PC Anda dan gunakan untuk mengakses pengaturan router.",
"install_devices_router_list_1":"Buka preferensi untuk router Anda. Biasanya, Anda dapat mengaksesnya dari peramban Anda melalui URL, seperti http://192.168.0.1/ atau http://192.168.1.1/. Anda mungkin diminta untuk memasukkan kata sandi. Jika Anda tidak mengingatnya, Anda sering kali dapat mengatur ulang kata sandi dengan menekan tombol pada router itu sendiri, tetapi perlu diketahui bahwa jika prosedur ini dipilih, Anda mungkin akan kehilangan seluruh konfigurasi router. Jika router Anda memerlukan aplikasi untuk menyiapkannya, pasang aplikasi tersebut di ponsel atau PC Anda dan gunakan untuk mengakses pengaturan router.",
"install_devices_router_list_2":"Temukan pengaturan DHCP / DNS. Cari huruf DNS di sebelah kolom yang memungkinkan dua atau tiga set angka, masing-masing dipecah menjadi empat kelompok dengan satu hingga tiga digit.",
"install_devices_router_list_3":"Masukkan alamat server AdGuard Home disana",
"install_devices_router_list_4":"Anda tidak dapat menyetel server DNS kustom pada beberapa tipe router. Dalam hal ini mungkin membantu jika Anda mengatur AdGuard Home sebagai <0>server DHCP</0>. Jika tidak, Anda harus mencari petunjuk tentang cara mengkustomisasi server DNS untuk model router khusus Anda.",
"install_devices_windows_list_1":"Buka Panel Kontrol melalui menu Start atau pencarian Windows.",
"install_devices_windows_list_2":"Masuk ke kategori Jaringan dan Internet (Network and Internet) dan kemudian ke Pusat Jaringan dan Berbagi (Network and Sharing Center).",
"install_devices_windows_list_4":"Klik kanan koneksi aktif Anda dan pilih Properties.",
"install_devices_windows_list_5":"Temukan \"Internet Protocol Version 4 (TCP/IPv4)\" (atau, untuk IPv6, \"Internet Protocol Version 6 (TCP/IPv6)\") dalam daftar, pilih dan kemudian klik Properties lagi.",
"install_devices_windows_list_4":"Klik kanan koneksi aktif Anda dan pilih Properti.",
"install_devices_windows_list_5":"Temukan \"Protokol Internet Versi 4 (TCP/IPv4)\" (atau, untuk IPv6, \"Protokol Internet Versi 6 (TCP/IPv6)\") dalam daftar, pilih dan kemudian klik Properti lagi.",
"install_devices_windows_list_6":"Pilih \"Gunakan alamat server DNS berikut\" dan masukkan alamat server Beranda AdGuard Anda.",
"install_devices_macos_list_1":"Klik ikon Apple dan pergi ke System Preferences.",
"install_devices_macos_list_2":"Klik Network.",
"install_devices_macos_list_1":"Klik ikon Apple dan buka Preferensi Sistem.",
"install_devices_macos_list_2":"Klik Jaringan.",
"install_devices_macos_list_3":"Pilih koneksi pertama dalam daftar dan klik Advanced.",
"install_devices_macos_list_4":"Pilih tab DNS dan masukkan alamat server AdGuard Anda.",
"install_devices_android_list_1":"Dari layar beranda Menu Android, ketuk Pengaturan.",
@@ -394,7 +394,7 @@
"open_dashboard":"Buka Beranda",
"install_saved":"Berhasil disimpan",
"encryption_title":"Enkripsi",
"encryption_desc":"Enkripsi (HTTPS/QUIC/TLS) untuk DNS dan antarmuka admin",
"encryption_desc":"Dukungan enkripsi (HTTPS/QUIC/TLS) untuk DNS dan antarmuka web admin",
"encryption_config_saved":"Pengaturan enkripsi telah tersimpan",
"encryption_server":"Nama server",
"encryption_server_enter":"Masukkan nama domain anda",
@@ -406,7 +406,7 @@
"encryption_dot":"Port DNS-over-TLS",
"encryption_dot_desc":"Jika port ini terkonfigurasi, AdGuard Home akan menjalankan server DNS-over-TLS dalam port ini",
"encryption_doq":"Port DNS-over-QUIC ",
"encryption_doq_desc":"Jika port ini diatur secara sepesifik, AdGuard Home akan menjalankan server DNS-lewat-QUIC pada port ini.",
"encryption_doq_desc":"Jika port ini dikonfigurasi, AdGuard Home akan menjalankan server DNS melalui QUIC pada port ini.",
"encryption_certificates":"Sertifikat",
"encryption_certificates_desc":"Untuk menggunakan enkripsi, Anda perlu memberikan rantai sertifikat SSL yang valid untuk domain Anda. Anda bisa mendapatkan sertifikat gratis di <0>{{link}}</0> atau Anda dapat membelinya dari salah satu Otoritas Sertifikat tepercaya.",
"encryption_certificates_input":"Salin / rekatkan sertifikat PEM yang disandikan di sini.",
@@ -431,8 +431,8 @@
"topline_expiring_certificate":"Sertifikat SSL Anda hampir kedaluwarsa. Perbarui <0>Pengaturan enkripsi</0>.",
"topline_expired_certificate":"Sertifikat SSL Anda kedaluwarsa. Perbarui <0>Pengaturan enkripsi</0>.",
"form_error_port_range":"Masukkan nomor port di kisaran 80-65535",
"form_error_port_unsafe":"Ini adalah port yang tidak aman",
"form_error_equal":"Seharusnya tidak sama",
"form_error_port_unsafe":"Port tidak aman",
"form_error_equal":"Tidak boleh sama",
"form_error_password":"Kata sandi tidak cocok",
"reset_settings":"Setel ulang pengaturan",
"update_announcement":"AdGuard Home {{version}} sekarang tersedia! <0>Klik di sini</0> untuk info lebih lanjut.",
@@ -447,7 +447,7 @@
"update_failed":"Pembaruan otomatis gagal. Silakan <a>ikuti langkah-langkah berikut</a> untuk memperbarui secara manual.",
"manual_update":"Silakan <a>mengikuti langkah berikut</a> untuk memperbarui secara manual.",
"processing_update":"Silahkan tunggu, AdGuard Home sedang diperbarui",
"clients_title":"Klien yang gigih",
"clients_title":"Klien persisten",
"clients_desc":"Konfigurasikan catatan klien persisten untuk perangkat yang terhubung ke AdGuard Home",
"settings_global":"Global",
"settings_custom":"Kustom",
@@ -459,7 +459,7 @@
"client_edit":"Ubah Klien",
"client_identifier":"Identifikasi",
"ip_address":"Alamat IP",
"client_identifier_desc":"Klien dapat diidentifikasi oleh alamat IP, CIDR, alamat MAC atau ClientID (dapat digunakan untuk DoT/DoH/DoQ). <0>Di sini</0> Anda dapat mempelajari lebih lanjut tentang cara mengidentifikasi klien.",
"client_identifier_desc":"Klien dapat diidentifikasi berdasarkan alamat IP, CIDR, alamat MAC, atau ClientID (dapat digunakan untuk DoT/DoH/DoQ). Pelajari lebih lanjut tentang cara mengidentifikasi klien <0>di sini</0>.",
"form_enter_ip":"Masukkan IP",
"form_enter_subnet_ip":"Masukkan alamat IP di subnet \"{{cidr}}\"",
"form_enter_mac":"Masukkan MAC",
@@ -475,8 +475,8 @@
"clients_not_found":"Tidak ada klien ditemukan",
"client_confirm_delete":"Apakah anda yakin ingin menghapus klien \"{{key}}\"?",
"list_confirm_delete":"Anda yakin ingin menghapus daftar ini?",
"auto_clients_title":"Klien (waktu berjalan)",
"auto_clients_desc":"Informasi tentang alamat IP perangkat yang menggunakan atau mungkin menggunakan AdGuard Home. Informasi ini dikumpulkan dari beberapa sumber, termasuk file host, reverse DNS, dll.",
"auto_clients_title":"Klien runtime",
"auto_clients_desc":"Informasi tentang alamat IP perangkat yang menggunakan atau mungkin menggunakan AdGuard Home. Informasi ini dikumpulkan dari beberapa sumber, termasuk berkas host, DNS terbalik, dll.",
"access_title":"Pengaturan akses",
"access_desc":"Disini anda dapat mengatur aturan akses untuk server AdGuard Home DNS",
"access_allowed_title":"Klien yang diizinkan",
@@ -484,9 +484,9 @@
"access_disallowed_title":"Klien yang tidak diizinkan",
"access_disallowed_desc":"Daftar CIDR, alamat IP, atau <a>ClientID</a>. Jika daftar ini memiliki entri, AdGuard Home akan membatalkan permintaan dari klien ini. Kolom ini diabaikan jika ada entri di daftar putih klien.",
"access_blocked_title":"Domain yang diblokir",
"access_blocked_desc":"Jangan bingung dengan filter. AdGuard Home menghapus kueri DNS yang cocok dengan domain ini, dan kueri ini bahkan tidak muncul di log kueri. Anda dapat menentukan nama domain, karakter pengganti, atau aturan filter URL yang tepat, mis. \"example.org\", \"*.example.org\", atau \"||example.org^\" yang sesuai.",
"access_blocked_desc":"Jangan dikelirukan dengan filter. AdGuard Home membuang kueri DNS yang cocok dengan domain ini, dan kueri ini bahkan tidak muncul di catatan kueri. Anda dapat menentukan nama domain, karakter pengganti, atau aturan filter URL yang tepat, misalnya \"example.org\", \"*.example.org\", atau \"||example.org^\" secara bersamaan.",
"access_settings_saved":"Pengaturan akses berhasil disimpan",
"updates_checked":"Versi baru AdGuard Home tersedia\n",
"updates_checked":"Versi baru AdGuard Home tersedia",
"updates_version_equal":"AdGuard Home sudah tebaru",
"check_updates_now":"Periksa pembaruan sekarang",
"version_request_error":"Pemeriksaan pembaruan gagal. Harap periksa koneksi internet anda.",
@@ -494,7 +494,7 @@
"setup_dns_privacy_1":"<0>DNS melalui TLS:</0> Gunakan <1>{{address}}</1> string.",
"setup_dns_privacy_2":"<0>DNS-over-TLS:</0> Memakai <1>{{address}}</1> string.",
"setup_dns_privacy_3":"<0>Berikut daftar perangkat lunak yang dapat Anda gunakan.</0>",
"setup_dns_privacy_4":"Di perangkat iOS 14 atau macOS Big Sur, Anda dapat mengunduh file '.mobileconfig' khusus yang menambahkan server <highlight>DNS-over-HTTPS</highlight> atau <highlight>DNS-over-TLS</highlight> ke pengaturan DNS.",
"setup_dns_privacy_4":"Pada perangkat iOS 14 atau macOS Big Sur, Anda dapat mengunduh berkas khusus '.mobileconfig' yang menambahkan server <highlight>DNS melalui HTTPS</highlight> atau <highlight>DNS melalui TLS</highlight> ke pengaturan DNS.",
"setup_dns_privacy_android_1":"Android 9 mendukung DNS-over-TLS secara asli. Untuk mengkonfigurasinya, buka Pengaturan → Jaringan & internet → Tingkat Lanjut → DNS Pribadi dan masukkan nama domain Anda di sana.",
"setup_dns_privacy_android_2":"<0>AdGuard untuk Android</0> mendukung <1>DNS-over-HTTPS</1> dan <1>DNS-over-TLS</1>.",
"setup_dns_privacy_android_3":"<0>Intra</0> menambahkan dukungan <1>DNS-over-HTTPS</1> untuk Android.",
@@ -517,7 +517,7 @@
"rewrite_confirm_delete":"Apakah anda yakin ingin menghapus DNS rewrite untuk \"{{key}}\"?",
"rewrite_desc":"Memungkinkan untuk dengan mudah mengkonfigurasi respons DNS kustom untuk nama domain tertentu.",
"rewrite_applied":"Aturan Rewrite yang diterapkan",
"rewrite_hosts_applied":"Ditulis ulang oleh aturan file hosts",
"rewrite_hosts_applied":"Ditulis ulang oleh aturan berkas host",
"dns_rewrites":"DNS rewrite",
"form_domain":"Masukkan nama domain",
"form_answer":"Masaukan alamat IP atau nama domain",
@@ -563,7 +563,7 @@
"ignore_domains":"Domain yang diabaikan (dipisahkan oleh baris baru)",
"ignore_domains_title":"Domain yang diabaikan",
"ignore_domains_desc_stats":"Kueri yang cocok dengan aturan ini tidak ditulis ke statistik",
"ignore_domains_desc_query":"Kueri yang cocok dengan aturan ini tidak ditulis ke log kueri",
"ignore_domains_desc_query":"Kueri yang cocok dengan aturan ini tidak ditulis ke catatan kueri",
"interval_hours":"{{count}} jam",
"interval_hours_plural":"{{count}} jam",
"filters_configuration":"Konfigurasi filter",
@@ -593,8 +593,8 @@
"example_rewrite_wildcard":"tulis ulang respon untuk semua subdomain <0>contoh.org</0>.",
"rewrite_ip_address":"Alamat IP: pakai IP ini dalam respons A atau AAAA",
"rewrite_domain_name":"Nama domain: tambah ke rekaman CNAME",
"rewrite_A":"<0>A</0>: nilai khusus, biarkan <0>A</0> merekam dari upstream",
"rewrite_AAAA":"<0>AAAA</0>: nilai khusus, biarkan <0>AAAA</0> merekam dari upstream",
"rewrite_A":"<0>A</0>: nilai khusus, biarkan <0>A</0> merekam dari hulu",
"rewrite_AAAA":"<0>AAAA</0>: nilai khusus, biarkan <0>AAAA</0> merekam dari hulu",
"cache_ttl_min_override_desc":"Perpanjang nilai waktu untuk hidup (detik) yang diterima dari server hulu saat menyimpan respons DNS.",
"cache_ttl_max_override_desc":"Tetapkan nilai waktu-online maksimum (detik) untuk entri di cache DNS.",
"cache_ttl_min_override_desc":"Perpanjang nilai time-to-live (detik) yang diterima dari server hulu saat menyimpan respons DNS.",
"cache_ttl_max_override_desc":"Tetapkan nilai maksimum time-to-live (detik) untuk entri dalam cache DNS.",
"ttl_cache_validation":"Nilai TTL cache minimum harus kurang dari atau sama dengan nilai maksimum",
"cache_optimistic":"Caching yang optimis",
"cache_optimistic_desc":"Buat AdGuard Home merespons dari cache bahkan ketika entri telah kedaluwarsa dan juga mencoba untuk menyegarkannya.",
@@ -676,9 +676,9 @@
"filter_allowlist":"PERINGATAN: Tindakan ini juga akan mengecualikan aturan \"{{disallowed_rule}}\" dari daftar klien yang diizinkan.",
"last_rule_in_allowlist":"Tidak dapat melarang klien ini karena mengecualikan aturan \"{{disallowed_rule}}\" akan MENONAKTIFKAN daftar \"Klien yang diizinkan\".",
"use_saved_key":"Gunakan kunci yang disimpan sebelumnya",
"parental_control":"Kontrol Orang Tua",
"parental_control":"Pengawasan Orang Tua",
"safe_browsing":"Penjelajahan Aman",
"served_from_cache":"{{value}} <i>(disajikan dari cache)</i>",
"served_from_cache_label":"Disajikan dari cache",
"form_error_password_length":"Kata sandi harus terdiri dari {{min}} hingga {{max}}",
"anonymizer_notification":"<0>Catatan:</0> Anonimisasi IP diaktifkan. Anda dapat menonaktifkannya di <1>Pengaturan umum</1> .",
"confirm_dns_cache_clear":"Apakah Anda yakin ingin menghapus cache DNS?",
@@ -688,11 +688,11 @@
"theme_auto_desc":"Otomatis (berdasarkan skema warna perangkat anda)",
"upstream_parallel":"Utilizza richieste parallele per accelerare la risoluzione interrogando simultaneamente tutti i server upstream.",
"parallel_requests":"Richieste parallele",
"load_balancing":"Bilanciamento del carico",
"load_balancing_desc":"Interroga un server upstream per volta.AdGuard Home utilizzerà un algoritmo casuale ponderato per la selezione del server, in maniera tale da scegliere spesso il più veloce.",
"load_balancing_desc":"Esegui una query su un server upstream alla volta.<br/>AdGuard Home utilizza un algoritmo casuale ponderato per selezionare i server con il minor numero di ricerche fallite e il tempo medio di ricerca più basso.",
"bootstrap_dns":"Server DNS bootstrap",
"bootstrap_dns_desc":"Indirizzi IP dei server DNS utilizzati per risolvere gli indirizzi IP dei resolver DoH/DoT specificati come upstream. I commenti non sono ammessi.",
"fallback_dns_title":"Server DNS di fallback",
"fallback_dns_desc":"Elenco dei server DNS fallback utilizzati quando i server DNS upstream non rispondono. La sintassi è la stessa del campo principale upstream sopra.",
"fallback_dns_placeholder":"Inserisci un server DNS fallback per riga",
"local_ptr_title":"Server DNS privati inversi",
"local_ptr_desc":"I server DNS che AdGuard Home utilizza per le richieste PTR locali. Questi server vengono utilizzati per risolvere i nomi host dei client con indirizzi IP privati, ad esempio \"192.168.12.34\", utilizzando il DNS inverso. Se non è impostato, AdGuard Home utilizzerà gli indirizzi dei resolutori DNS predefiniti del tuo sistema operativo ad eccezione degli indirizzi di AdGuard Home stesso.",
"local_ptr_desc":"I server DNS usati da AdGuard Home per richieste private PTR, SOA e NS. Una richiesta è considerata privata se richiede un dominio ARPA contenente una sottorete all'interno di intervalli IP privati (come \"192.168.12.34\") e proviene da un client con un indirizzo IP privato. Se non impostato, saranno usati i risolutori DNS predefiniti del tuo sistema operativo, ad eccezione degli indirizzi IP di AdGuard Home.",
"local_ptr_default_resolver":"Per impostazione predefinita, AdGuard Home utilizzerà i seguenti risolutori DNS inversi: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home non è stato in grado di determinare i risolutori DNS inversi privati adatti per questo sistema.",
"local_ptr_placeholder":"Inserisci un indirizzo IP per riga",
"resolve_clients_title":"Attiva la risoluzione inversa degli indirizzi IP dei client",
"resolve_clients_desc":"Risolve inversamente gli indirizzi IP dei client nei loro nomi host inviando richieste PTR ai risolutori corrispondenti (server DNS privati per client locali, server upstream per client con indirizzi IP pubblici).",
"use_private_ptr_resolvers_title":"Utilizza dei resolver rDNS privati",
"use_private_ptr_resolvers_desc":"Esegue ricerche DNS inverse per indirizzi locali utilizzando questi server upstream. Se disattivata, AdGuard Home risponderà con NXDOMAIN a tutte le richieste PTR ad eccezione dei client noti da DHCP, /etc/hosts, e così via.",
"use_private_ptr_resolvers_desc":"Risolvi le richieste PTR, SOA e NS per domini ARPA contenenti indirizzi IP privati tramite server upstream privati, DHCP, /etc/hosts, ecc. Se disabilitato, AdGuard Home risponderà a tutte queste richieste con NXDOMAIN.",
"check_dhcp_servers":"Controlla la presenza di server DHCP",
"save_config":"Salva configurazione",
"enabled_dhcp":"Server DHCP attivo",
@@ -154,7 +154,7 @@
"use_adguard_parental":"Utilizza il Controllo Parentale di AdGuard",
"use_adguard_parental_hint":"AdGuard Home verificherà se il dominio contiene materiale per adulti. Utilizza le stesse API privacy-friendly del servizio web 'sicurezza di navigazione'.",
"enforce_safe_search":"Utilizza Ricerca Sicura",
"enforce_save_search_hint":"AdGuard Home forzerà la ricerca sicura sui seguenti motori di ricerca: Google, YouTube, Bing, DuckDuckGo, Yandex, Pixabay.",
"enforce_save_search_hint":"AdGuard Home applicherà la ricerca sicura nei seguenti motori di ricerca: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay.",
"no_servers_specified":"Nessun server specificato",
"general_settings":"Impostazioni generali",
"dns_settings":"Impostazioni DNS",
@@ -294,6 +294,9 @@
"blocked_response_ttl":"Risposta TTL bloccata",
"blocked_response_ttl_desc":"Specifica per quanti secondi i client devono tenere nella cache una risposta filtrata",
"form_enter_blocked_response_ttl":"Inserisci tempo di vita (TTL) della risposta bloccata (secondi)",
"upstream_timeout":"Timeout upstream",
"upstream_timeout_desc":"Specifica il numero di secondi da attendere per una risposta dal server upstream",
"form_enter_upstream_timeout":"Inserisci la durata del timeout del server upstream in secondi",
"install_welcome_title":"Benvenuto nella Home di AdGuard!",
"install_welcome_title":"Benvenuto in AdGuard Home!",
"install_welcome_desc":"AdGuard Home è un server DNS che blocca annunci e tracciatori a livello di rete. Il suo scopo è quello di permetterti il controllo dell'intera rete e di tutti i dispositivi, e non richiede l'utilizzo di un programma lato client.",
"install_settings_title":"Interfaccia Web dell'Admin",
"disable_ipv6_desc":"Eliminare tutte le query DNS per gli indirizzi IPv6 (tipo AAAA) e rimuovere i suggerimenti IPv6 dalle risposte HTTPS.",
"fastest_addr":"Indirizzo IP più veloce",
"fastest_addr_desc":"Interroga tutti i server DNS e restituisci l'indirizzo IP più veloce tra tutte le risposte. Ciò rallenterà le richieste DNS poiché AdGuard Home dovrà attendere le risposte da tutti i server DNS, ma ciò migliorerà complessivamente la connettività.",
"fastest_addr_desc":"Attendi le risposte da <b>tutti i</b> server DNS, misura la velocità di connessione TCP per ogni server e restituisci l'indirizzo IP del server con la velocità di connessione più elevata.<br/>Questa modalità può rallentare notevolmente le query DNS, se uno o più server upstream non rispondono. Assicurati che i tuoi server upstream siano stabili e che il timeout upstream sia basso.",
"autofix_warning_text":"Se fai clic su \"Correggi\", AdGuardHome configurerà il tuo sistema per utilizzare il server DNS AdGuardHome.",
"autofix_warning_list":"Eseguirà queste attività: <0> Disattiva DNSStubListener di sistema </0> <0> Imposta l'indirizzo del server DNS su 127.0.0.1 </0> <0> Sostituisci la destinazione del collegamento simbolico di /etc/resolv.conf su / run / systemd /resolve/resolv.conf </0> <0> Arresta DNSStubListener (ricarica il servizio systemd-resolved) </0>",
"autofix_warning_result":"Di conseguenza, tutte le richieste DNS dal sistema verranno elaborate da AdGuardHome per impostazione predefinita.",
"local_ptr_desc":"AdGuard Home がプライベート PTR、SOA、および NS リクエストに使用するDNSサーバー。プライベートIP 範囲内のサブネット (「192.168.12.34」など) を含む ARPA ドメインを要求し、プライベート IP アドレスを持つクライアントから来たリクエストが、プライベートリクエストとみなされます。本設定が特に指定されていない場合、OSのデフォルトDNSリゾルバ(AdGuard Home の IP アドレスを除く)が使用されます。",
"upstream_parallel":"쿼리 처리 속도를 높이려면 모든 업스트림 서버에서 동시에 병렬 쿼리를 사용해주세요.",
"parallel_requests":"병렬 처리 요청",
"load_balancing":"로드 밸런싱",
"load_balancing_desc":"한 번에 하나의 서버씩 질의합니다. AdGuard Home은 가중 랜덤 알고리즘를 사용해서 가장 빠른 서버가 자주 사용되도록 서버를 선택합니다.",
"load_balancing_desc":"한 번에 하나의 업스트림 서버를 쿼리합니다.<br/>AdGuard Home은 가중 무작위 알고리즘을 사용하여 조회 실패 횟수가 가장 적고 평균 조회 시간이 가장 짧은 서버를 선택합니다.",
"bootstrap_dns":"부트스트랩 DNS 서버",
"bootstrap_dns_desc":"업스트림으로 지정한 DoH/DoT 리졸버의 IP 주소를 확인하는 데 사용되는 DNS 서버의 IP 주소입니다. 주석은 허용되지 않습니다.",
"fallback_dns_title":"폴백 DNS 서버",
"fallback_dns_desc":"업스트림 DNS 서버가 응답하지 않을 때 사용되는 폴백 DNS 서버 목록입니다. 구문은 위의 기본 업스트림 필드와 동일합니다.",
"fallback_dns_placeholder":"한 줄에 하나의 폴백 DNS 서버를 입력하세요.",
"local_ptr_title":"프라이빗 역방향 DNS 서버",
"local_ptr_desc":"AdGuard Home이 로컬 PTR 쿼리에 사용하는 DNS 서버입니다. 이러한 서버는 역방향 DNS를 사용하여 개인 IP 주소(예: '192.168.12.34')가 있는 클라이언트의 호스트 이름을 확인하는 데 사용됩니다. 설정되지 않은 경우, AdGuard Home은 AdGuard Home의 주소를 제외하고 운영 체제의 기본 DNS 리졸버의 주소를 사용합니다.",
"local_ptr_desc":"AdGuard Home에서 비공개 PTR, SOA 및 NS 요청에 사용하는 DNS 서버입니다. 요청이 비공개 IP 범위 내의 서브넷(예: \"192.168.12.34\")을 포함하는 ARPA 도메인을 요청하고 비공개 IP 주소를 가진 클라이언트로부터 오는 경우 비공개로 간주됩니다. 설정하지 않으면 AdGuard Home IP 주소를 제외한 OS의 기본 DNS 리졸버가 사용됩니다.",
"local_ptr_default_resolver":"기본적으로 AdGuard Home에서는 {{ip}} 역방향 DNS 서버를 이용합니다.",
"local_ptr_no_default_resolver":"AdGuard Home에서 이 시스템에 적합한 사설 역방향 프라이빗 DNS 서버를 결정할 수 없습니다.",
"local_ptr_placeholder":"한 줄에 하나씩 IP 주소를 입력하세요.",
"resolve_clients_title":"클라이언트 IP 주소에 대한 호스트명 확인 활성화",
"resolve_clients_desc":"해당 서버에 대한 PTR 쿼리를 통해 클라이언트의 도메인 이름을 정의합니다. (로컬 클라이언트의 경우 프라이빗 DNS 서버, 공용 IP 주소가 있는 클라이언트의 경우 업스트림 서버).",
"use_private_ptr_resolvers_title":"프라이빗 역방향 DNS 리졸버 사용",
"use_private_ptr_resolvers_desc":"업스트림 서버를 사용해 로컬로 제공되는 주소의 역방향 DNS를 조회합니다. 끄는 경우, AdGuard Home은 DHCP, /etc/hosts 등에서 알려진 클라이언트를 제외한 모든 PTR 요청에 NXDOMAIN으로 응답합니다.",
"use_private_ptr_resolvers_desc":"사설 업스트림 서버, DHCP, / etc/hosts 등을 통해 사설 IP 주소가 포함된 ARPA 도메인에 대한 PTR, SOA 및 NS 요청을 처리합니다. 비활성화하면 AdGuard Home은 NXDOMAIN을 사용하여 이러한 모든 요청에 응답합니다.",
"check_dhcp_servers":"DHCP 서버 체크",
"save_config":"구성 저장",
"enabled_dhcp":"DHCP 서버 활성화됨",
@@ -108,7 +108,7 @@
"off":"OFF",
"copyright":"Copyright",
"homepage":"홈페이지",
"report_an_issue":"문제를 보고합니다",
"report_an_issue":"문제 신고",
"privacy_policy":"개인정보취급방침",
"enable_protection":"보호 활성화",
"enabled_protection":"보호 활성화됨",
@@ -154,7 +154,7 @@
"use_adguard_parental":"AdGuard 자녀 보호 웹 서비스 사용",
"use_adguard_parental_hint":"AdGuard Home은 도메인에 성인 자료가 포함되어 있는지 확인합니다. 브라우징 보안 웹 서비스와 동일한 개인정보 보호 API를 사용함.",
"enforce_safe_search":"세이프서치 사용",
"enforce_save_search_hint":"AdGuard Home은 Google, YouTube, Bing, DuckDuckGo, Yandex, Pixabay와 같은 검색 엔진에서 세이프서치를 시행합니다.",
"enforce_save_search_hint":"AdGuard Home은 Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay와 같은 검색 엔진에서 세이프서치를 시행합니다.",
"no_servers_specified":"지정된 서버 없음",
"general_settings":"일반 설정",
"dns_settings":"DNS 설정",
@@ -294,6 +294,9 @@
"blocked_response_ttl":"차단된 TTL 응답",
"blocked_response_ttl_desc":"클라이언트가 필터링된 응답을 캐시해야 하는 시간(초)을 지정합니다.",
"form_enter_upstream_timeout":"업스트림 서버 응답 제한 시간을 초 단위로 입력하세요.",
"dnscrypt":"DNSCrypt",
"dns_over_https":"DNS-over-HTTPS",
"dns_over_tls":"DNS-over-TLS",
@@ -598,7 +601,7 @@
"disable_ipv6":"IPv6 주소 확인 비활성화",
"disable_ipv6_desc":"IPv6 주소(AAAA 유형)에 대한 모든 DNS 쿼리를 무시하고 HTTPS 유형 응답에서 IPv6 데이터를 제거합니다.",
"fastest_addr":"가장 빠른 IP 주소",
"fastest_addr_desc":"모든 DNS 서버에 쿼리를 수행한 다음 반응이 가장 빠른 IP주소를 반송합니다. AdGuard Home이 모든 DNS 서버의 응답을 기다려야 하기 때문에 DNS 쿼리 속도가 느려지지만 전반적인 연결이 향상됩니다.",
"fastest_addr_desc":"<b>모든</b> DNS 서버의 응답을 기다렸다가 각 서버의 TCP 연결 속도를 측정하여 연결 속도가 가장 빠른 서버의 IP주소를 반환합니다.<br/>이 모드는 하나 이상의 업스트림 서버가 응답하지 않는 경우, 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에 의해 처리됩니다.",
"upstream_parallel":"Parallelle verzoeken gebruiken om te versnellen door gelijktijdig verzoeken te sturen naar alle upstream servers.",
"parallel_requests":"Parallelle verzoeken",
"load_balancing":"Volume balanceren",
"load_balancing_desc":"Eén server per keer bevragen. AdGuard Home gebruikt hiervoor een gewogen willekeurig algoritme om de server te kiezen zodat de snelste server meer zal gebruikt worden.",
"load_balancing_desc":"Voer zoekopdrachten uit op één upstream-server tegelijk.<br/>AdGuard Home gebruikt een gewogen willekeurig algoritme om servers te selecteren met het laagste aantal mislukte zoekopdrachten en de laagste gemiddelde opzoektijd.",
"bootstrap_dns":"Bootstrap DNS-servers",
"bootstrap_dns_desc":"IP-adressen van DNS-servers die worden gebruikt om IP-adressen om te zetten van de DoH/DoT-resolvers die je opgeeft als upstreams. Opmerkingen zijn niet toegestaan.",
"fallback_dns_title":"Back-up DNS-servers",
"fallback_dns_desc":"Lijst met DNS-back-up-noodservers die worden gebruikt wanneer upstream DNS-servers niet reageren. De syntaxis is hetzelfde als in het veld hoofdstroomopwaarts hierboven.",
"fallback_dns_placeholder":"Voer één DNS-back-upserver per regel in",
"local_ptr_desc":"De DNS-servers die AdGuard Home gebruikt voor lokale PTR-zoekopdrachten. Deze servers worden gebruikt om PTR-verzoeken voor adressen in privé-IP-bereiken op te lossen, bijvoorbeeld \"192.168.12.34\", met behulp van reverse DNS. Indien niet ingesteld, gebruikt AdGuard Home de adressen van de standaard DNS-resolvers van uw besturingssysteem, behalve de adressen van AdGuard Home zelf.",
"local_ptr_desc":"DNS-servers die door AdGuard Home worden gebruikt voor privé PTR-, SOA- en NS-verzoeken. Een verzoek wordt als privé beschouwd als het vraagt om een ARPA-domein dat een subnet binnen privé-IP-bereiken bevat (zoals \"192.168.12.34\") en afkomstig is van een client met een privé-IP-adres. Indien niet ingesteld, zullen de standaard DNS-resolvers van je besturingssysteem worden gebruikt, behalve de AdGuard Home IP-adressen.",
"local_ptr_default_resolver":"Standaard gebruikt AdGuard Home de volgende omgekeerde DNS-resolvers: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home kon voor dit systeem geen geschikte private omgekeerde DNS-resolvers bepalen.",
"local_ptr_placeholder":"Voer één IP-adres per regel in",
"resolve_clients_title":"Omzetten van hostnamen van clients inschakelen",
"resolve_clients_desc":"Indien ingeschakeld, zal AdGuard Home proberen om IP-adressen van apparaten te converteren in hun hostnamen door PTR-verzoeken te sturen naar overeenkomstige resolvers (privé-DNS-servers voor lokale apparaten, upstream-server voor apparaten met een openbaar IP-adres).",
"use_private_ptr_resolvers_desc":"Omgekeerde DNS opzoekingen uitvoeren voor locale adressen door deze upstreamservers te gebruiken. Indien uitgeschakeld, reageert AdGuard Home met NXDOMAIN op al dergelijke PTR-verzoeken, uitgezonderd voor apparaten gekend van DHCP, /etc/hosts, enz.",
"use_private_ptr_resolvers_desc":"PTR-, SOA- en NS-verzoeken voor ARPA-domeinen die privé-IP-adressen bevatten oplossen via privé-upstreamservers, DHCP, /etc/hosts, enz. Indien uitgeschakeld, zal AdGuard Home op al dergelijke verzoeken reageren met NXDOMAIN.",
"check_dhcp_servers":"Zoek achter DHCP servers",
"save_config":"Configuratie opslaan",
"enabled_dhcp":"DHCP server inschakelen",
@@ -154,7 +154,7 @@
"use_adguard_parental":"Gebruik AdGuard Ouderlijk toezicht web service",
"use_adguard_parental_hint":"AdGuard Home controleert of het domein 18+ content bevat. Dit gebeurt dmv dezelfde privacy vriendelijke API als de Browsing Security web service.",
"enforce_safe_search":"Veilig zoeken gebruiken",
"enforce_save_search_hint":"AdGuard Home kan veilig zoeken forceren voor de volgende zoekmachines: Google, Youtube, Bing, en DuckDuckGo, Yandex, Pixabay.",
"enforce_save_search_hint":"AdGuard Home dwingt veilig zoeken af in de volgende zoekmachines: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay.",
"blocked_response_ttl_desc":"Hiermee geef je op hoeveel seconden de clients een gefilterd antwoord in de cache moeten opslaan",
"form_enter_blocked_response_ttl":"Voer geblokkeerd antwoord TTL in (seconden)",
"upstream_timeout":"Upstream time-out",
"upstream_timeout_desc":"Geeft het aantal seconden aan dat moet worden gewacht op een reactie van de upstream-server",
"form_enter_upstream_timeout":"Voer de time-outduur van de upstream-server in seconden in",
"dnscrypt":"DNSCrypt",
"dns_over_https":"DNS-via-HTTPS",
"dns_over_tls":"DNS-via-TLS",
@@ -324,10 +327,10 @@
"rate_limit_whitelist_placeholder":"Voer één IP-adres per regel in",
"blocking_ipv4_desc":"IP-adres dat moet worden teruggegeven voor een geblokkeerd A-verzoek",
"blocking_ipv6_desc":"IP-adres dat moet worden teruggegeven voor een geblokkeerd A-verzoek",
"blocking_mode_default":"Standaard: Reageer met een nul IPadres (0.0.0.0 for A; :: voor AAAA) wanneer geblokkeerd door een Adblock-type regel; reageer met het IP-adres dat is opgegeven in de regel wanneer geblokkeerd door een /etc/hosts type regel",
"blocking_mode_default":"Standaard: Reageer met een nul IP-adres (0.0.0.0 for A; :: voor AAAA) wanneer geblokkeerd door een Adblock-type regel; reageer met het IP-adres dat is opgegeven in de regel wanneer geblokkeerd door een /etc/hosts type regel",
"blocking_mode_refused":"REFUSED: Antwoorden met REFUSED code",
"blocking_mode_nxdomain":"NXDOMAIN: Reageer met NXDOMAIN code",
"blocking_mode_null_ip":"Nul IP: Reageer met een nul IPaddress (0.0.0.0 voor A; :: voor AAAA)",
"blocking_mode_null_ip":"Nul IP: Reageer met een nul IP-adres (0.0.0.0 voor A; :: voor AAAA)",
"blocking_mode_custom_ip":"Aangepast IP: Reageer met een handmatige ingesteld IP adres",
"theme_auto":"Automatisch",
"theme_light":"Licht",
@@ -495,7 +498,7 @@
"setup_dns_privacy_2":"<0>DNS-via-HTTPS:</0> Gebruik <1>{{address}}</1> string.",
"setup_dns_privacy_3":"<0>Hou er rekening mee dat het beveiligde DNS protocol alleen beschikbaar is voor Android 9. U moet dus extra software installeren voor andere besturingssystemen.</0><0>Hier is een lijst van te gebruiken software.</0>",
"setup_dns_privacy_4":"Op een iOS 14 of macOS Big Sur apparaat kan je een speciaal '.mobileconfig'-bestand downloaden dat <highlight>DNS-via-HTTPS</highlight> of <highlight>DNS-via-TLS</highlight> servers aan de DNS-instellingen toevoegt.",
"setup_dns_privacy_android_1":"Android 9 ondersteunt native DNS-via-TLS. Om het te configureren, ga naar Instellingen → Netwerk & internet → Geavanceerd → PrivéDNS en voer daar je domeinnaam in.",
"setup_dns_privacy_android_1":"Android 9 ondersteunt native DNS-via-TLS. Om het te configureren, ga naar Instellingen → Netwerk & internet → Geavanceerd → Privé-DNS en voer daar je domeinnaam in.",
"setup_dns_privacy_android_2":"<0>AdGuard voor Android</0>ondersteunt<1>DNS-via-HTTPS </1>en<1>DNS-via-TLS</1>.",
"setup_dns_privacy_android_3":"<0> Intra </0> voegt <1> DNS-via-HTTPS</1> ondersteuning toe aan Android.",
"setup_dns_privacy_ios_1":"<0>DNSCloak</0> ondersteunt <1> DNS-via-HTTPS </1>, maar om het te configureren op jouw eigen server moet er een <2> DNS-stempel </2> gegenereerd worden.",
"disable_ipv6_desc":"Alle DNS-query's voor IPv6-adressen (type AAAA) verwijderen en IPv6-hints uit HTTPS-antwoorden verwijderen.",
"fastest_addr":"Snelste IP adres",
"fastest_addr_desc":"Alle DNS-servers bevragen en het snelste IP adres terugkoppelen. Dit zal de DNS verzoeken vertragen omdat AdGuard Home moet wachten op de antwoorden van alles DNS-servers, maar verbetert wel de connectiviteit.",
"fastest_addr_desc":"Wacht op reacties van <b>alle</b> DNS-servers, meet de TCP-verbindingssnelheid voor elke server en retourneer het IP-adres van de server met de hoogste verbindingssnelheid.<br/>Deze modus kan DNS-query's aanzienlijk vertragen als een of meer upstream-servers niet reageren. Zorg ervoor dat je upstream-servers stabiel zijn en dat je upstream-time-out laag is.",
"autofix_warning_text":"Als je op \"Repareren\" klikt, configureert AdGuard Home jouw systeem om de AdGuard Home DNS-server te gebruiken.",
"autofix_warning_list":"De volgende taken worden uitgevoerd: <0> Deactiveren van Systeem DNSStubListener</0> <0> DNS-serveradres instellen op 127.0.0.1 </0> <0> Symbolisch koppelingsdoel van /etc/resolv.conf vervangen door /run/systemd/resolve/resolv.conf </0> <0> Stop DNSStubListener (herlaad systemd-resolved service) </0>",
"autofix_warning_result":"Als gevolg hiervan worden alle DNS-aanvragen van je systeem standaard door AdGuard Home verwerkt.",
"upstream_parallel":"Użyj zapytań równoległych, aby przyspieszyć rozwiązywanie przez jednoczesne wysyłanie zapytań do wszystkich serwerów nadrzędnych.",
"parallel_requests":"Równoległe żądania",
"load_balancing":"Równoważenie obciążenia",
"load_balancing_desc":"Wysyłaj zapytania do jednego serwera nadrzędnego na raz. AdGuard Home używa swojego losowego algorytmu ważonego, aby wybrać serwer, tak aby najszybszy serwer był używany częściej.",
"load_balancing_desc":"Zapytaj jeden serwer nadrzędny na raz. AdGuard Home używa ważonego, losowego algorytmu do wybierania serwerów z najmniejszą liczbą nieudanych wyszukiwań i najniższym uśrednionym czasem wyszukiwania.",
"bootstrap_dns":"Serwery DNS Bootstrap",
"bootstrap_dns_desc":"Adresy IP serwerów DNS używanych do rozpoznawania adresów IP programów rozpoznawania nazw DoH/DoT określonych jako nadrzędne. Komentarze są niedozwolone.",
"fallback_dns_title":"Rezerwowe serwery DNS",
"fallback_dns_desc":"Lista rezerwowych serwerów DNS używanych, gdy nadrzędne serwery DNS nie odpowiadają. Składnia jest taka sama jak w głównym polu powyżej.",
"fallback_dns_placeholder":"Wprowadź jeden rezerwowy serwer DNS w każdym wierszu",
"local_ptr_desc":"Serwery DNS, których AdGuard Home używa do lokalnych zapytań PTR. Serwery te są używane do rozpoznawania nazw hostów klientów z prywatnymi adresami IP, na przykład „192.168.12.34”, przy użyciu odwrotnego DNS. Jeśli nie jest ustawiona, AdGuard Home używa adresów domyślnych resolwerów DNS systemu operacyjnego, z wyjątkiem adresów samego AdGuard Home.",
"local_ptr_desc":"Serwery DNS używane przez AdGuard Home do prywatnych żądań PTR, SOA i NS. Żądanie jest uważane za prywatne, jeśli prosi o domenę ARPA zawierającą podsieć w prywatnym zakresie adresów IP (np. „192.168.12.34”) i pochodzi od klienta z prywatnym adresem IP. Jeśli nie zostanie ustawione, zostaną użyte domyślne programy rozpoznawania nazw DNS Twojego systemu operacyjnego, z wyjątkiem domowych adresów IP AdGuard.",
"local_ptr_default_resolver":"Domyślnie AdGuard Home używa następujących odwrotnych resolwerów DNS: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home nie mógł określić odpowiednich prywatnych resolwerów DNS dla tego systemu.",
"local_ptr_placeholder":"Wprowadź po jednym adresie IP w każdym wierszu",
"resolve_clients_title":"Włącz odwrotne rozpoznawanie adresów IP klientów",
"resolve_clients_desc":"Odwróć adresy IP klientów na ich nazwy hostów, wysyłając zapytania PTR do odpowiednich programów tłumaczących (prywatne serwery DNS dla klientów lokalnych, serwery nadrzędne dla klientów z publicznymi adresami IP).",
"use_private_ptr_resolvers_desc":"Wykonuj odwrotne wyszukiwania DNS dla adresów obsługiwanych lokalnie przy użyciu tych serwerów nadrzędnych. Po wyłączeniu AdGuard Home odpowiada za pomocą NXDOMAIN na wszystkie takie żądania PTR, z wyjątkiem klientów znanych z DHCP, /etc/hosts i tak dalej.",
"use_private_ptr_resolvers_desc":"Rozwiązuj żądania PTR, SOA i NS dla domen ARPA zawierających prywatne adresy IP za pośrednictwem prywatnych serwerów nadrzędnych, DHCP, /etc/hosts itp. Jeśli ta opcja jest wyłączona, AdGuard Home będzie odpowiadać na wszystkie takie żądania za pomocą NXDOMAIN.",
"no_upstreams_data_found":"Brak danych dotyczących serwerów nadrzędnych",
@@ -154,7 +154,7 @@
"use_adguard_parental":"Użyj usługi Kontrola Rodzicielska AdGuard",
"use_adguard_parental_hint":"AdGuard Home sprawdzi, czy domena zawiera materiały dla dorosłych. Używa tego samego interfejsu API przyjaznego prywatności, co usługa sieciowa Bezpieczne Przeglądanie. ",
"upstream_parallel":"Usar consultas paralelas para acelerar a resolução consultando simultaneamente todos os servidores DNS primário",
"parallel_requests":"Solicitações paralelas",
"load_balancing":"Balanceamento de carga",
"load_balancing_desc":"Consulte um servidor DNS primário por vez.O AdGuard Home usa seu algoritmo aleatório ponderado para escolher o servidor para que o servidor mais rápido seja usado com mais frequência.",
"load_balancing_desc":"Consulte um servidor upstream por vez.<br/>O AdGuard Home usa um algoritmo aleatório ponderado para selecionar servidores com o menor número de falhas e o menor tempo médio de consulta.",
"bootstrap_dns":"Servidores DNS de inicialização",
"bootstrap_dns_desc":"Endereços IP de servidores DNS usados para resolver endereços IP dos resolvedores DoH/DoT que você especifica como upstreams. Comentários não são permitidos.",
"fallback_dns_title":"Servidores DNS Fallback",
"fallback_dns_desc":"Lista de servidores DNS Fallback usados quando os servidores DNS primários não estão respondendo. A sintaxe é a mesma dos campos de servidores principais na seção acima.",
"fallback_dns_placeholder":"Insira um servidor DNS fallback por linha",
"local_ptr_title":"Servidores DNS reversos privados",
"local_ptr_desc":"Os servidores DNS que o AdGuard Home usa para consultas PTR locais. Esses servidores são usados para resolver solicitações de PTR para endereços em intervalos de IP privados, por exemplo \"192.168.12.34\", usando DNS reverso. Se não estiver definido, o AdGuard Home usa os endereços dos resolvedores de DNS padrão do seu sistema operacional, exceto os endereços do próprio AdGuard Home.",
"local_ptr_desc":"Os servidores DNS que o AdGuard Home utiliza para consultas privadas de PTR, SOA e NS. A solicitação é considerada privada se solicitar um domínio ARPA contendo uma sub-rede dentro de intervalos de IP privados, por exemplo \"192.168.12.34\", e vier de um cliente com endereço privado. Se não for definido, o AdGuard Home usará os endereços dos resolvedores DNS padrão do seu sistema operacional, exceto os endereços do próprio AdGuard Home.",
"local_ptr_default_resolver":"Por padrão, o AdGuard Home usa os seguintes resolvedores de DNS reverso: {{ip}}.",
"local_ptr_no_default_resolver":"A página inicial do AdGuard não conseguiu determinar resolvedores DNS reversos privados adequados para este sistema.",
"local_ptr_placeholder":"Insira um endereço IP por linha",
"resolve_clients_title":"Ativar resolução reversa de endereços IP de clientes",
"resolve_clients_desc":"Resolva reversamente os endereços IP dos clientes em seus nomes de host, enviando consultas PTR aos resolvedores correspondentes (servidores DNS privados para clientes locais, servidores upstream para clientes com endereços IP públicos).",
"use_private_ptr_resolvers_title":"Usar resolvedores DNS reversos privados",
"use_private_ptr_resolvers_desc":"Execute pesquisas reversas de DNS para endereços servidos localmente usando esses servidores DNS primário. Se desativado, o AdGuard Home responde com NXDOMAIN a todas essas solicitações PTR, exceto para clientes conhecidos de DHCP, /etc/hosts e assim por diante.",
"use_private_ptr_resolvers_desc":"Resolver solicitações PTR, SOA e NS para domínios ARPA contendo endereços privados usando servidores upstream privados, DHCP, /etc/hosts e assim por diante. Se desativado, o AdGuard Home responde a todas essas consultas com NXDOMAIN.",
"check_dhcp_servers":"Verificar por servidores DHCP",
"save_config":"Salvar configuração",
"enabled_dhcp":"Servidor DHCP ativado",
@@ -154,7 +154,7 @@
"use_adguard_parental":"Usar o serviço de controle parental do AdGuard",
"use_adguard_parental_hint":"O AdGuard Home irá verificar se o domínio contém conteúdo adulto. Ele usa a mesma API amigável de privacidade que o serviço de segurança da navegação.",
"enforce_safe_search":"Usar pesquisa segura",
"enforce_save_search_hint":"O AdGuard Home forcará a pesquisa segura nos seguintes motores de busca: Google, YouTube, Bing, DuckDuckGo, Yandex, Pixabay.",
"enforce_save_search_hint":"O AdGuard Home forcará a pesquisa segura nos seguintes motores de busca: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay.",
"blocked_response_ttl_desc":"Especifica por quantos segundos os clientes devem armazenar em cache uma resposta filtrada",
"form_enter_blocked_response_ttl":"Insira o TTL da resposta bloqueada (segundos)",
"upstream_timeout":"Tempo limite de upstream",
"upstream_timeout_desc":"Especifica o número de segundos para esperar por uma resposta do servidor upstream",
"form_enter_upstream_timeout":"Insira a duração do tempo limite do servidor upstream em segundos",
"dnscrypt":"DNSCrypt",
"dns_over_https":"DNS-sobre-HTTPS",
"dns_over_tls":"DNS-sobre-TLS",
@@ -598,7 +601,7 @@
"disable_ipv6":"Desativar resolução de endereços IPv6",
"disable_ipv6_desc":"Descarta todas as consultas DNS para endereços IPv6 (tipo AAAA) e remove dicas de IPv6 das respostas HTTPS.",
"fastest_addr":"Endereço de IP mais rápido",
"fastest_addr_desc":"Consulta todos os servidores DNS e retorna o endereço IP mais rápido entre todas as respostas. Isso torna as consultas DNS mais lentas, pois o AdGuard Home tem que esperar pelas respostas de todos os servidores DNS, mas melhora a conectividade geral.",
"fastest_addr_desc":"Aguarde as respostas de <b>todos</b> os servidores DNS, meça a velocidade da conexão TCP para cada servidor e retorne o endereço de IP do servidor com a velocidade de conexão mais rápida.<br/>Esse modo pode retardar significativamente as consultas de DNS, se um ou mais servidores DNS primários não estiverem respondendo. Certifique-se de que seus servidores DNS primários sejam estáveis e que seu tempo de espera para DNS seja baixo.",
"autofix_warning_text":"Se clicar em \"Corrigir\", o AdGuardHome irá configurar o seu sistema para utilizar o servidor DNS do AdGuardHome.",
"autofix_warning_list":"Ele irá realizar estas tarefas: <0>Desativar sistema DNSStubListener</0> <0>Definir endereço do servidor DNS para 127.0.0.1</0> <0>Substituir o alvo simbólico do link /etc/resolv.conf para /run/systemd/resolv.conf</0> <0>Parar DNSStubListener (recarregar serviço resolvido pelo sistema)</0>",
"autofix_warning_result":"Como resultado, todos as solicitações DNS do seu sistema serão processadas pelo AdGuard Home por padrão.",
"upstream_parallel":"Usar consultas paralelas para acelerar a resolução consultando simultaneamente todos os servidores DNS",
"parallel_requests":"Solicitações paralelas",
"load_balancing":"Balanceamento de carga",
"load_balancing_desc":"Consulte um servidor DNS primário por vez. O AdGuard Home usa seu algoritmo aleatório ponderado para escolher o servidor para que o servidor mais rápido seja usado com mais frequência.",
"load_balancing_desc":"Consulta um servidor upstream de cada vez. <br/>O AdGuard Home usa um algoritmo aleatório ponderado para selecionar servidores com o menor número de pesquisas falhadas e o menor tempo médio de pesquisa.",
"bootstrap_dns":"Servidores DNS de arranque",
"bootstrap_dns_desc":"Endereços IP de servidores DNS usados para resolver endereços IP dos resolvedores DoH/DoT que você especifica como upstreams. Comentários não são permitidos.",
"fallback_dns_title":"Servidores DNS de fallback",
"fallback_dns_desc":"Lista de servidores DNS de fallback usados quando os servidores DNS upstream não estão respondendo. A sintaxe é a mesma do campo principal de upstreams acima.",
"fallback_dns_placeholder":"Insira um servidor DNS de fallback por linha",
"local_ptr_title":"Servidores DNS reversos privados",
"local_ptr_desc":"Os servidores DNS que o AdGuard Home usa para consultas PTR locais. Esses servidores são usados para resolver solicitações de PTR para endereços em intervalos de IP privados, por exemplo \"192.168.12.34\", usando DNS reverso. Se não estiver definido, o AdGuard Home usa os endereços dos resolvedores de DNS padrão do seu sistema operacional, exceto os endereços do próprio AdGuard Home.",
"local_ptr_desc":"Os servidores DNS que o AdGuard Home utiliza para consultas privadas de PTR, SOA e NS. A solicitação é considerada privada se solicitar um domínio ARPA contendo uma sub-rede dentro de intervalos de IP privados, por exemplo \"192.168.12.34\", e vier de um cliente com endereço privado. Se não for definido, o AdGuard Home usará os endereços dos resolvedores DNS padrão do seu sistema operacional, exceto os endereços do próprio AdGuard Home.",
"local_ptr_default_resolver":"Por predefinição, o AdGuard Home usa os seguintes resolvedores de DNS reverso: {{ip}}.",
"local_ptr_no_default_resolver":"A página inicial do AdGuard não conseguiu determinar resolvedores DNS reversos privados adequados para este sistema.",
"local_ptr_placeholder":"Insira um endereço IP por linha",
"resolve_clients_title":"Ativar resolução reversa de endereços IP de clientes",
"resolve_clients_desc":"Resolva reversamente os endereços IP dos clientes em seus nomes de host, enviando consultas PTR aos resolvedores correspondentes (servidores DNS privados para clientes locais, servidores upstream para clientes com endereços IP públicos).",
"use_private_ptr_resolvers_title":"Usar resolvedores DNS reversos privados",
"use_private_ptr_resolvers_desc":"Execute pesquisas reversas de DNS para endereços servidos localmente usando esses servidores DNS primário. Se desativado, o AdGuard Home responde com NXDOMAIN a todas essas solicitações PTR, exceto para clientes conhecidos de DHCP, /etc/hosts e assim por diante.",
"use_private_ptr_resolvers_desc":"Resolver solicitações PTR, SOA e NS para domínios ARPA contendo endereços privados usando servidores upstream privados, DHCP, /etc/hosts e assim por diante. Se desativado, o AdGuard Home responde a todas essas consultas com NXDOMAIN.",
"check_dhcp_servers":"Verificar por servidores DHCP",
"save_config":"Guardar definição",
"enabled_dhcp":"Servidor DHCP ativado",
@@ -154,7 +154,7 @@
"use_adguard_parental":"Usar o serviço de controlo parental do AdGuard",
"use_adguard_parental_hint":"O AdGuard Home irá verificar se o domínio contém conteúdo adulto. Usa a mesma API amigável de privacidade que o serviço de segurança da navegação.",
"enforce_safe_search":"Usar pesquisa segura",
"enforce_save_search_hint":"O AdGuard Home forçará a pesquisa segura nos seguintes motores de busca: Google, Youtube, Bing, DuckDuckGo, Yandex, Pixabay.",
"enforce_save_search_hint":"O AdGuard Home aplicará pesquisa segura nos seguintes motores de busca: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay.",
"blocked_response_ttl_desc":"Especifica por quantos segundos os clientes devem armazenar em cache uma resposta filtrada",
"form_enter_blocked_response_ttl":"Insira o TTL da resposta bloqueada (segundos)",
"upstream_timeout":"Tempo esgotado de upstream",
"upstream_timeout_desc":"Especifica o número de segundos a aguardar por uma resposta do servidor upstream",
"form_enter_upstream_timeout":"Insira a duração do tempo esgotado do servidor upstream em segundos",
"dnscrypt":"DNSCrypt",
"dns_over_https":"DNS-sobre-HTTPS",
"dns_over_tls":"DNS-sobre-TLS",
@@ -598,7 +601,7 @@
"disable_ipv6":"Desativar resolução de endereços IPv6",
"disable_ipv6_desc":"Descarte todas as consultas DNS para endereços IPv6 (tipo AAAA) e remova as dicas IPv6 das respostas HTTPS.",
"fastest_addr":"Endereço de IP mais rápido",
"fastest_addr_desc":"Consulta todos os servidores DNS e retorna o endereço IP mais rápido entre todas as respostas. Isso torna as consultas DNS mais lentas, pois o AdGuard Home tem que esperar pelas respostas de todos os servidores DNS, mas melhora a conectividade geral.",
"fastest_addr_desc":"Aguarda por respostas de <b>todos</b> os servidores DNS, mede a velocidade da ligação TCP para cada servidor e devolva o endereço IP do servidor com a velocidade de ligação mais rápida.<br/>Este modo pode abrandar significativamente as consultas DNS, se um ou mais servidores upstream não estiverem a responder. Certifique-se de que os seus servidores upstream são estáveis e que o tempo esgotado de upstream é baixo.",
"autofix_warning_text":"Se clicar em \"Corrigir\", o AdGuardHome irá configurar o seu sistema para utilizar o servidor DNS do AdGuardHome.",
"autofix_warning_list":"Irá realizar estas tarefas: <0>Desativar sistema DNSStubListener</0> <0>Definir endereço do servidor DNS para 127.0.0.1</0> <0>Substituir o alvo simbólico do link /etc/resolv.conf para /run/systemd/resolv.conf</0> <0>Parar DNSStubListener (recarregar serviço resolvido pelo sistema)</0>",
"autofix_warning_result":"Como resultado, todos as solicitações DNS do seu sistema serão processadas pelo AdGuard Home por predefinição.",
"upstream_parallel":"Использовать параллельные запросы ко всем серверам одновременно для ускорения обработки запроса.",
"parallel_requests":"Параллельные запросы",
"load_balancing":"Распределение нагрузки\n",
"load_balancing_desc":"Запрашивать по одному серверу за раз. AdGuard Home использует алгоритм взвешенного случайного выбора сервера, так что самый быстрый сервер используется чаще.",
"load_balancing_desc":"Запрашивать по одному upstream-серверу.<br/>AdGuard Home использует алгоритм случайной выборки с учётом веса для выбора серверов с наименьшим количеством неудачных запросов и наименьшим средним временем выполнения запроса.",
"bootstrap_dns":"Bootstrap DNS-серверы",
"bootstrap_dns_desc":"IP-адреса DNS-серверов, используемых для поиска IP-адресов DoH/DoT upstream-серверов, которые вы указали. Комментарии не допускаются.",
"fallback_dns_title":"Резервные DNS-серверы",
"fallback_dns_desc":"Список резервных DNS-серверов, используемых в тех случаях, когда вышестоящие DNS-серверы недоступны. Синтаксис такой же, как и в поле Upstream DNS-серверы выше.",
"fallback_dns_placeholder":"Введите один резервный DNS-сервер в каждой строке",
"local_ptr_title":"Приватные серверы для обратного DNS",
"local_ptr_desc":"DNS-серверы, которые AdGuard Home использует для локальных PTR-запросов. Эти серверы используются, чтобы получить доменные имена клиентов с приватными IP-адресами, например «192.168.12.34», с помощью обратного DNS. Если список пуст, AdGuard Home использует DNS-серверы по умолчанию вашей ОС.",
"local_ptr_desc":"DNS-серверы, которые AdGuard Home использует для локальных PTR, SOA и NS-запросов. Запрос считается локальным, если он запрашивает информацию об ARPA-домене, подсеть которого в локальном IP-диапазоне (например, «192.168.12.34»), и если при этом запрос пришел от клиента с локальным адресом. Если значение не установлено, AdGuard Home использует адреса DNS-серверы по умолчанию в вашей ОС, за исключением адресов самого AdGuard Home.",
"local_ptr_default_resolver":"По умолчанию AdGuard Home использует следующие обратные DNS-резолверы: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home не смог определить подходящие приватные обратные DNS-резолверы для этой системы.",
"local_ptr_placeholder":"Введите по одному адресу на строчку",
"resolve_clients_title":"Включить запрашивание доменных имён для IP-адресов клиентов",
"resolve_clients_desc":"Определять доменные имена клиентов через PTR-запросы к соответствующим серверам (приватные DNS-серверы для локальных клиентов, upstream-серверы для клиентов с публичным IP-адресом).",
"use_private_ptr_resolvers_desc":"Посылать обратные DNS-запросы для локально обслуживаемых адресов на указанные серверы. Если отключено, AdGuard Home будет отвечать NXDOMAIN на все подобные PTR-запросы, кроме запросов о клиентах, уже известных по DHCP, /etc/hosts и так далее.",
"use_private_ptr_resolvers_desc":"Посылать PTR, SOA и NS-запросы для ARPA-доменов, содержащих локальные адреса, с помощью указанных upstream-серверов, DHCP, /etc/hosts и так далее. Если отключено, AdGuard Home отвечает NXDOMAIN на все подобные запросы.",
"check_dhcp_servers":"Проверить DHCP-серверы",
"save_config":"Сохранить конфигурацию",
"enabled_dhcp":"DHCP-сервер включён",
@@ -154,7 +154,7 @@
"use_adguard_parental":"Включить модуль Родительского контроля AdGuard ",
"use_adguard_parental_hint":"AdGuard Home проверит, содержит ли домен материалы 18+. Он использует тот же API для обеспечения конфиденциальности, что и веб-служба безопасности браузера.",
"enforce_save_search_hint":"AdGuard Home может обеспечить безопасный поиск в следующих поисковых системах: Google, YouTube, Bing, DuckDuckGo, Yandex и Pixabay.",
"enforce_save_search_hint":"AdGuard Home будет обеспечивать безопасный поиск в следующих поисковых системах: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay.",
"disable_ipv6_desc":"Игнорировать все DNS-запросы адресов IPv6 (тип AAAA) и удалять IPv6-данные из ответов типа HTTPS.",
"fastest_addr":"Самый быстрый IP-адрес",
"fastest_addr_desc":"Опросить все DNS-серверы и вернуть самый быстрый IP-адрес из полученных ответов. Это замедлит DNS-запросы, так как нужно будет дождаться ответов со всех DNS-серверов, но улучшит соединение.",
"fastest_addr_desc":"Дождаться ответов от <b>всех</b> DNS-серверов, измерить скорость TCP-соединения для каждого сервера и вернуть IP-адрес сервера с самой высокой скоростью соединения.<br/>Этот режим может значительно замедлить выполнение DNS-запросов, если один или несколько серверов не отвечают. Убедитесь, что ваши серверы работают стабильно, а время ожидания серверов мало.",
"autofix_warning_text":"При нажатии «Исправить» AdGuard Home настроит вашу систему на использование DNS-сервера AdGuard Home.",
"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 (перезагрузить системную службу)</0>.",
"autofix_warning_result":"В результате все DNS-запросы от вашей системы будут по умолчанию обрабатываться AdGuard Home.\n",
"upstream_parallel":"Používať paralelné dopyty na zrýchlenie súčasným dopytovaním všetkých upstream serverov súčasne.",
"parallel_requests":"Paralelné dopyty",
"load_balancing":"Vyrovnávanie záťaže",
"load_balancing_desc":"Dopytovať len jeden server v danom čase. AdGuard Home použije na výber servera vážený náhodný algoritmus, aby sa najrýchlejší server používal častejšie.",
"load_balancing_desc":"Dopytuje sa súčasne len jeden upstream server.<br/>AdGuard Home používa vážený náhodný algoritmus na výber serverov s najnižším počtom neúspešných vyhľadávaní a najnižším priemerným časom vyhľadávania.",
"bootstrap_dns":"Bootstrap DNS servery",
"bootstrap_dns_desc":"IP adresy serverov DNS používaných na rozlíšenie IP adries prekladačov DoH/DoT, ktoré zadáte ako upstream. Komentáre nie sú povolené.",
"fallback_dns_title":"Záložné servery DNS",
"fallback_dns_desc":"Zoznam záložných serverov DNS, ktoré sa používajú, keď nadradený servery DNS neodpovedajú. Syntax je rovnaká ako v hlavnom poli vyššie.",
"fallback_dns_placeholder":"Zadajte jeden záložný server DNS na riadok",
"local_ptr_title":"Súkromné reverzné DNS servery",
"local_ptr_desc":"DNS servery, ktoré AdGuard Home používa pre miestne PTR dopyty. Tieto servery sa používajú na rozlíšenie názvov hostiteľov klientov so súkromnými adresami IP, napríklad \"192.168.12.34\", pomocou reverzného DNS. Ak nie je nastavené inak, AdGuard Home použije adresy predvolených prekladačov DNS Vášho operačného systému okrem adries samotného AdGuard Home.",
"local_ptr_desc":"Servery DNS, ktoré používa AdGuard Home na súkromné dopyty PTR, SOA a NS. Dopyt sa považuje za súkromný, ak požaduje doménu ARPA obsahujúcu podsieť v rozsahu súkromnej IP adresy (napríklad „192.168.12.34“) a pochádza od klienta so súkromnou IP adresou. Ak nie je nastavené, použijú sa predvolené DNS resolvery Vášho operačného systému, okrem AdGuard Home IP adries.",
"local_ptr_default_resolver":"V predvolenom nastavení používa AdGuard Home nasledujúce reverzné DNS prekladače: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home nemohol určiť vhodné súkromné reverzné DNS prekladače pre tento systém.",
"local_ptr_placeholder":"Na každý riadok zadajte IP adresu jedného servera",
"resolve_clients_title":"Povoliť spätný preklad IP adries klientov",
"resolve_clients_desc":"Reverzne rozlišuje adresy IP klientov na ich názvy hostiteľov odosielaním PTR dopytov príslušným prekladačom (súkromné DNS servery pre miestnych klientov, servery typu upstream pre klientov s verejnými IP adresami).",
"use_private_ptr_resolvers_title":"Použiť súkromné reverzné DNS resolvery",
"use_private_ptr_resolvers_desc":"Realizuje reverzné vyhľadávanie DNS pre lokálne adresy pomocou týchto upstream serverov. Ak je funkcia vypnutá, Adguard Home reaguje s NXDOMAIN na všetky takéto PTR dopyty okrem klientov známych z DHCP, /etc/hosts, a tak ďalej.",
"use_private_ptr_resolvers_desc":"Riešenie dopytov PTR, SOA a NS pre domény ARPA obsahujúce súkromné IP adresy prostredníctvom súkromných upstream serverov, DHCP, /etc/hosts atď. Ak je vypnuté, AdGuard Home bude na všetky takéto dopyty odpovedať pomocou NXDOMAIN.",
"check_dhcp_servers":"Skontrolovať DHCP servery",
"save_config":"Uložiť konfiguráciu",
"enabled_dhcp":"DHCP server zapnutý",
@@ -89,7 +89,7 @@
"form_enter_hostname":"Zadajte meno hostiteľa",
"error_details":"Podrobnosti chyby",
"response_details":"Podrobnosti odpovede",
"request_details":"Podrobnosti požiadavky",
"request_details":"Podrobnosti dopytu",
"client_details":"Podrobnosti klienta",
"details":"Podrobnosti",
"back":"Naspäť",
@@ -154,7 +154,7 @@
"use_adguard_parental":"Použiť AdGuard službu Rodičovská kontrola",
"use_adguard_parental_hint":"AdGuard Home skontroluje, či doména obsahuje materiály pre dospelých. Používa rovnaké API priateľské k ochrane osobných údajov ako služba Bezpečného prehliadania.",
"enforce_save_search_hint":"AdGuard Home vynucuje bezpečné vyhľadávanie v nasledujúcich vyhľadávačoch: Google, YouTube, Bing, DuckDuckGo, Yandex a Pixabay.",
"enforce_save_search_hint":"AdGuard Home vynúti bezpečné vyhľadávanie v nasledujúcich vyhľadávačoch: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay.",
"no_servers_specified":"Neboli špecifikované žiadne servery",
"general_settings":"Všeobecné nastavenia",
"dns_settings":"Nastavenia DNS",
@@ -294,6 +294,9 @@
"blocked_response_ttl":"Blokovaná odozva TTL",
"blocked_response_ttl_desc":"Určuje, na koľko sekúnd by mali klienti uložiť filtrovanú odozvu do vyrovnávacej pamäte",
"edns_cs_desc":"Pridáva možnosť EDNS Client Subnet (ECS) do upstream požiadaviek a zapíše hodnoty odoslané klientmi do denníka dopytov.",
"edns_cs_desc":"Pridáva možnosť EDNS Client Subnet (ECS) do upstream dopytov a zapíše hodnoty odoslané klientami do denníka dopytov.",
"edns_use_custom_ip":"Použiť vlastnú IP adresu pre EDNS",
"edns_use_custom_ip_desc":"Povoliť používanie vlastnej IP adresy pre EDNS",
"rate_limit_desc":"Počet požiadaviek za sekundu, ktoré môže jeden klient vykonať. Nastavenie na hodnotu 0 znamená neobmedzene.",
@@ -480,11 +483,11 @@
"access_title":"Nastavenia prístupu",
"access_desc":"Tu môžete konfigurovať pravidlá prístupu pre server DNS AdGuard Home.",
"access_allowed_title":"Povolení klienti",
"access_allowed_desc":"Zoznam CIDR, IP adries alebo <a>ClientID</a>. Ak tento zoznam obsahuje položky, AdGuard Home bude akceptovať požiadavky iba od týchto klientov.",
"access_allowed_desc":"Zoznam CIDR, IP adries alebo <a>ClientID</a>. Ak tento zoznam obsahuje položky, AdGuard Home bude akceptovať dopyty iba od týchto klientov.",
"access_disallowed_title":"Nepovolení klienti",
"access_disallowed_desc":"Zoznam CIDR, IP adries alebo <a>ClientID</a>. Ak tento zoznam obsahuje položky, AdGuard Home zruší požiadavky od týchto klientov. Toto pole sa ignoruje, ak sú v poli Povolení klienti položky.",
"access_disallowed_desc":"Zoznam CIDR, IP adries alebo <a>ClientID</a>. Ak tento zoznam obsahuje položky, AdGuard Home zruší dopyty od týchto klientov. Toto pole sa ignoruje, ak sú v poli Povolení klienti položky.",
"access_blocked_title":"Nepovolené domény",
"access_blocked_desc":"Nesmie byť zamieňaná s filtrami. AdGuard Home zruší DNS dopyty, ktoré sa zhodujú s týmito doménami, a tieto dopyty sa nezobrazia ani v denníku dopytov. Môžete určiť presné názvy domén, zástupné znaky alebo pravidlá filtrovania URL adries, napr. \"example.org\", \"*.example.org\" alebo ||example.org^\" zodpovedajúcim spôsobom.",
"access_blocked_desc":"Nesmie byť zamieňaná s filtrami. AdGuard Home zruší DNS dopyty, ktoré sa zhodujú s týmito doménami, a tieto dopyty sa nezobrazia ani v denníku dopytov. Môžete určiť presné názvy domén, zástupné znaky alebo pravidlá filtrácie URL adries, napr. \"example.org\", \"*.example.org\" alebo ||example.org^\" zodpovedajúcim spôsobom.",
"access_settings_saved":"Nastavenia prístupu úspešne uložené",
"updates_checked":"K dispozícii je nová verzia aplikácie AdGuard Home\n",
"updates_version_equal":"AdGuard Home je aktuálny",
@@ -598,7 +601,7 @@
"disable_ipv6":"Vypnúť rozlišovanie IPv6 adries",
"disable_ipv6_desc":"Ignorovať všetky dotazy DNS na adresy IPv6 (typ AAAA) a odstrániť IPv6 údaje z HTTPS odpovedí.",
"fastest_addr":"Najrýchlejšia IP adresa",
"fastest_addr_desc":"Dopytovať všetky servery DNS a vrátiť najrýchlejšiu IP adresu zo všetkých odpovedí. Toto spomalí DNS dopyty, pretože AdGuard Home musí čakať na odpovede zo všetkých serverov DNS, ale zlepší sa celkové pripojenie.",
"fastest_addr_desc":"Čaká na odpovede od <b>všetkých</b> DNS serverov, zmeria rýchlosť pripojenia TCP pre každý server a vráti adresu IP servera s najväčšou rýchlosťou pripojenia.<br/>Tento režim môže výrazne spomaliť DNS dopyty, ak jeden alebo viac upstream serverov neodpovedá. Uistite sa, že Vaše upstream servery sú stabilné a upstream upstream je nízky.",
"autofix_warning_text":"Ak kliknete na „Opraviť“, AdGuardHome nakonfiguruje Váš systém tak, aby používal DNS server AdGuardHome.",
"autofix_warning_list":"Bude vykonávať tieto úlohy: <0>Deaktivovať systém DNSStubListener</0> <0>Nastaviť adresu servera DNS na 127.0.0.1</0> <0>Nahradiť cieľový symbolický odkaz /etc/resolv.conf na /run/systemd/resolve/resolv.conf</0> <0>Zastaviť službu DNSStubListener (znova načítať službu systemd-resolved)</0>",
"autofix_warning_result":"Výsledkom bude, že všetky DNS dopyty z Vášho systému budú štandardne spracované službou AdGuard Home.",
"load_balancing_desc":"Fråga en uppströmsserver åt gången. AdGuard Home använder sin viktade slumpmässiga algoritm för att välja server så att den snabbaste servern används oftare.",
"bootstrap_dns":"Bootstrap-DNS-servrar",
"bootstrap_dns_desc":"IP-adresser för DNS-servrar som används för att lösa IP-adresser för de DoH/DoT-resolvers som du anger som uppströms. Kommentarer är inte tillåtna.",
"fallback_dns_title":"Reserv-DNS-servrar",
"fallback_dns_title":"ReservDNS-servrar",
"fallback_dns_desc":"Lista över reserv-DNS-servrar som används när uppströms DNS-servrar inte svarar. Syntaxen är densamma som i huvuduppströmsfältet ovan.",
"fallback_dns_placeholder":"Ange en reserv-DNS-server per rad",
"local_ptr_title":"Privata omvända DNS-servrar",
@@ -141,8 +141,8 @@
"number_of_dns_query_blocked_24_hours":"Antalet DNS-förfrågningar som blockerades av annonsfilter och värdens blockeringsklistor",
"number_of_dns_query_blocked_24_hours_by_sec":"Antalet DNS-förfrågningar som blockerades av AdGuards modul för surfsäkerhet",
"number_of_dns_query_blocked_24_hours_adult":"Antalet vuxensajter som blockerats",
"enforced_save_search":"Aktivering av Säker surf",
"number_of_dns_query_to_safe_search":"Antalet DNS-förfrågningar mot sökmotorer där Säker surf tvingats",
"enforced_save_search":"Genomdrev SafeSearch",
"number_of_dns_query_to_safe_search":"Antalet DNS-förfrågningar till sökmotorer för vilka SafeSearch genomdrevs",
"use_adguard_browsing_sec_hint":"AdGuard Home kommer att kontrollera om en domän är blockerad av webbservicen surfsäkerhet. Med en integritetsvänlig metod görs en API-lookup för att kontrollera: endast ett kort prefix i domännamnet SHA256 hash skickas till servern.",
"use_adguard_parental":"Använda AdGuards webbservice för föräldrakontroll",
"use_adguard_parental_hint":"AdGuard Home kommer att kontrollera domäner för innehåll av vuxenmaterial . Samma integritetsvänliga metod för API-lookup som tillämpas i webbservicens surfsäkerhet används.",
"enforce_safe_search":"Använd säker webbsökning",
"enforce_safe_search":"Använd SafeSearch",
"enforce_save_search_hint":"AdGuard Home kommer tvinga säker surf på följande sökmotorer: Google, Youtube, Bing, DuckDuckGo, Yandex, Pixabay.",
"upstream_parallel":"Tüm üst sunucuları eş zamanlı sorgulayarak çözümlemeyi hızlandırmak için paralel sorgular kullanın.",
"parallel_requests":"Paralel istekler",
"load_balancing":"Yük dengeleme",
"load_balancing_desc":"Her seferde bir üst sunucuyu sorgulayın. AdGuard Home, sunucuyu seçmek için ağırlıklı rastgele algoritmasını kullanır, böylece en hızlı sunucu daha sık kullanılır.",
"load_balancing_desc":"Aynı anda bir üst kaynak sunucusunu sorgulayın. AdGuard Home, en düşük başarısız arama sayısına ve en düşük ortalama arama süresine sahip sunucuları seçmek için ağırlıklı rastgele bir algoritma kullanır.",
"bootstrap_dns":"DNS Önyükleme sunucuları",
"bootstrap_dns_desc":"Üst kaynak olarak belirttiğiniz DoH/DoT çözümleyicilerin IP adreslerini çözümlemek için kullanılan DNS sunucularının IP adresleri. Yorumlara izin verilmez.",
"fallback_dns_title":"Yedek DNS sunucuları",
"fallback_dns_desc":"Yukarı akış DNS sunucuları yanıt vermediğinde kullanılan yedek DNS sunucularının listesi. Söz dizimi yukarıdaki ana üst kaynak alanıyla aynıdır.",
"fallback_dns_placeholder":"Her satıra bir yedek DNS sunucusu girin",
"local_ptr_title":"Özel ters DNS sunucuları",
"local_ptr_desc":"AdGuard Home'un yerel PTR sorguları için kullandığı DNS sunucuları. Bu sunucular, rDNS kullanarak, örneğin \"192.168.12.34\" gibi özel IP aralıklarındaki adresler için PTR isteklerini çözmek için kullanılır. Ayarlanmadığı durumda AdGuard Home, işletim sisteminizin varsayılan DNS çözümleme adreslerini kullanır.",
"local_ptr_desc":"AdGuard Home tarafından özel PTR, SOA ve NS istekleri için kullanılan DNS sunucuları. Bir istek, özel IP aralıkları (\"192.168.12.34\" gibi) içinde bir alt ağ içeren bir ARPA alan adı ister ve özel IP adresine sahip bir istemciden gelirse özel olarak kabul edilir. Ayarlanmadığı durumda AdGuard Home, IP adresleri dışında işletim sisteminizin varsayılan DNS çözümleyicileri kullanılır.",
"local_ptr_default_resolver":"AdGuard Home, varsayılan olarak aşağıdaki ters DNS çözümleyicilerini kullanır: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home, bu sistem için uygun olan özel ters DNS çözümleyicilerini belirleyemedi.",
"local_ptr_placeholder":"Her satıra bir IP adresi girin",
"resolve_clients_title":"İstemcilerin IP adreslerinin ters çözümlenmesini etkinleştir",
"resolve_clients_desc":"Karşılık gelen çözümleyicilere (yerel istemciler için özel DNS sunucuları, genel IP adresleri olan istemciler için üst sunucuları) PTR sorguları göndererek istemcilerin IP adreslerini ana makine adlarının tersine çözün.",
"use_private_ptr_resolvers_title":"Özel ters DNS çözümleyicileri kullan",
"use_private_ptr_resolvers_desc":"Bu üst kaynak sunucularını kullanarak yerel olarak sunulan adresler için ters DNS aramaları yapın. Devre dışı bırakılırsa, AdGuard Home, DHCP, /etc/hosts, vb. tarafından bilinen istemciler dışında bu tür tüm PTR isteklerine NXDOMAIN ile yanıt verir.",
"use_private_ptr_resolvers_desc":"Özel üst kaynak sunucuları, DHCP, /etc/hosts, vb. aracılığıyla özel IP adresleri içeren ARPA alan adları için PTR, SOA ve NS isteklerini çözümleyin. Devre dışı bırakılırsa, AdGuard Home bu tür tüm isteklere NXDOMAIN ile yanıt verir.",
"check_dhcp_servers":"DHCP sunucularını denetle",
"save_config":"Yapılandırmayı kaydet",
"enabled_dhcp":"DHCP sunucusu etkinleştirildi",
@@ -40,11 +40,11 @@
"dhcp_ipv4_settings":"DHCP IPv4 Ayarları",
"dhcp_ipv6_settings":"DHCP IPv6 Ayarları",
"form_error_required":"Gerekli alan",
"form_error_ip4_format":"Geçersiz IPv4 adresi",
"form_error_ip4_gateway_format":"Geçersiz ağ geçidi IPv4 adresi",
"form_error_client_id_format":"İstemci Kimliği yalnızca sayılar, küçük harfler ve kısa çizgiler içermelidir",
"form_error_server_name":"Sunucu adı geçersiz",
"form_error_subnet":"\"{{cidr}}\" alt ağı, \"{{ip}}\" IP adresini içermiyor",
@@ -68,7 +68,7 @@
"ip":"IP",
"dhcp_table_hostname":"Ana makine Adı",
"dhcp_table_expires":"Bitiş tarihi",
"dhcp_warning":"DHCP sunucusunu yine de etkinleştirmek istiyorsanız, ağınızda başka aktif DHCP sunucusu olmadığından emin olun, aksi takdirde ağa bağlı cihazların İnternet bağlantısı kesilebilir!",
"dhcp_warning":"DHCP sunucusunu yine de etkinleştirmek istiyorsanız, ağınızda başka bir aktif DHCP sunucusu olmadığından emin olun, aksi takdirde ağa bağlı cihazların internet bağlantısı kesilebilir!",
"dhcp_error":"AdGuard Home, ağda başka bir etkin DHCP sunucusu olup olmadığını belirleyemedi",
"dhcp_static_ip_error":"DHCP sunucusunu kullanmak için sabit bir IP adresi ayarlanmalıdır. AdGuard Home, bu ağ arayüzünün sabit bir IP adresi kullanılarak yapılandırılıp yapılandırılmadığını belirleyemedi. Lütfen sabit IP adresini elle ayarlayın.",
"dhcp_dynamic_ip_found":"Sisteminiz, <0>{{interfaceName}}</0> arayüzü için dinamik IP adresi yapılandırması kullanıyor. DHCP sunucusunu kullanmak için sabit bir IP adresi ayarlanmalıdır. Geçerli olan IP adresiniz <0>{{ipAddress}}</0>. \"DHCP sunucusunu etkinleştir\" düğmesine basarsanız, AdGuard Home bu IP adresini otomatik bir şekilde sabit olarak ayarlayacaktır.",
@@ -147,14 +147,14 @@
"average_upstream_response_time":"Ortalama üst kaynak yanıt süresi",
"response_time":"Yanıt süresi",
"average_processing_time_hint":"Bir DNS isteğinin milisaniye cinsinden ortalama işlem süresi",
"block_domain_use_filters_and_hosts":"Filtre ve hosts dosyalarını kullanarak alan adlarını engelle",
"block_domain_use_filters_and_hosts":"Filtre ve ana bilgisayar dosyalarını kullanarak alan adlarını engelle",
"use_adguard_browsing_sec":"AdGuard gezinti koruması web hizmetini kullan",
"use_adguard_browsing_sec_hint":"AdGuard Home, alan adının gezinti koruması web hizmeti tarafından engellenip engellenmediğini kontrol eder. Kontrolü gerçekleştirmek için gizlilik dostu arama API'sini kullanır: sunucuya yalnızca SHA256 karma alan adının kısa bir ön eki gönderilir.",
"use_adguard_parental":"AdGuard ebeveyn denetimi web hizmetini kullan",
"use_adguard_parental_hint":"AdGuard Home, alan adının yetişkin içerik bulundurup bulundurmadığını kontrol eder. Gezinti koruması web hizmeti ile kullandığımız aynı gizlilik dostu API'yi kullanır.",
"enforce_safe_search":"Güvenli Aramayı kullan",
"enforce_save_search_hint":"AdGuard Home, şu arama motorlarında güvenli aramayı uygular: Google, YouTube, Bing, DuckDuckGo, Yandex ve Pixabay.",
"install_welcome_desc":"AdGuard Home, ağ genelinde reklamları ve izleyicileri engelleyen bir DNS sunucusudur. Tüm ağınızı ve tüm cihazlarınızı kontrol etmenizi sağlar, istemci tarafında herhangi bir program kullanmanıza gerek duymaz.",
"install_welcome_desc":"AdGuard Home, ağ genelinde reklam ve izleyici engelleyen bir DNS sunucusudur. Tüm ağınızı ve cihazlarınızı kontrol etmenizi sağlar ve istemci tarafında ek bir yazılım kullanmanıza gerek duymaz.",
"install_settings_title":"Yönetici Web Arayüzü",
"install_settings_listen":"Dinleme arayüzü",
"install_settings_port":"Bağlantı noktası",
"install_settings_interface_link":"AdGuard Home yönetici web arayüzünüz aşağıdaki adreslerde bulunacaktır:",
"install_settings_interface_link":"AdGuard Home yönetici web arayüzüne aşağıdaki adreslerden erişebilirsiniz:",
"form_error_port":"Geçerli bir bağlantı noktası değeri girin",
"install_settings_dns":"DNS sunucusu",
"install_settings_dns_desc":"Aşağıdaki adreslerde DNS sunucusunu kullanmak için cihazlarınızı veya yönlendiricinizi yapılandırmanız gerekir:",
"install_settings_dns_desc":"Cihazlarınızı veya yönlendiricinizi aşağıdaki adreslerdeki DNS sunucusunu kullanacak şekilde yapılandırmanız gerekir:",
"install_auth_desc":"AdGuard Home yönetim web arayüzü için şifre doğrulaması yapılandırılmalıdır. AdGuard Home'a yalnızca yerel ağınızdan erişilebilir olsa bile, onu sınırsız erişimden korumak yine de önemlidir.",
"install_auth_desc":"AdGuard Home yönetici web arayüzüne parola ile kimlik doğrulama yapılandırılmalıdır. AdGuard Home yalnızca yerel ağınızdan erişilebilir olsa bile, yine de yetkisiz erişime karşı korunması önemlidir.",
"install_auth_username":"Kullanıcı adı",
"install_auth_password":"Parola",
"install_auth_confirm":"Parolayı onayla",
@@ -366,10 +369,10 @@
"install_devices_router":"Yönlendirici",
"install_devices_router_desc":"Bu kurulum, ev yönlendiricinize bağlı tüm cihazları otomatik olarak kapsar ve her birini elle yapılandırmanıza gerek yoktur.",
"install_devices_address":"AdGuard Home DNS sunucusu aşağıdaki adresleri dinliyor",
"install_devices_router_list_1":"Yönlendiricinizin ayarlarına gidin. Genellikle tarayıcınızdan http://192.168.0.1/ veya http://192.168.1.1/ gibi bir URL aracılığıyla erişebilirsiniz. Bir parola girmeniz istenebilir. Hatırlamıyorsanız, genellikle yönlendiricinin üzerindeki bir düğmeye basarak parolayı sıfırlayabilirsiniz, ancak bu işlemin seçilmesi durumunda yüksek ihtimalle tüm yönlendirici yapılandırmasını kaybedeceğinizi unutmayın. Yönlendiricinizin kurulumu için bir uygulama gerekiyorsa, lütfen uygulamayı telefonunuza veya PC'nize yükleyin ve yönlendiricinin ayarlarına erişmek için kullanın.",
"install_devices_router_list_1":"Yönlendiricinizin ayarlarına gidin. Genellikle, tarayıcınızdan http://192.168.0.1/ veya http://192.168.1.1/ gibi bir URL üzerinden erişebilirsiniz. Giriş yaparken bir parola girmeniz istenebilir. Parolanızı hatırlamıyorsanız, genellikle yönlendiricinin üzerindeki bir düğmeye basarak parolayı sıfırlayabilirsiniz, ancak bu işlemi seçerseniz yönlendiricinin tüm yapılandırmasını kaybedebileceğinizi unutmayın. Yönlendiricinizin kurulumu için bir uygulama gerekiyorsa, lütfen uygulamayı telefonunuza veya bilgisayarınıza yükleyin ve yönlendiricinin ayarlarına erişmek için bu uygulamayı kullanın.",
"install_devices_router_list_2":"DHCP/DNS ayarlarını bulun. DNS satırlarını arayın, genelde iki veya üç tanedir, üç rakam girilebilen dört ayrı grup içeren satırdır.",
"install_devices_router_list_3":"AdGuard Home sunucu adreslerinizi oraya girin.",
"install_devices_router_list_4":"Bazı yönlendirici türlerinde özel bir DNS sunucusu ayarlanamaz. Bu durumda, AdGuard Home'u <0>DHCP sunucusu</0> olarak ayarlamak yardımcı olabilir. Aksi takdirde, yönlendirici modeliniz için DNS sunucularını nasıl ayarlayacağınız konusunda yönlendirici kılavuzuna bakmalısınız.",
"install_devices_router_list_4":"Bazı yönlendirici türlerinde özel bir DNS sunucusu yapılandırılamaz. Bu durumda, AdGuard Home'u bir <0>DHCP sunucusu</0> olarak yapılandırmak yardımcı olabilir. Aksi takdirde, yönlendirici modelinizde DNS sunucularını nasıl özelleştireceğinizi öğrenmek için yönlendirici kılavuzunu kontrol etmelisiniz.",
"install_devices_windows_list_1":"Başlat menüsünden veya Windows araması aracılığıyla Denetim Masası'nı açın.",
"install_devices_windows_list_2":"Ağ ve İnternet kategorisine girin ve ardından Ağ ve Paylaşım Merkezi'ne girin.",
"install_devices_ios_list_2":"Sol menüde bulunan Wi-Fi bölümüne girin (telefon ağlar için özel DNS sunucusu ayarlanamaz).",
"install_devices_ios_list_3":"O anda aktif olan ağın adına dokunun.",
"install_devices_ios_list_4":"DNS alanına AdGuard Home sunucunuzun adreslerini girin.",
"get_started":"Başlayın",
"get_started":"Başla",
"next":"Sonraki",
"open_dashboard":"Panoyu Aç",
"install_saved":"Başarıyla kaydedildi",
@@ -452,14 +455,14 @@
"settings_global":"Genel",
"settings_custom":"Özel",
"table_client":"İstemci",
"table_name":"AdAdı",
"table_name":"Ad",
"save_btn":"Kaydet",
"client_add":"İstemci Ekle",
"client_new":"Yeni İstemci",
"client_edit":"İstemciyi Düzenle",
"client_identifier":"Tanımlayıcı",
"ip_address":"IP adresi",
"client_identifier_desc":"İstemciler IP adresleri, CIDR, MAC adresleri veya ClientID (DoT/DoH/DoQ için kullanılabilir) ile tanımlanabilir. İstemcileri nasıl tanımlayacağınız hakkında daha fazla bilgiyi <0>buradan</0> edinebilirsiniz.",
"client_identifier_desc":"İstemciler, IP adresi, CIDR, MAC adresi veya ClientID (DoT/DoH/DoQ için kullanılabilir) ile tanımlanabilir. İstemcileri nasıl tanımlayacağınız hakkında daha fazla bilgiye <0>buradan</0> ulaşabilirsiniz.",
"form_enter_ip":"IP girin",
"form_enter_subnet_ip":"\"{{cidr}}\" alt ağına bir IP adresi girin",
"auto_clients_title":"Çalışma zamanı istemcileri",
"auto_clients_desc":"AdGuard Home'u kullanan veya kullanabilecek cihazların IP adresleri hakkında bilgiler. Bu bilgiler, hosts dosyaları, ters DNS, vb. dahil olmak üzere çeşitli kaynaklardan toplanır.",
"auto_clients_desc":"AdGuard Home'u kullanan veya kullanabilecek cihazların IP adresleri hakkında bilgiler. Bu bilgiler, ana bilgisayar dosyaları, ters DNS sorguları ve çeşitli diğer kaynaklardan toplanmaktadır.",
"access_title":"Erişim ayarları",
"access_desc":"AdGuard Home DNS sunucusu için erişim kurallarını buradan yapılandırabilirsiniz",
"access_allowed_title":"İzin verilen istemciler",
@@ -598,12 +601,12 @@
"disable_ipv6":"IPv6 adreslerinin çözümlenmesini devre dışı bırak",
"disable_ipv6_desc":"IPv6 adresleri için tüm DNS sorgularını bırakın (AAAA yazın) ve HTTPS yanıtlarından IPv6 ipuçlarını kaldırın.",
"fastest_addr":"En hızlı IP adresi",
"fastest_addr_desc":"Tüm DNS sunucularını sorgulayın ve tüm yanıtlar arasından en hızlı olan IP adresini döndürün. AdGuard Home'un tüm DNS sunucularından yanıt beklemesi gerektiği için DNS sorgularını yavaşlatır, ancak genel bağlantıyı iyileştirir.",
"fastest_addr_desc":"<b>Tüm</b> DNS sunucularından yanıt bekler, her sunucu için TCP bağlantı hızını ölçer ve en hızlı bağlantı hızına sahip sunucunun IP adresini döndürür.<br/>Bu yapılandırma, bir veya daha fazla üst kaynak sunucusu yanıt vermediğinde, DNS sorgularını önemli ölçüde yavaşlatabilir. Üst kaynak sunucularınızın kararlı olduğundan ve üst kaynak zaman aşım sürenizin düşük olduğundan emin olun.",
"autofix_warning_text":"\"Düzelt\" seçeneğine tıklarsanız, AdGuard Home, sisteminizi AdGuard Home DNS sunucusunu kullanacak şekilde yapılandırır.",
"autofix_warning_list":"Bu görevleri gerçekleştirir: <0>Sistem DNSStubListener'ı devre dışı bırakın</0> <0>DNS sunucusu adresini 127.0.0.1 olarak ayarlayın</0> <0>/etc/resolv.conf'un sembolik bağlantı hedefini /run/systemd/resolve/resolv.conf ile değiştirin<0> <0>DNSStubListener'ı durdurun (systemd çözümlenmiş hizmeti yeniden yükleyin)</0>",
"autofix_warning_result":"Sonuç olarak, sisteminizden gelen tüm DNS istekleri varsayılan olarak AdGuard Home tarafından işlenecektir.",
"tags_title":"Etiketler",
"tags_desc":"İstemciye karşılık gelen etiketleri seçebilirsiniz. Etiketleri daha kesin olarak uygulamak için filtreleme kurallarına dahil edin. <0>Daha fazla bilgi edinin</0>.",
"tags_desc":"İstemciyi tanımlayan etiketleri seçebilirsiniz. Filtreleme kurallarına etiketleri dahil ederek daha hassas bir şekilde uygulayabilirsiniz. <0>Daha fazla bilgi edinin</0>.",
"form_select_tags":"İstemci etiketlerini seçin",
"check_title":"Filtrelemeyi denetleyin",
"check_desc":"Ana makine adının filtreleme durumunu kontrol edin.",
@@ -624,11 +627,11 @@
"client_blocked":"\"{{ip}}\" istemcisi başarıyla engellendi",
"client_unblocked":"\"{{ip}}\" istemcinin engellemesi başarıyla kaldırıldı",
"static_ip":"Sabit IP adresi",
"static_ip_desc":"AdGuard Home bir sunucudur, bu nedenle düzgün çalışması için sabit bir IP adresine ihtiyacı vardır. Aksi takdirde, yönlendiriciniz bir zaman sonra bu cihaza farklı bir IP adresi atayabilir.",
"static_ip_desc":"AdGuard Home bir sunucudur, bu nedenle düzgün çalışabilmesi için sabit bir IP adresine ihtiyaç duyar. Aksi takdirde, yönlendiriciniz bu cihaza farklı bir IP adresi atayabilir.",
"set_static_ip":"Sabit IP adresi ayarla",
"install_static_ok":"Güzel haber! Sabit IP adresi zaten yapılandırılmış",
"install_static_error":"AdGuard Home, bu ağ arayüzü için otomatik olarak yapılandıramıyor. Lütfen bunu elle nasıl yapacağınızla ilgili talimatlara bakın.",
"install_static_configure":"AdGuard Home, <0>{{ip}}</0> dinamik IP adresinin kullanıldığını tespit etti. Sabit adresiniz olarak ayarlanmasını ister misiniz?",
"install_static_configure":"AdGuard Home, <0>{{ip}}</0> sabit IP adresinin kullanıldığını tespit etti. Sabit adresiniz olarak ayarlanmasını ister misiniz?",
"confirm_static_ip":"AdGuard Home, {{ip}} adresini sabit IP adresiniz olacak şekilde yapılandırır. Devam etmek istiyor musunuz?",
"list_updated":"{{count}} liste güncellendi",
"list_updated_plural":"{{count}} liste güncellendi",
@@ -707,8 +710,8 @@
"custom_rotation_input":"Rotasyonu saat cinsinden girin",
"protection_section_label":"Koruma",
"log_and_stats_section_label":"Sorgu günlüğü ve istatistikler",
"ignore_query_log":"Sorgu günlüğünde bu istemciyi yoksay",
"ignore_statistics":"İstatistiklerde bu istemciyi yoksay",
"ignore_query_log":"Sorgu günlüğünde bu istemciyi gösterme",
"ignore_statistics":"İstatistiklerde bu istemciyi gösterme",
"resolve_clients_title":"Увімкнути зворотне вирішення IP-адрес клієнтів",
"resolve_clients_desc":"Визначати доменні імена клієнтів за допомогою PTR-запитів до відповідних серверів — приватних DNS-серверів для локальних клієнтів та upstream-серверів для клієнтів з публічними IP-адресами.",
"use_private_ptr_resolvers_desc":"Надсилати зворотні DNS-запити до вказаних серверів для клієнтів, що обслуговуються локально. Якщо вимкнено, AdGuard Home буде відповідати NXDOMAIN на всі такі PTR-запити, окрім запитів про клієнтів, що уже відомі завдяки DHCP, /etc/hosts тощо.",
"use_private_ptr_resolvers_desc":"Розвʼязувати запити PTR, SOA та NS для доменів ARPA, що містять приватні IP-адреси, через приватні вихідні сервери, DHCP, /etc/hosts тощо. Якщо вимкнено, AdGuard Home відповідатиме на всі такі запити з NXDOMAIN.",
"check_dhcp_servers":"Перевірити DHCP-сервери",
"save_config":"Зберегти конфігурацію",
"enabled_dhcp":"DHCP-сервер увімкнено",
@@ -68,7 +68,7 @@
"ip":"IP",
"dhcp_table_hostname":"Назва вузла",
"dhcp_table_expires":"Закінчується",
"dhcp_warning":"Якщо ви однаково хочете увімкнути DHCP-сервер, переконайтеся, що у вашій мережі немає інших активних DHCP-серверів. Інакше, це може порушити роботу інтернету на під'єднаних пристроях!",
"dhcp_warning":"Якщо ви однаково хочете увімкнути DHCP-сервер, переконайтеся, що у вашій мережі немає інших активних DHCP-серверів. Інакше, це може порушити роботу інтернету на підʼєднаних пристроях!",
"dhcp_error":"AdGuard Home не зміг визначити, чи є в мережі інший DHCP-сервер",
"dhcp_static_ip_error":"Для використання DHCP-сервера необхідно встановити статичну IP-адресу. Нам не вдалося визначити, чи цей мережевий інтерфейс налаштовано для використання статичної IP-адреси. Встановіть статичну IP-адресу вручну.",
"dhcp_dynamic_ip_found":"Ваша система використовує конфігурацію з динамічною IP-адресою для інтерфейсу <0>{{interfaceName}}</0>. Для використання DHCP-сервера необхідно встановити статичну IP-адресу. Ваша поточна IP-адреса <0>{{ipAddress}}</0>. Ми автоматично встановимо цю IP-адресу як статичну, якщо ви натиснете кнопку «Увімкнути DHCP-сервер».",
@@ -343,10 +343,10 @@
"known_tracker":"Відомі трекери",
"install_welcome_title":"Вітаємо в AdGuard Home!",
"install_welcome_desc":"AdGuard Home — це мережевий DNS-сервер, що блокує рекламу та відстеження. Його мета — надати вам контроль над усією мережею та всіма пристроями в ній без потреби використання програми на стороні клієнта.",
"install_settings_interface_link":"Веб-інтерфейс адміністратора AdGuard Home буде доступний за такими адресами:",
"install_settings_interface_link":"Вебінтерфейс адміністратора AdGuard Home буде доступний за такими адресами:",
"form_error_port":"Уведіть правильне значення порту",
"install_settings_dns":"DNS-сервер",
"install_settings_dns_desc":"Вам потрібно буде налаштувати свої пристрої або маршрутизатор для використання DNS-сервера за такими адресами:",
@@ -364,7 +364,7 @@
"install_submit_title":"Вітаємо!",
"install_submit_desc":"Процедура налаштування завершена і тепер все готово, аби почати користуватися AdGuard Home.",
"install_devices_router":"Роутер",
"install_devices_router_desc":"Це налаштування буде автоматично охоплювати всі пристрої, що під'єднано до домашнього маршрутизатора. Вам не потрібно буде налаштовувати кожен з них вручну.",
"install_devices_router_desc":"Це налаштування буде автоматично охоплювати всі пристрої, що підʼєднано до домашнього маршрутизатора. Вам не потрібно буде налаштовувати кожен з них вручну.",
"install_devices_address":"DNS-сервер AdGuard Home прослуховує наступні адреси",
"install_devices_router_list_1":"Відкрийте налаштування маршрутизатора. Зазвичай ви можете отримати до нього доступ із браузера за допомогою URL-адреси, наприклад, http://192.168.0.1/ або http://192.168.1.1/. Можливо, треба буде ввести пароль. Якщо ви його не знаєте, часто можна скинути пароль, натиснувши кнопку на самому маршрутизаторі. Для деяких маршрутизаторів потрібна спеціальна програма, яка в такому випадку повинна бути вже встановлена на вашому комп’ютері чи телефоні.",
"install_devices_router_list_2":"Знайдіть налаштування DHCP/DNS. Шукайте літери DNS поруч із полем, в яке можна ввести два або три набори чисел, кожен з яких розбитий на чотири групи від однієї до трьох цифр.",
@@ -448,7 +448,7 @@
"manual_update":"Щоб оновити самостійно, <a>виконайте ці кроки</a>.",
"processing_update":"Зачекайте будь ласка, AdGuard Home оновлюється",
"clients_title":"Постійні клієнти",
"clients_desc":"Налаштуйте пристрої, під'єднані до AdGuard Home",
"clients_desc":"Налаштуйте пристрої, які підʼєднано до AdGuard Home",
"upstream_parallel":"Sử dụng truy vấn song song để tăng tốc độ giải quyết bằng cách truy vấn đồng thời tất cả các máy chủ ngược tuyến",
"parallel_requests":"Yêu cầu song song",
"load_balancing":"Cân bằng tải",
"load_balancing_desc":"Chỉ truy xuất một máy chủ trong cùng thời điểm. AdGuard Home sẽ sử dụng thuật toán trọng số ngẫu nhiên để chọn một máy chủ nhanh nhất và sử dụng máy chủ đó thường xuyên hơn.",
"load_balancing_desc":"Truy vấn một máy chủ thượng nguồn tại một thời điểm. AdGuard Home sử dụng thuật toán ngẫu nhiên có trọng số để chọn máy chủ có số lần tìm kiếm không thành công thấp nhất và thời gian tìm kiếm trung bình thấp nhất.",
"bootstrap_dns":"Máy chủ DNS Bootstrap",
"bootstrap_dns_desc":"Địa chỉ IP của máy chủ DNS được sử dụng để phân giải địa chỉ IP của trình phân giải DoH/DoT mà bạn chỉ định làm thượng nguồn. Bình luận không được phép.",
"fallback_dns_title":"Máy chủ DNS dự phòng",
"fallback_dns_desc":"Danh sách máy chủ DNS dự phòng được sử dụng khi máy chủ DNS ngược tuyến không phản hồi. Cú pháp tương tự như trong trường ngược dòng chính ở trên.",
"fallback_dns_placeholder":"Nhập một máy chủ DNS dự phòng trên mỗi dòng",
"local_ptr_title":"Máy chủ DNS riêng tư",
"local_ptr_desc":"Máy chủ DNS hoặc các máy chủ mà AdGuard Home sẽ sử dụng cho các truy vấn về tài nguyên được phân phối cục bộ. Ví dụ: máy chủ này sẽ được sử dụng để phân giải tên máy khách của máy khách cho các máy khách có địa chỉ IP riêng. Nếu không được cài đặt, AdGuard Home sẽ tự động sử dụng trình phân giải DNS mặc định của bạn.",
"local_ptr_desc":"Máy chủ DNS được AdGuard Home sử dụng cho các yêu cầu PTR, SOA và NS riêng tư. Một yêu cầu được coi là riêng tư nếu nó yêu cầu một miền ARPA chứa một mạng con trong phạm vi IP riêng tư (chẳng hạn như \"192.168.12.34\") và đến từ một máy khách có địa chỉ IP riêng tư. Nếu không được thiết lập, các trình phân giải DNS mặc định của hệ điều hành của bạn sẽ được sử dụng, ngoại trừ các địa chỉ IP của AdGuard Home.",
"local_ptr_default_resolver":"Theo mặc định, AdGuard Home sử dụng các hệ thống phân giải tên miền ngược sau: {{ip}}.",
"local_ptr_no_default_resolver":"AdGuard Home không thể xác định hệ thống phân giải tên miền ngược riêng phù hợp cho hệ thống này.",
"local_ptr_placeholder":"Nhập một địa chỉ IP trên mỗi dòng",
"resolve_clients_title":"Kích hoạt cho phép phân giải ngược về địa chỉ IP của máy khách",
"resolve_clients_desc":"Nếu được bật, AdGuard Home sẽ cố gắng phân giải ngược lại địa chỉ IP của khách hàng thành tên máy chủ của họ bằng cách gửi các truy vấn PTR tới trình phân giải tương ứng (máy chủ DNS riêng cho máy khách cục bộ, máy chủ ngược dòng cho máy khách có địa chỉ IP công cộng).",
"use_private_ptr_resolvers_title":"Sử dụng trình rDNS riêng tư",
"use_private_ptr_resolvers_desc":"Thực hiện tra cứu ngược DNS cho các địa chỉ được phân phối cục bộ bằng cách sử dụng các máy chủ nguồn. Nếu bị vô hiệu hóa, AdGuard Home sẽ phản hồi với NXDOMAIN cho tất cả các yêu cầu PTR ngoại trừ các ứng dụng khách được biết đến bởi DHCP, / etc / hosts, v. v.",
"use_private_ptr_resolvers_desc":"Giải quyết các yêu cầu PTR, SOA và NS cho các miền ARPA chứa địa chỉ IP riêng thông qua máy chủ thượng nguồn riêng, DHCP, /etc/hosts, v. v. Nếu bị vô hiệu hóa, AdGuard Home sẽ phản hồi tất cả các yêu cầu đó bằng NXDOMAIN.",
"check_dhcp_servers":"Kiểm tra máy chủ DHCP",
"save_config":"Lưu thiết lập",
"enabled_dhcp":"Máy chủ DHCP đã kích hoạt",
@@ -154,7 +154,7 @@
"use_adguard_parental":"Sử dụng dịch vụ quản lý của phụ huynh AdGuard",
"use_adguard_parental_hint":"AdGuard Home sẽ kiểm tra nếu tên miền chứa từ khoá người lớn. Tính năng sử dụng API thân thiện với quyền riêng tư tương tự với dịch vụ bảo vệ duyệt web",
"enforce_safe_search":"Bắt buộc tìm kiếm an toàn",
"enforce_save_search_hint":"AdGuard Home có thể bắt buộc tìm kiếm an toàn với các dịch vụ tìm kiếm: Google, Youtube, Bing, Yandex.",
"enforce_save_search_hint":"AdGuard Home sẽ thực thi tìm kiếm an toàn trong các công cụ tìm kiếm sau: Google, YouTube, Bing, DuckDuckGo, Ecosia, Yandex, Pixabay.",
"no_servers_specified":"Không có máy chủ nào được liệt kê",
"general_settings":"Cài đặt chung",
"dns_settings":"Cài đặt DNS",
@@ -425,6 +425,9 @@
"encryption_hostnames":"Tên máy chủ",
"encryption_reset":"Bạn có chắc chắn muốn đặt lại cài đặt mã hóa?",
"encryption_warning":"Cảnh báo",
"encryption_plain_dns_enable":"Kích hoạt DNS đơn giản",
"encryption_plain_dns_desc":"DNS đơn giản được bật theo mặc định. Bạn có thể vô hiệu hóa nó để buộc tất cả các thiết bị sử dụng DNS được mã hóa. Để thực hiện việc này, bạn phải kích hoạt ít nhất một giao thức DNS được mã hóa",
"encryption_plain_dns_error":"Để tắt DNS đơn giản, hãy bật ít nhất một giao thức DNS được mã hóa",
"topline_expiring_certificate":"Chứng chỉ SSL của bạn sắp hết hạn. Cập nhật <0>Cài đặt mã hóa</0>.",
"topline_expired_certificate":"Chứng chỉ SSL của bạn đã hết hạn. Cập nhật <0>Cài đặt mã hóa</0>.",
"form_error_port_range":"Nhập giá trị cổng trong phạm vi 80-65535",
@@ -675,7 +678,7 @@
"use_saved_key":"Sử dụng khóa đã lưu trước đó",
"parental_control":"Quản lý của phụ huynh",
"safe_browsing":"Duyệt web an toàn",
"served_from_cache":"{{value}} <i>(được phục vụ từ bộ nhớ cache)</i>",
"served_from_cache_label":"Được phục vụ từ bộ nhớ đệm",
"form_error_password_length":"Mật khẩu phải dài từ {{min}} đến {{max}} ký tự",
"anonymizer_notification":"<0> Lưu ý:</0> Tính năng ẩn danh IP được bật. Bạn có thể tắt nó trong <1> Cài đặt chung</1>.",
"confirm_dns_cache_clear":"Bạn có chắc chắn muốn xóa bộ đệm ẩn DNS không?",
"load_balancing_desc":"一次查询一台服务器。AdGuard Home 将使用加权随机算法来选择服务器,以便更常使用最快的服务器。",
"load_balancing_desc":"一次查询一台上游服务器。<br/>AdGuard Home 使用加权随机算法来选择具有最少失败查找和最低平均查找时间的服务器。",
"bootstrap_dns":"Bootstrap DNS 服务器",
"bootstrap_dns_desc":"DNS 服务器的 IP 地址,用于解析指定为上游的 DoH/DoT 解析器的 IP 地址。不允许添加注释。",
"fallback_dns_title":"后备 DNS 服务器",
"fallback_dns_desc":"当上游 DNS 服务器没有响应时使用的后备 DNS 服务器列表。语法与上面的「主要上游」字段相同。",
"fallback_dns_placeholder":"每行输入一个后备 DNS 服务器",
"local_ptr_title":"私人反向 DNS 服务器",
"local_ptr_desc":"AdGuard Home 用于本地 PTR 查询的 DNS 服务器。这些服务器将使用反向 DNS 解析具有私人 IP 地址的客户机的主机名,比如 \"192.168.12.34\"。如果没有设置,除非是 AdGuard Home 里设置的地址,AdGuard Home 都将自动使用您的操作系统的默认 DNS 解析器。",
"local_ptr_desc":"AdGuard Home 用于私人 PTR、SOA 和 NS 请求的 DNS 服务器。如果请求的 ARPA 域名包含私有 IP 范围内的子网(如 \"192.168.12.34\"),且请求来自具有私有 IP 地址的客户端,该请求被视为私有请求。如果未设置,将使用操作系统的默认 DNS 解析器,AdGuard Home IP 地址除外。",
"local_ptr_default_resolver":"AdGuard Home 默认使用下列反向 DNS 解析器: {{ip}}",
"local_ptr_no_default_resolver":"AdGuard Home 无法为这个系统确定合适的私人反向 DNS 解析器。",
"local_ptr_placeholder":"每行输入一个 IP 地址",
"resolve_clients_title":"启用客户端的 IP 地址的反向解析",
"resolve_clients_desc":"通过发送 PTR 查询到对应的解析器 (本地客户端的私人 DNS 服务器,公共 IP 客户端的上游服务器) 将 IP 地址反向解析成其客户端主机名。",
"use_private_ptr_resolvers_title":"使用私人反向 DNS 解析器",
"use_private_ptr_resolvers_desc":"使用这些上游服务器对本地服务的地址执行反向 DNS 查找。 如果禁用,则 AdGuard Home 会以 NXDOMAIN 响应所有此类 PTR 请求,从 DHCP、/etc/hosts 等获知的客户端除外。",
"use_private_ptr_resolvers_desc":"使用私有上游服务器、DHCP、/etc/hosts 等解决包含私有 IP 地址的 ARPA 域名的 PTR、SOA 和 NS 请求。如果禁用,AdGuard Home 将以 NXDOMAIN 回应所有此类请求。",
"check_dhcp_servers":"检查 DHCP 服务器",
"save_config":"保存配置",
"enabled_dhcp":"DHCP 服务器已启用",
@@ -154,7 +154,7 @@
"use_adguard_parental":"使用 AdGuard 【家长控制】服务",
"use_adguard_parental_hint":"AdGuard Home 将使用与浏览安全服务相同的隐私性强的 API 来检查域名指向的网站是否包含成人内容。",
"enforce_safe_search":"使用安全搜索",
"enforce_save_search_hint":"AdGuard Home 对以下搜索引擎可强制启用安全搜索:Google、YouTube、Bing、DuckDuckGo、Yandex、Pixabay。",
"enforce_save_search_hint":"AdGuard Home 将会在下列搜索引擎中强制启用安全搜索:Google、YouTube、Bing、DuckDuckGo、Ecosia、Yandex、Pixabay。",
"load_balancing_desc":"每次查詢一個上游伺服器。AdGuard Home 使用它的加權隨機的演算法來選擇伺服器,以便最快的伺服器被更常使用。",
"load_balancing_desc":"一次查詢一台上游伺服器。<br/>AdGuard Home 使用加權隨機演算法來選擇具有最少失敗查詢和最低平均查詢時間的伺服器。",
"bootstrap_dns":"自我啟動(Bootstrap)DNS 伺服器",
"bootstrap_dns_desc":"DNS 伺服器的 IP 位址,用於解析您指定為上游伺服器的 DoH/DoT 解析器的 IP 位址。不允許註釋。",
"fallback_dns_title":"應變 DNS 伺服器",
"fallback_dns_desc":"當上游 DNS 伺服器未回覆時被使用的應變 DNS 伺服器之清單。此語法與在上面主要上游欄位中的相同。",
"fallback_dns_placeholder":"每行輸入一個應變 DNS 伺服器",
"local_ptr_title":"私人反向的 DNS 伺服器",
"local_ptr_desc":"AdGuard Home 用於區域指標(PTR)查詢之 DNS 伺服器。這些伺服器被用於解析有關在私人 IP 範圍的位址之區域指標查詢,例如,\"192.168.12.34\",使用反向的 DNS。如果未被設定,AdGuard Home 使用您的作業系統之預設 DNS 解析器的位址。",
"local_ptr_desc":"AdGuard Home 使用的 DNS 伺服器用於私人 PTR、SOA 和 NS 請求。如果請求要求包含私人 IP 範圍內的子網域的 ARPA 網域(例如\"192.168.12.34\"),並來自具有私人 IP 位址的用戶端,該請求被視為私人。如果未設定,將使用您的作業系統的預設 DNS 解析器,但不包括 AdGuard Home 的 IP 位址。",
"local_ptr_default_resolver":"預設下,AdGuard Home 使用以下反向的 DNS 解析器:{{ip}}。",
"local_ptr_no_default_resolver":"AdGuard Home 無法為此系統決定合適的私人反向的 DNS 解析器。",
"local_ptr_placeholder":"每行輸入一個 IP 位址",
"resolve_clients_title":"啟用用戶端的 IP 位址之反向的解析",
"resolve_clients_desc":"透過傳送指標(PTR)查詢到對應的解析器(私人 DNS 伺服器供區域的用戶端,上游的伺服器供有公共 IP 位址的用戶端),反向地解析用戶端的 IP 位址變為它們的主機名稱。",
"use_private_ptr_resolvers_title":"使用私人反向的 DNS 解析器",
"use_private_ptr_resolvers_desc":"對於正使用這些上游伺服器之區域服務的位址執行反向的 DNS 查找。如果被禁用,除已知來自 DHCP、/etc/hosts 等等的用戶端之外,AdGuard Home 對於所有此類的區域指標(PTR)請求以 NXDOMAIN 回覆。",
"use_private_ptr_resolvers_desc":"使用私人上游伺服器、DHCP、/etc/hosts 等方式解析包含私人 IP 位址的 ARPA 網域的 PTR、SOA 和 NS 請求。如果停用,AdGuard Home 將對所有此類請求以 NXDOMAIN 回應。",
"check_dhcp_servers":"檢查動態主機設定協定(DHCP)伺服器",
"save_config":"儲存配置",
"enabled_dhcp":"動態主機設定協定(DHCP)伺服器被啟用",
"disabled_dhcp":"動態主機設定協定(DHCP)伺服器被禁用",
"disabled_dhcp":"DHCP伺服器已停用",
"unavailable_dhcp":"DHCP 為不可用的",
"unavailable_dhcp_desc":"AdGuard Home 無法於您的作業系統上執行 DHCP 伺服器",
@@ -88,7 +97,6 @@ class Rewrites extends Component {
handleSubmit={this.handleSubmit}
processingAdd={processingAdd}
processingDelete={processingDelete}
processingUpdate={processingUpdate}
currentRewrite={currentRewrite}
/>
</Fragment>
@@ -98,14 +106,4 @@ class Rewrites extends Component {
}
}
Rewrites.propTypes={
t: PropTypes.func.isRequired,
getRewritesList: PropTypes.func.isRequired,
toggleRewritesModal: PropTypes.func.isRequired,
addRewrite: PropTypes.func.isRequired,
deleteRewrite: PropTypes.func.isRequired,
updateRewrite: PropTypes.func.isRequired,
rewrites: PropTypes.object.isRequired,
};
exportdefaultwithTranslation()(Rewrites);
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.