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
If you want to contribute to AdGuard Home by filing or commenting on an issue or opening a pull request, please follow the instructions below.
## General recommendations
Please don’t:
- post comments like “+1” or “this”. Use the :+1: reaction on the issue instead, as this allows us to actually see the level of support for issues.
- file issues about localization errors or send localization updates as PRs. We’re using [CrowdIn] to manage our translations and we generally update them before each Beta and Release build. You can learn more about translating AdGuard products [in our Knowledge Base][kb-trans].
- file issues about a particular filtering-rule list misbehaving. These are tracked through the [separate form for filtering issues][form].
- send or request updates to filtering-rule lists, such as the ones for the Blocked Services feature or the list of approved filtering-rule lists. We update them from the [separate repository][hostlist] once before each Beta and Release build.
Please do:
- follow the template instructions and provide data for reproducing issues.
- write the title of your issue or pull request in English. Any language is fine in the body, but it is important to keep the title in English to make it easier for people and bots to look up duplicated issues.
Please make sure that the issue is not a duplicate or a question. If it’s a duplicate, please react to the original issue with a thumbs up. If it’s a question, please look through our [Wiki] and, if you haven’t found the answer, post it to the GitHub [Discussions] page.
Developers need to be able to reproduce the faulty behavior in order to fix an issue, so please make sure that you follow the instructions in the issue template carefully.
## Pull requests
### Discuss your changes first
Please discuss your changes by opening an issue. The maintainers should evaluate your proposal, and it’s generally better if that’s done before any code is written.
### Review your changes for style
We have a set of [code guidelines][hacking] that we expect the code to follow. Please make sure you follow it.
Make sure that it passes linters and tests by running the corresponding Make targets. For backend changes, it’s `make go-check`. For frontend, run `make js-lint`.
Additionally, a manual test is often required. While we’re constantly working on improving our test suites, they’re still not as good as we’d like them to be.
This document was moved to the [AdGuard Code Guidelines repository][repo]. All
sections with IDs now only have links to the corresponding files and sections in
that repository.
This document was moved to the [AdGuard Code Guidelines repository][repo]. All sections with IDs now only have links to the corresponding files and sections in that repository.
## <a href="#git" id="git" name="git">Git</a>
## <a href="#git" id="git" name="git">Git</a>
This section was moved to [its own document][git].
AdGuard Home is a network-wide software for blocking ads and tracking. After you
set it up, it'll cover ALL your home devices, and you don't need any client-side
software for that.
AdGuard Home is a network-wide software for blocking ads and tracking. After you set it up, it'll cover ALL your home devices, and you don't need any client-side software for that.
It operates as a DNS server that re-routes tracking domains to a “black hole”,
thus preventing your devices from connecting to those servers. It's based on
software we use for our public [AdGuard DNS] servers, and both share a lot of
code.
It operates as a DNS server that re-routes tracking domains to a “black hole”, thus preventing your devices from connecting to those servers. It's based on software we use for our public [AdGuard DNS] servers, and both share a lot of code.
Please read the **[Getting Started][wiki-start]** article on our Wiki to learn how to install AdGuard Home manually, and how to configure your devices to use it.
If you want to integrate with AdGuard Home, you can use our [REST API][openapi].
Alternatively, you can use this [python client][pyclient], which is used to
build the [AdGuard Home Hass.io Add-on][hassio].
If you want to integrate with AdGuard Home, you can use our [REST API][openapi]. Alternatively, you can use this [python client][pyclient], which is used to build the [AdGuard Home Hass.io Add-on][hassio].
## <a href="#comparison" id="comparison" name="comparison">Comparing AdGuard Home to other solutions</a>
### <a href="#comparison-adguard-dns" id="comparison-adguard-dns" name="comparison-adguard-dns">How is this different from public AdGuard DNS servers?</a>
## <a href="#comparison" id="comparison" name="comparison">Comparing AdGuard Home to other solutions</a>
Running your own AdGuard Home server allows you to do much more than using a public DNS server. It's a completely different level. See for yourself:
### <a href="#comparison-adguard-dns" id="comparison-adguard-dns" name="comparison-adguard-dns">How is this different from public AdGuard DNS servers?</a>
- Choose what exactly the server blocks and permits.
Running your own AdGuard Home server allows you to do much more than using a
public DNS server. It's a completely different level. See for yourself:
- Monitor your network activity.
* Choose what exactly the server blocks and permits.
- Add your own custom filtering rules.
* Monitor your network activity.
- **Most importantly, it's your own server, and you are the only one who's in control.**
* Add your own custom filtering rules.
### <a href="#comparison-pi-hole" id="comparison-pi-hole" name="comparison-pi-hole">How does AdGuard Home compare to Pi-Hole</a>
* **Most importantly, it's your own server, and you are the only one who's in
control.**
At this point, AdGuard Home has a lot in common with Pi-Hole. Both block ads and trackers using the so-called “DNS sinkholing” method and both allow customizing what's blocked.
> [!NOTE]
> We're not going to stop here. DNS sinkholing is not a bad starting point, but this is just the beginning.
AdGuard Home provides a lot of features out-of-the-box with no need to install and configure additional software. We want it to be simple to the point when even casual users can set it up with minimal effort.
### <a href="#comparison-pi-hole" id="comparison-pi-hole" name="comparison-pi-hole">How does AdGuard Home compare to Pi-Hole</a>
At this point, AdGuard Home has a lot in common with Pi-Hole. Both block ads
and trackers using the so-called “DNS sinkholing” method and both allow
customizing what's blocked.
<aside>
We're not going to stop here. DNS sinkholing is not a bad starting point, but
this is just the beginning.
</aside>
AdGuard Home provides a lot of features out-of-the-box with no need to install
and configure additional software. We want it to be simple to the point when
even casual users can set it up with minimal effort.
**Disclaimer:** some of the listed features can be added to Pi-Hole by
installing additional software or by manually using SSH terminal and
reconfiguring one of the utilities Pi-Hole consists of. However, in our
opinion, this cannot be legitimately counted as a Pi-Hole's feature.
> [!NOTE]
> Some of the listed features can be added to Pi-Hole by installing additional software or by manually using SSH terminal and reconfiguring one of the utilities Pi-Hole consists of. However, in our opinion, this cannot be legitimately counted as a Pi-Hole's feature.
### <a href="#comparison-adblock" id="comparison-adblock" name="comparison-adblock">How does AdGuard Home compare to traditional ad blockers</a>
### <a href="#comparison-adblock" id="comparison-adblock" name="comparison-adblock">How does AdGuard Home compare to traditional ad blockers</a>
It depends.
DNS sinkholing is capable of blocking a big percentage of ads, but it lacks
the flexibility and the power of traditional ad blockers. You can get a good
impression about the difference between these methods by reading [this
article][blog-adaway], which compares AdGuard for Android (a traditional ad
blocker) to hosts-level ad blockers (which are almost identical to DNS-based
blockers in their capabilities). This level of protection is enough for some
users.
DNS sinkholing is capable of blocking a big percentage of ads, but it lacks the flexibility and the power of traditional ad blockers. You can get a good impression about the difference between these methods by reading [this article][blog-adaway], which compares AdGuard for Android (a traditional ad blocker) to hosts-level ad blockers (which are almost identical to DNS-based blockers in their capabilities). This level of protection is enough for some users.
Additionally, using a DNS-based blocker can help to block ads, tracking and
analytics requests on other types of devices, such as SmartTVs, smart speakers
or other kinds of IoT devices (on which you can't install traditional ad
blockers).
Additionally, using a DNS-based blocker can help to block ads, tracking and analytics requests on other types of devices, such as SmartTVs, smart speakers or other kinds of IoT devices (on which you can't install traditional ad blockers).
Here are some examples of what cannot be blocked by a DNS-level blocker:
* YouTube, Twitch ads;
- YouTube, Twitch ads;
* Facebook, Twitter, Instagram sponsored posts.
- Facebook, Twitter, Instagram sponsored posts.
Essentially, any advertising that shares a domain with content cannot be blocked
by a DNS-level blocker.
Essentially, any advertising that shares a domain with content cannot be blocked by a DNS-level blocker.
Is there a chance to handle this in the future? DNS will never be enough to do
this. Our only option is to use a content blocking proxy like what we do in the
standalone AdGuard applications. We're [going to bring][issue-1228] this
feature support to AdGuard Home in the future. Unfortunately, even in this
case, there still will be cases when this won't be enough or would require quite
a complicated configuration.
Is there a chance to handle this in the future? DNS will never be enough to do this. Our only option is to use a content blocking proxy like what we do in the standalone AdGuard applications. We're [going to bring][issue-1228] this feature support to AdGuard Home in the future. Unfortunately, even in this case, there still will be cases when this won't be enough or would require quite a complicated configuration.
**NOTE:** 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`.
> [!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`.
Check the [`Makefile`][src-makefile] to learn about other commands.
#### <a href="#building-cross" id="building-cross" name="building-cross">Building for a different platform</a>
#### <a href="#building-cross" id="building-cross" name="building-cross">Building for a different platform</a>
You can build AdGuard Home for any OS/ARCH that Go supports. In order to do
this, specify `GOOS` and `GOARCH` environment variables as macros when running
`make`.
You can build AdGuard Home for any OS/ARCH that Go supports. In order to do this, specify `GOOS` and `GOARCH` environment variables as macros when running `make`.
Run `make build-docker` to build the Docker image locally (the one that we
publish to DockerHub). Please note, that we're using [Docker Buildx][buildx] to
build our official image.
Run `make build-docker` to build the Docker image locally (the one that we publish to DockerHub). Please note, that we're using [Docker Buildx][buildx] to build our official image.
You may need to prepare before using these builds:
* (Linux-only) Install Qemu:
- (Linux-only) Install Qemu:
```sh
docker run --rm --privileged multiarch/qemu-user-static --reset -p yes --credential yes
```
```sh
docker run --rm --privileged multiarch/qemu-user-static --reset -p yes --credential yes
See the [`build-docker` target documentation][targ-docker].
#### <a href="#debugging-the-frontend" id="debugging-the-frontend" name="debugging-the-frontend">Debugging the frontend</a>
#### <a href="#debugging-the-frontend" id="debugging-the-frontend" name="debugging-the-frontend">Debugging the frontend</a>
When you need to debug the frontend without recompiling the production version
every time, for example to check how your labels would look on a form, you can
run the frontend build a development environment.
When you need to debug the frontend without recompiling the production version every time, for example to check how your labels would look on a form, you can run the frontend build a development environment.
1. In a separate terminal, run:
1. In a separate terminal, run:
```sh
( cd ./client/ && env NODE_ENV='development' npm run watch )
```
```sh
( cd ./client/ && env NODE_ENV='development' npm run watch )
```
2. Run your `AdGuardHome` binary with the `--local-frontend` flag, which
instructs AdGuard Home to ignore the built-in frontend files and use those
from the `./build/` directory.
2. Run your `AdGuardHome` binary with the `--local-frontend` flag, which instructs AdGuard Home to ignore the built-in frontend files and use those from the `./build/` directory.
3. Now any changes you make in the `./client/` directory should be recompiled
and become available on the web UI. Make sure that you disable the browser
cache to make sure that you actually get the recompiled version.
3. Now any changes you make in the `./client/` directory should be recompiled and become available on the web UI. Make sure that you disable the browser cache to make sure that you actually get the recompiled version.
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.
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.
Please note that we don't expect people to contribute to both UI and backend
parts of the program simultaneously. Ideally, the backend part is implemented
first, i.e. configuration, API, and the functionality itself. The UI part can
be implemented later in a different pull request by a different person.
Please note that we don't expect people to contribute to both UI and backend parts of the program simultaneously. Ideally, the backend part is implemented first, i.e. configuration, API, and the functionality itself. The UI part can be implemented later in a different pull request by a different person.
If you run into any problem or have a suggestion, head to [this page][iss] and
click on the “New issue” button. Please follow the instructions in the issue
form carefully and don't forget to start by searching for duplicates.
If you run into any problem or have a suggestion, head to [this page][iss] and click on the “New issue” button. Please follow the instructions in the issue form carefully and don't forget to start by searching for duplicates.
### <a href="#translate" id="translate" name="translate">Help with translations</a>
### <a href="#translate" id="translate" name="translate">Help with translations</a>
If you want to help with AdGuard Home translations, please learn more about
translating AdGuard products [in our Knowledge Base][kb-trans]. You can
contribute to the [AdGuardHome project on CrowdIn][crowdin].
If you want to help with AdGuard Home translations, please learn more about translating AdGuard products [in our Knowledge Base][kb-trans]. You can contribute to the [AdGuardHome project on CrowdIn][crowdin].
Another way you can contribute is by [looking for issues][iss-help] marked as
`help wanted`, asking if the issue is up for grabs, and sending a PR fixing the
bug or implementing the feature.
Another way you can contribute is by [looking for issues][iss-help] marked as `help wanted`, asking if the issue is up for grabs, and sending a PR fixing the bug or implementing the feature.
- [OpenWrt LUCI app](https://github.com/kongfl888/luci-app-adguardhome) by [@kongfl888](https://github.com/kongfl888) (originally by [@rufengsuixing](https://github.com/rufengsuixing)).
* [Prometheus exporter for AdGuard
Home](https://github.com/ebrianne/adguard-exporter) by
[@ebrianne](https://github.com/ebrianne).
- [AdGuardHome sync](https://github.com/bakito/adguardhome-sync) by [@bakito](https://github.com/bakito).
* [Terminal-based, real-time traffic monitoring and statistics for your AdGuard Home
instance](https://github.com/Lissy93/AdGuardian-Term) by
[@Lissy93](https://github.com/Lissy93)
- [Terminal-based, real-time traffic monitoring and statistics for your AdGuard Home instance](https://github.com/Lissy93/AdGuardian-Term) by [@Lissy93](https://github.com/Lissy93)
* [AdGuard Home on GLInet
routers](https://forum.gl-inet.com/t/adguardhome-on-gl-routers/10664) by
[Gl-Inet](https://gl-inet.com/).
- [AdGuard Home on GLInet routers](https://forum.gl-inet.com/t/adguardhome-on-gl-routers/10664) by [Gl-Inet](https://gl-inet.com/).
* [Cloudron app](https://git.cloudron.io/cloudron/adguard-home-app) by
[@gramakri](https://github.com/gramakri).
- [Cloudron app](https://git.cloudron.io/cloudron/adguard-home-app) by [@gramakri](https://github.com/gramakri).
Our main idea is that you are the one, who should be in control of your data.
So it is only natural, that AdGuard Home does not collect any usage statistics,
and does not use any web services unless you configure it to do so. See also
the [full privacy policy][privacy] with every bit that *could in theory be sent*
by AdGuard Home is available.
Our main idea is that you are the one, who should be in control of your data. So it is only natural, that AdGuard Home does not collect any usage statistics, and does not use any web services unless you configure it to do so. See also the [full privacy policy][privacy] with every bit that *could in theory be sent* by AdGuard Home is available.
Please send your vulnerability reports to <security@adguard.com>. To make sure
that your report reaches us, please:
Please send your vulnerability reports to <security@adguard.com>. To make sure that your report reaches us, please:
1. Include the words “AdGuard Home” and “vulnerability” to the subject line as
well as a short description of the vulnerability. For example:
1. Include the words “AdGuard Home” and “vulnerability” to the subject line as well as a short description of the vulnerability. For example:
> AdGuard Home API vulnerability: possible XSS attack
> AdGuard Home API vulnerability: possible XSS attack
2. Make sure that the message body contains a clear description of the
vulnerability.
1. Make sure that the message body contains a clear description of the vulnerability.
If you have not received a reply to your email within 7 days, please make sure
to follow up with us again at <security@adguard.com>. Once again, make sure
that the word “vulnerability” is in the subject line.
If you have not received a reply to your email within 7 days, please make sure to follow up with us again at <security@adguard.com>. Once again, make sure that the word “vulnerability” is in the subject line.
"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",
@@ -279,6 +292,8 @@
"blocking_ipv4":"حجب عنوان IPv4",
"blocking_ipv6":"حجب عنوان IPv6",
"blocked_response_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":"الاربعاء",
"thursday_short":"الخميس",
"friday_short":"الجمعة",
"saturday_short":"السبت"
"saturday_short":"السبت",
"upstream_dns_cache_configuration":"تهيئة ذاكرة التخزين المؤقت لنظام أسماء النطاقات المستقبلي",
"enable_upstream_dns_cache":"تمكين التخزين المؤقت لنظام أسماء النطاقات DNS لتكوين المنبع المخصص لهذا العميل",
"dns_cache_size":"حجم ذاكرة التخزين المؤقت لنظام أسماء النطاقات، بالبايت"
"dns_test_warning_toast":"Upstream «{{key}}» не адказвае на тэставыя запыты і можа не працаваць належным чынам",
"unblock":"Адблакаваць",
"block":"Заблакаваць",
@@ -241,6 +244,7 @@
"allow_this_client":"Дазволіць доступ гэтаму кліенту",
"block_for_this_client_only":"Заблакаваць толькі для гэтага кліента",
"unblock_for_this_client_only":"Адблакаваць толькі для гэтага кліента",
"add_persistent_client":"Дадаць у захаваныя кліенты",
"time_table_header":"Час",
"date":"Дата",
"domain_name_table_header":"Дамен",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Выкарыстоўваць указаны IP для DNS",
"edns_use_custom_ip_desc":"Дазволіць выкарыстоўваць уласны IP для DNS",
"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":"Увядзіце па адным адрасе на радок",
"blocking_ipv4_desc":"IP-адрас, што вяртаецца пры блакаванню A-запыту",
"blocking_ipv6_desc":"IP-адрас, што вяртаецца пры блакаванню AAAA-запыту",
"blocking_mode_default":"Стандартны: Адказвае з нулёвым IP-адрасам (0.0.0.0 для A; :: для AAAA), калі заблакавана правілам у стылі Adblock; адказвае з IP-адрасам, паказаным у правіле, калі заблакавана правілам у стылі /etc/hosts-style",
"example_upstream_reserved":"odchozí DNS připojení <0>pro konkrétní doménu(y)</0>;",
"example_multiple_upstreams_reserved":"více odchozích připojení <0>pro konkrétní domény</0>;",
"example_upstream_comment":"komentář.",
"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. 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.",
"number_of_dns_query_to_safe_search":"Počet požadavků DNS na vyhledávače, při kterých bylo vynucené bezpečné vyhledávání",
"average_processing_time":"Průměrný čas zpracování",
"processing_time":"Doba zpracování",
"average_upstream_response_time":"Průměrná doba odezvy odchozích připojení",
"response_time":"Čas odezvy",
"average_processing_time_hint":"Průměrný čas zpracování požadavků DNS v milisekundách",
"block_domain_use_filters_and_hosts":"Blokovat domény pomocí filtrů a seznamů adres",
"filters_block_toggle_hint":"Pravidla blokování můžete nastavit v nastavení <a>Filtry</a>.",
@@ -234,6 +236,7 @@
"updated_upstream_dns_toast":"Odchozí servery byly úspěšně uloženy",
"dns_test_ok_toast":"Specifikované DNS servery pracují správně",
"dns_test_not_ok_toast":"Server \"{{key}}\": nemohl být použit, zkontrolujte, zda jste ho správně napsali",
"dns_test_parsing_error_toast":"Sekce {{section}}: řádek {{line}}: nelze použít, zkontrolujte prosím, zda jste ho správně napsali",
"dns_test_warning_toast":"Upstream \"{{key}}\" neodpovídá na testovací požadavky a nemusí fungovat správně",
"unblock":"Odblokovat",
"block":"Blokovat",
@@ -241,6 +244,7 @@
"allow_this_client":"Povolit tohoto klienta",
"block_for_this_client_only":"Blokovat pouze pro tohoto klienta",
"unblock_for_this_client_only":"Odblokovat pouze pro tohoto klienta",
"add_persistent_client":"Přidat jako trvalého klienta",
"time_table_header":"Čas",
"date":"Datum",
"domain_name_table_header":"Název domény",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Použít vlastní IP pro EDNS",
"edns_use_custom_ip_desc":"Povolit použití vlastní IP pro EDNS",
"rate_limit_desc":"Počet požadavků za sekundu, které smí jeden klient provádět (0: neomezeno)",
"rate_limit_subnet_len_ipv4":"Délka předpony podsítě pro adresy IPv4",
"rate_limit_subnet_len_ipv4_desc":"Délka předpony podsítě pro adresy IPv4 používané pro omezení rychlosti. Výchozí hodnota je 24",
"rate_limit_subnet_len_ipv4_error":"Délka předpony podsítě IPv4 by měla být mezi 0 a 32",
"rate_limit_subnet_len_ipv6":"Délka předpony podsítě pro adresy IPv6",
"rate_limit_subnet_len_ipv6_desc":"Délka předpony podsítě pro adresy IPv6 používané pro omezení rychlosti. Výchozí hodnota je 56",
"rate_limit_subnet_len_ipv6_error":"Délka předpony podsítě IPv6 by měla být mezi 0 a 128",
"form_enter_rate_limit_subnet_len":"Zadejte délku předpony podsítě pro omezení rychlosti",
"rate_limit_whitelist":"Seznam výjimek pro omezení rychlosti",
"rate_limit_whitelist_desc":"IP adresy vyloučené z omezení rychlosti",
"rate_limit_whitelist_placeholder":"Zadejte jednu IP adresu na řádek",
"blocking_ipv4_desc":"IP adresa, která se má vrátit v případě blokovaného požadavku typu A",
"blocking_ipv6_desc":"IP adresa, která se má vrátit v případě blokovaného požadavku typu AAAA",
"blocking_mode_default":"Výchozí: Odezva s nulovou IP adresou (0.0.0.0 pro A; :: pro AAAA), pokud je blokováno pravidlem ve stylu Adblock; odezva pomocí IP adresy uvedené v pravidle, pokud je blokováno pravidlem /etc/hosts-style",
"encryption_plain_dns_desc":"Ve výchozím nastavení je povolen běžný DNS. Můžete ho zakázat, aby všechna zařízení používala šifrovaný DNS. Chcete-li to provést, musíte povolit alespoň jeden šifrovaný protokol DNS",
"encryption_plain_dns_error":"Chcete-li zakázat běžný DNS, povolte alespoň jeden šifrovaný protokol DNS",
"topline_expiring_certificate":"Váš SSL certifikát brzy vyprší. Aktualizujte <0>Nastavení šifrování</0>.",
"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. 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.",
"dns_test_not_ok_toast":"Server \"{{key}}\": Kunne ikke bruges. Tjek, at du har angivet den korrekt",
"dns_test_parsing_error_toast":"Sektion {{section}}: linje {{line}}: kunne ikke anvendes. Tjek at den er angivet korrekt",
"dns_test_warning_toast":"Upstream \"{{key}}\" svarer ikke på testforespørgsler og fungerer muligvis ikke korrekt",
"unblock":"Afblokering",
"block":"Blokering",
@@ -241,6 +244,7 @@
"allow_this_client":"Tillad denne klient",
"block_for_this_client_only":"Blokér kun for denne klient",
"unblock_for_this_client_only":"Afblokér kun for denne klient",
"add_persistent_client":"Tilføj som vedvarende klient",
"time_table_header":"Tid",
"date":"Dato",
"domain_name_table_header":"Domænenavn",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Brug tilpasset IP til EDNS",
"edns_use_custom_ip_desc":"Tillad brug af tilpasset IP til EDNS",
"rate_limit_desc":"Antallet af forespørgsler pr. sekund tilladt pr. klient (værdien 0 = ubegrænset)",
"rate_limit_subnet_len_ipv4":"Længde på undernetpræfiks for IPv4-adresser",
"rate_limit_subnet_len_ipv4_desc":"Længde på undernetpræfiks for IPv4-adresser til hastighedsbegrænsning. Standard er 24",
"rate_limit_subnet_len_ipv4_error":"Længden på IPv4-undernetpræfiks skal være mellem 0 og 32",
"rate_limit_subnet_len_ipv6":"Længde på undernetpræfiks for IPv6-adresser",
"rate_limit_subnet_len_ipv6_desc":"Længde på undernetpræfiks for IPv6-adresser til hastighedsbegrænsning. Standard er 56",
"rate_limit_subnet_len_ipv6_error":"Længden på IPv6-undernetpræfiks skal være mellem 0 og 128",
"form_enter_rate_limit_subnet_len":"Angiv længden på undernetpræfiks til hastighedsbegrænsning",
"rate_limit_whitelist":"Hvidliste til hastighedsbegrænsning",
"rate_limit_whitelist_desc":"IP-adresser undtaget fra hastighedsbegrænsning",
"rate_limit_whitelist_placeholder":"Angiv én IP-adresse pr. linje",
"blocking_ipv4_desc":"Returneret IP-adresse for en blokeret A-forespørgsel",
"blocking_ipv6_desc":"Returneret IP-adresse for en blokeret AAAA-forespørgsel",
"blocking_mode_default":"Standard: Svar med nul IP-adresse (0.0.0.0 for A; :: for AAAA), når blokeret af Adblock-lignende regel. Svar med IP-adressen angivet i reglen, når blokeret af /etc/hosts-lignende regel",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Værtsnavne",
"encryption_reset":"Sikker på, at du vil nulstille krypteringsindstillingerne?",
"encryption_plain_dns_desc":"Almindelig DNS er aktiveret som standard. Den kan deaktiveres for at tvinge alle enheder til at bruge krypteret DNS. For at gøre dette, aktivér mindst én krypteret DNS-protokol",
"encryption_plain_dns_error":"Aktivér mindst én krypteret DNS-protokol for at deaktivere almindelig DNS",
"topline_expiring_certificate":"Dit SSL-certifikat er ved at udløbe. Opdatér <0>Krypteringsindstillinger</0>.",
"topline_expired_certificate":"Dit SSL-certifikat er udløbet. Opdatér <0>Krypteringsindstillinger</0>.",
"form_error_port_range":"Angiv portnummer i intervallet 80-65535",
"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. 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.",
"dns_test_not_ok_toast":"Server „{{key}}“: konnte nicht verwendet werden, bitte überprüfen Sie die korrekte Schreibweise",
"dns_test_parsing_error_toast":"Abschnitt {{section}}: Zeile {{line}}: konnte nicht verwendet werden, bitte überprüfen Sie, ob alles richtig geschrieben ist",
"dns_test_warning_toast":"Upstream „{{key}}“ reagiert nicht auf Testanfragen und funktioniert möglicherweise nicht fehlerfrei",
"unblock":"Entsperren",
"block":"Sperren",
@@ -241,6 +244,7 @@
"allow_this_client":"Diesen Client zulassen",
"block_for_this_client_only":"Nur für diesen Client sperren",
"unblock_for_this_client_only":"Nur für diesen Client freigeben",
"rule_removed_from_custom_filtering_toast":"Regel wurde aus den benutzerdefinierten Filterregeln entfernt: {{rule}}",
"rule_added_to_custom_filtering_toast":"Regel wurde zu den benutzerdefinierten Filterregeln hinzugefügt: {{rule}}",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Benutzerdefinierte IP für EDNS verwenden",
"edns_use_custom_ip_desc":"Benutzerdefinierte IP für EDNS zulassen",
"rate_limit_desc":"Die Anzahl der Anfragen pro Sekunde, die ein einzelner Client stellen darf. Das Setzen auf 0 bedeutet keine Begrenzung.",
"rate_limit_subnet_len_ipv4":"Länge des Subnetzpräfixes für IPv4-Adressen",
"rate_limit_subnet_len_ipv4_desc":"Subnetpräfixlänge für IPv4-Adressen, die für die Ratebegrenzung verwendet werden. Der Standardwert ist 24",
"rate_limit_subnet_len_ipv4_error":"Die Subnetzpräfixlänge für IPv4-Adressen sollte zwischen 0 und 32 liegen",
"rate_limit_subnet_len_ipv6":"Subnetzpräfixlänge für IPv6-Adressen",
"rate_limit_subnet_len_ipv6_desc":"Subnetpräfixlänge für IPv6-Adressen, die für die Ratebegrenzung verwendet werden. Der Standardwert ist 56",
"rate_limit_subnet_len_ipv6_error":"Die Subnetzpräfixlänge für IPv6-Adressen sollte zwischen 0 und 128 liegen",
"form_enter_rate_limit_subnet_len":"Geben Sie die Subnetzpräfixlänge für die Ratebegrenzung ein",
"rate_limit_whitelist":"Zulassungsliste für die Ratebegrenzung",
"rate_limit_whitelist_desc":"IP-Adressen, die von der Ratebegrenzung ausgeschlossen sind",
"rate_limit_whitelist_placeholder":"Geben Sie eine IP-Adresse pro Zeile ein",
"blocking_ipv4_desc":"IP-Adresse, die für eine gesperrte A-Anfrage zurückgegeben werden soll",
"blocking_ipv6_desc":"IP-Adresse, die für eine gesperrte AAAA-Anfrage zurückgegeben werden soll",
"blocking_mode_default":"Standard: Mit Null IP Adress (0.0.0.0 for A; :: for AAAA) antworten, wenn sie durch eine Regel im Adblock-Stil gesperrt sind; mit der in der Regel angegebenen IP-Adresse antworten, wenn sie durch eine Regel im /etc/hosts-Stil gesperrt wurde",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Hostnamen",
"encryption_reset":"Möchten Sie die Verschlüsselungseinstellungen wirklich zurücksetzen?",
"encryption_warning":"Warnhinweis",
"encryption_plain_dns_enable":"Einfaches DNS aktivieren",
"encryption_plain_dns_desc":"Einfaches DNS ist standardmäßig aktiviert. Sie können es deaktivieren, um alle Geräte zu zwingen, verschlüsseltes DNS zu verwenden. Dazu müssen Sie mindestens ein verschlüsseltes DNS-Protokoll aktivieren",
"encryption_plain_dns_error":"Um einfaches DNS zu deaktivieren, aktivieren Sie mindestens ein verschlüsseltes DNS-Protokoll",
"topline_expiring_certificate":"Ihr SSL-Zertifikat läuft demnächst ab. Aktualisieren Sie Ihre <0>Verschlüsselungseinstellungen</0>.",
"topline_expired_certificate":"Ihr SSL-Zertifikat ist abgelaufen. Aktualisieren Sie Ihre <0>Verschlüsselungseinstellungen</0>.",
"form_error_port_range":"Geben Sie die Portnummer zwischen 80 und 65535 ein",
"example_upstream_reserved":"an upstream <0>for specific domains</0>;",
"example_multiple_upstreams_reserved":"multiple upstreams <0>for specific domains</0>;",
"example_upstream_comment":"a comment.",
"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. 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",
@@ -143,7 +144,8 @@
"enforced_save_search":"Enforced safe search",
"number_of_dns_query_to_safe_search":"The number of DNS requests to search engines for which Safe Search was enforced",
"average_processing_time_hint":"Average time in milliseconds on processing a DNS request",
"block_domain_use_filters_and_hosts":"Block domains using filters and hosts files",
"filters_block_toggle_hint":"You can setup blocking rules in the <a>Filters</a> settings.",
@@ -152,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.",
"dns_test_ok_toast":"Specified DNS servers are working correctly",
"dns_test_not_ok_toast":"Server \"{{key}}\": could not be used, please check that you've written it correctly",
"dns_test_parsing_error_toast":"Section {{section}}: line {{line}}: could not be used, please check that you've written it correctly",
"dns_test_warning_toast":"Upstream \"{{key}}\" does not respond to test requests and may not work properly",
"unblock":"Unblock",
"block":"Block",
@@ -241,6 +244,7 @@
"allow_this_client":"Allow this client",
"block_for_this_client_only":"Block for this client only",
"unblock_for_this_client_only":"Unblock for this client only",
"add_persistent_client":"Add as persistent client",
"time_table_header":"Time",
"date":"Date",
"domain_name_table_header":"Domain name",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Use custom IP for EDNS",
"edns_use_custom_ip_desc":"Allow to use custom IP for EDNS",
"rate_limit_desc":"The number of requests per second allowed per client. Setting it to 0 means no limit.",
"rate_limit_subnet_len_ipv4":"Subnet prefix length for IPv4 addresses",
"rate_limit_subnet_len_ipv4_desc":"Subnet prefix length for IPv4 addresses used for rate limiting. The default is 24",
"rate_limit_subnet_len_ipv4_error":"The IPv4 subnet prefix length should be between 0 and 32",
"rate_limit_subnet_len_ipv6":"Subnet prefix length for IPv6 addresses",
"rate_limit_subnet_len_ipv6_desc":"Subnet prefix length for IPv6 addresses used for rate limiting. The default is 56",
"rate_limit_subnet_len_ipv6_error":"The IPv6 subnet prefix length should be between 0 and 128",
"form_enter_rate_limit_subnet_len":"Enter subnet prefix length for rate limiting",
"rate_limit_whitelist":"Rate limiting allowlist",
"rate_limit_whitelist_desc":"IP addresses excluded from rate limiting",
"rate_limit_whitelist_placeholder":"Enter one IP address per line",
"blocking_ipv4_desc":"IP address to be returned for a blocked A request",
"blocking_ipv6_desc":"IP address to be returned for a blocked AAAA request",
"blocking_mode_default":"Default: Respond with zero IP address (0.0.0.0 for A; :: for AAAA) when blocked by Adblock-style rule; respond with the IP address specified in the rule when blocked by /etc/hosts-style rule",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Hostnames",
"encryption_reset":"Are you sure you want to reset encryption settings?",
"encryption_warning":"Warning",
"encryption_plain_dns_enable":"Enable plain DNS",
"encryption_plain_dns_desc":"Plain DNS is enabled by default. You can disable it to force all devices to use encrypted DNS. To do this, you must enable at least one encrypted DNS protocol",
"encryption_plain_dns_error":"To disable plain DNS, enable at least one encrypted DNS protocol",
"topline_expiring_certificate":"Your SSL certificate is about to expire. Update <0>Encryption settings</0>.",
"topline_expired_certificate":"Your SSL certificate is expired. Update <0>Encryption settings</0>.",
"form_error_port_range":"Enter port number in the range of 80-65535",
"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 upstream a la vez. 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 de fallback",
"fallback_dns_desc":"La lista de DNS de fallback serán usadas cuando los servidores de upstream de DNS no respondan. La sintaxis es la misma que en los principales del campo anterior.",
"fallback_dns_placeholder":"Ingresa un servidor de DNS alternativo por línea",
"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",
@@ -131,8 +132,8 @@
"top_clients":"Clientes más frecuentes",
"no_clients_found":"No se han encontrado clientes",
"general_statistics":"Estadísticas generales",
"top_upstreams":"Mejores upstreams",
"no_upstreams_data_found":"No se han encontrado datos de upstreams",
"top_upstreams":"DNS de subida más frecuentes",
"no_upstreams_data_found":"No se han encontrado datos de DNS de subida",
"number_of_dns_query_days":"Número de consultas DNS procesadas durante el último {{count}} día",
"number_of_dns_query_days_plural":"Número de consultas DNS procesadas durante los últimos {{count}} días",
"number_of_dns_query_hours":"Número de consultas DNS procesadas durante la última {{count}} hora",
"updated_upstream_dns_toast":"Servidores DNS de subida guardados correctamente",
"dns_test_ok_toast":"Los servidores DNS especificados funcionan correctamente",
"dns_test_not_ok_toast":"Servidor \"{{key}}\": no se puede utilizar, por favor revisa si lo has escrito correctamente",
"dns_test_parsing_error_toast":"No se pudo utilizar la sección {{section}}: línea {{line}}:, verifica si la escribiste correctamente",
"dns_test_warning_toast":"DNS de subida \"{{key}}\" no responde a las peticiones de prueba y es posible que no funcione correctamente",
"unblock":"Desbloquear",
"block":"Bloquear",
@@ -241,6 +244,7 @@
"allow_this_client":"Permitir a este cliente",
"block_for_this_client_only":"Bloquear solo para este cliente",
"unblock_for_this_client_only":"Desbloquear solo para este cliente",
"add_persistent_client":"Añadir como cliente persistente",
"time_table_header":"Hora",
"date":"Fecha",
"domain_name_table_header":"Nombre del dominio",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Usar IP personalizada para EDNS",
"edns_use_custom_ip_desc":"Permitir el uso de IP personalizadas para EDNS",
"rate_limit_desc":"Número de peticiones por segundo permitidas por cliente. Establecerlo en 0 significa que no hay límite.",
"rate_limit_subnet_len_ipv4":"Longitud del prefijo de subred para direcciones IPv4",
"rate_limit_subnet_len_ipv4_desc":"Longitud del prefijo de subred para direcciones IPv4 utilizadas para limitar la velocidad. El valor predeterminado es 24",
"rate_limit_subnet_len_ipv4_error":"La longitud del prefijo de subred IPv4 debe estar entre 0 y 32",
"rate_limit_subnet_len_ipv6":"Longitud del prefijo de subred para direcciones IPv6",
"rate_limit_subnet_len_ipv6_desc":"Longitud del prefijo de subred para direcciones IPv6 utilizadas para limitar la velocidad. El valor predeterminado es 56",
"rate_limit_subnet_len_ipv6_error":"La longitud del prefijo de subred IPv6 debe estar entre 0 y 128",
"form_enter_rate_limit_subnet_len":"Ingresa la longitud del prefijo de subred para limitar la velocidad",
"rate_limit_whitelist":"Lista de permitidos de limitación de velocidad",
"rate_limit_whitelist_desc":"Direcciones IP excluidas de la limitación de velocidad",
"rate_limit_whitelist_placeholder":"Ingresa una dirección IP por línea",
"blocking_ipv4_desc":"Dirección IP devolverá una petición A bloqueada",
"blocking_ipv6_desc":"Dirección IP devolverá una petición AAAA bloqueada",
"blocking_mode_default":"Predeterminado: Responde con dirección IP cero (0.0.0.0 para A; :: para AAAA) cuando está bloqueado por la regla de estilo Adblock; responde con la dirección IP especificada en la regla cuando está bloqueado por una regla de estilo /etc/hosts",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Nombres de hosts",
"encryption_reset":"¿Estás seguro de que deseas restablecer la configuración de cifrado?",
"encryption_warning":"Advertencia",
"encryption_plain_dns_enable":"Activar DNS simple (sin cifrado)",
"encryption_plain_dns_desc":"El DNS simple (sin cifrado) está activado de forma predeterminada. Puedes desactivarlo para obligar a todos los dispositivos a utilizar DNS cifrado. Para ello, debes habilitar al menos un protocolo DNS cifrado",
"encryption_plain_dns_error":"Para desactivar el DNS simple, activa al menos un protocolo DNS cifrado",
"topline_expiring_certificate":"Tu certificado SSL está a punto de expirar. Actualiza la <0>configuración de cifrado</0>.",
"topline_expired_certificate":"Tu certificado SSL ha expirado. Actualiza la <0>configuración de cifrado</0>.",
"form_error_port_range":"Ingresa el número del puerto en el rango de 80 a 65535",
@@ -450,6 +467,7 @@
"form_add_id":"Añadir identificador",
"form_client_name":"Ingresa el nombre del cliente",
"schedule_modal_description":"Este horario sustituirá cualquier horario existente para el mismo día de la semana. Cada día de la semana solo puede tener un periodo de inactividad.",
"schedule_modal_time_off":"Detener el servicio de bloqueo:",
"schedule_modal_time_off":"Detener servicio de bloqueo:",
"schedule_new":"Nuevo horario",
"schedule_edit":"Editar horario",
"schedule_save":"Guardar horario",
@@ -722,5 +740,8 @@
"wednesday_short":"Mié.",
"thursday_short":"Jue.",
"friday_short":"Vie.",
"saturday_short":"Sáb."
"saturday_short":"Sáb.",
"upstream_dns_cache_configuration":"Configuración de la caché DNS upstream",
"enable_upstream_dns_cache":"Habilitar el almacenamiento en caché de DNS para la configuración personalizada de este cliente",
"dns_cache_size":"Tamaño de la caché DNS, en bytes"
"number_of_dns_query_to_safe_search":"تعداد درخواست های DNS برای موتور جستجو که جستجوی اَمن اجبار شده",
"average_processing_time":"میانگین زمان پردازش",
"processing_time":"زمان پردازش",
"average_processing_time_hint":"زمان میانگین بر هزارم ثانیه در پردازش درخواست DNS",
"block_domain_use_filters_and_hosts":"مسدودسازی دامنه ها توسط فیلترها و فایل های میزبان",
"filters_block_toggle_hint":"میتوانید دستورات مسدودسازی را در تنظیمات <a>فیلترها</a> راه اندازی کنید.",
@@ -221,6 +220,7 @@
"updated_upstream_dns_toast":"سرورهای DNS جریان ارسالی بروز رسانی شده است",
"dns_test_ok_toast":"سرورهای DNS تعیین شده بدرستی کار می کنند",
"dns_test_not_ok_toast":"سرور \"{{key}}\": نمیتواند مورد استفاده قرار گیرد،لطفا بررسی کنید آن را بدرستی نوشته اید",
"dns_test_parsing_error_toast":"بخش {{section}}: خط {{line}}: نمیتواند مورد استفاده قرار گیرد،لطفا بررسی کنید آن را بهدرستی نوشتهاید",
"unblock":"رفع انسداد",
"block":"مسدود کردن",
"disallow_this_client":"این مشتری را رد کنید",
@@ -421,6 +421,7 @@
"form_add_id":"افزودن احرازکننده",
"form_client_name":"نام کلاینت را وارد کنید",
"name":"نام",
"client_name":"مشتری {{id}}",
"client_global_settings":"استفاده از تنظیمات سراسری",
"client_deleted":"کلاینت \"{{key}}\" را با موفقیت حذف کرد",
"client_added":"کلاینت \"{{key}}\" را با موفقیت اضافه کرد",
@@ -588,6 +589,7 @@
"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",
@@ -12,14 +13,14 @@
"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.",
"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",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Isäntänimet",
"encryption_reset":"Haluatko varmasti palauttaa salausasetukset?",
"encryption_warning":"Varoitus",
"encryption_plain_dns_enable":"Käytä tavallista DNS:ää",
"encryption_plain_dns_desc":"Tavallinen DNS on oletusarvoisesti käytössä. Voit poistaa sen käytöstä pakottaaksesi kaikki laitteet käyttämään salattua DNS:ää. Tätä varten sinun on otettava käyttöön ainakin yksi salattu DNS-protokolla.",
"encryption_plain_dns_error":"Voit poistaa tavallisen DNS:n käytöstä ottamalla käyttöön ainakin yhden salatun DNS-protokollan.",
"topline_expiring_certificate":"SSL-varmenteesi on erääntymässä. Päivitä <0>Salausasetukset</0>.",
"topline_expired_certificate":"SSL-varmenteesi on erääntynyt. Päivitä <0>Salausasetukset</0>.",
"access_desc":"Tässä voidaan määrittää AdGuard Homen DNS-palvelimen käyttöoikeussääntöjä.",
"access_allowed_title":"Sallitut päätelaitteet",
"access_allowed_desc":"Lista CIDR-merkinnöistä, IP-osoitteista tai <a>ClientID</a>-tunnisteista. Jos listalla on kohteita, hyväksyy AdGuard Home pyyntöjä vain näiltä päätelaitteilta.",
"access_disallowed_desc":"Lista CIDR-merkinnöistä, IP-osoitteista tai <a>ClientID</a>-tunnisteista. Jos listalla on kohteita, hylkää AdGuard Home näiden päätelaitteiden pyynnöt. Tätä kenttää ei huomioida, jos sallittuja päätelaitteita on määritetty.",
"access_blocked_desc":"Ei pidä sekoittaa suodattimiin. AdGuard Home hylkää näiden verkkotunnusten DNS-pyynnöt, eivätkä nämä pyynnöt näy edes pyyntöhistoriassa. Tähän voidaan syöttää tarkkoja verkkotunnuksia, jokerimerkkejä tai URL-suodatussääntöjä, kuten \"example.org\", \"*.example.org\" tai \"||example.org^\".",
"access_blocked_title":"Estetyt verkkotunnukset",
"access_blocked_desc":"Ei pidä sekoittaa suodattimiin. AdGuard Home hylkää näiden verkkotunnusten DNS-pyynnöt, eivätkä nämä pyynnöt myöskään näy pyyntöhistoriassa. Tähän voidaan syöttää tarkkoja verkkotunnuksia, jokerimerkkejä tai URL-suodatussääntöjä, kuten \"example.org\", \"*.example.org\" tai \"||example.org^\".",
"updates_checked":"Uusi versio AdGuard Home -ohjelmasta on saatavana\n",
"updates_version_equal":"AdGuard Home on ajan tasalla",
@@ -483,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.",
"example_upstream_reserved":"un amont <0>pour des domaines spécifiques</0> ;",
"example_multiple_upstreams_reserved":"plusieurs amonts <0>pour des domaines spécifiques</0> ;",
"example_upstream_comment":" un commentaire.",
"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. 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",
"number_of_dns_query_to_safe_search":"Le nombre de requêtes DNS faites avec la Recherche securisée",
"average_processing_time":"Temps moyen de traitement",
"processing_time":"Délai de traitement",
"average_upstream_response_time":"Temps de réponse moyen en amont",
"response_time":"Temps de réponse",
"average_processing_time_hint":"Temps moyen (en millisecondes) de traitement d'une requête DNS",
"block_domain_use_filters_and_hosts":"Bloquez les domaines à l'aide des filtres et fichiers hosts",
"filters_block_toggle_hint":"Vous pouvez configurer les règles de filtrage dans les paramètres des <a>Filtres</a>.",
@@ -234,6 +236,7 @@
"updated_upstream_dns_toast":"Serveurs en amont enregistrés",
"dns_test_ok_toast":"Les serveurs DNS spécifiés fonctionnent correctement",
"dns_test_not_ok_toast":"Impossible d'utiliser le serveur « {{key}} »: veuillez vérifier si le nom saisi est bien correct",
"dns_test_parsing_error_toast":"La section {{section}}: ligne {{line}}: n'a pas pu être utilisée, veuillez vérifier que vous l'avez écrite correctement",
"dns_test_warning_toast":"L'amont « {{key}} » ne répond pas aux demandes de test et peut ne pas fonctionner correctement",
"unblock":"Débloquer",
"block":"Bloquer",
@@ -241,6 +244,7 @@
"allow_this_client":"Autoriser ce client",
"block_for_this_client_only":"Bloquer uniquement pour ce client",
"unblock_for_this_client_only":"Débloquer uniquement pour ce client",
"add_persistent_client":"Ajouter comme client persistant",
"time_table_header":"Temps",
"date":"Date",
"domain_name_table_header":"Nom de domaine",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Utiliser une IP personnalisée pour EDNS",
"edns_use_custom_ip_desc":"Autoriser l'utilisation d'une adresse IP personnalisée pour EDNS",
"rate_limit_desc":"Le nombre de requêtes par seconde qu’un seul client est autorisé à faire. Le réglage 0 fait illimité.",
"rate_limit_subnet_len_ipv4":"Longueur du préfixe de sous-réseau pour les adresses IPv4",
"rate_limit_subnet_len_ipv4_desc":"Longueur du préfixe de sous-réseau pour les adresses IPv4 utilisé pour la limitation de vitesse. La valeur par défaut est 24",
"rate_limit_subnet_len_ipv4_error":"La longueur du préfixe du sous-réseau IPv4 doit être entre 0 et 32",
"rate_limit_subnet_len_ipv6":"Longueur du préfixe de sous-réseau pour les adresses IPv6",
"rate_limit_subnet_len_ipv6_desc":"Longueur du préfixe de sous-réseau pour les adresses IPv6 utilisé pour la limitation de débit. La valeur par défaut est 56",
"rate_limit_subnet_len_ipv6_error":"La longueur du préfixe du sous-réseau IPv6 doit être entre 0 et 128",
"form_enter_rate_limit_subnet_len":"Saisissez la longueur du préfixe de sous-réseau pour la limitation de débit",
"rate_limit_whitelist":"Liste d'autorisation de limitation de débit",
"rate_limit_whitelist_desc":"Adresses IP exclues de la limitation du débit",
"rate_limit_whitelist_placeholder":"Saisissez une adresse IP par ligne",
"blocking_ipv4_desc":"Adresse IP à renvoyer pour une demande A bloquée",
"blocking_ipv6_desc":"Adresse IP à renvoyer pour une demande AAAA bloquée",
"blocking_mode_default":"Par défaut : Répondre avec adresse IP zéro (0.0.0.0 pour A ; :: pour AAAA) lorsque bloqué par la règle de style Adblock ; répondre avec l’adresse IP spécifiée dans la règle lorsque bloquée par la règle du style /etc/hosts",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Noms d'hôte",
"encryption_reset":"Voulez-vous vraiment réinitialiser les paramètres de chiffrement ?",
"encryption_warning":"Attention",
"encryption_plain_dns_enable":"Activer le DNS simple",
"encryption_plain_dns_desc":"Le DNS simple est activé par défaut. Vous pouvez le désactiver pour forcer tous les appareils à utiliser un DNS crypté. Pour faire ça, vous devez activer au moins un protocole DNS crypté",
"encryption_plain_dns_error":"Pour désactiver le DNS simple, activez au moins un protocole DNS crypté",
"topline_expiring_certificate":"Votre certificat SSL est sur le point d'expirer. Mettez à jour vos <0>Paramètres de chiffrement</0>.",
"topline_expired_certificate":"Votre certificat SSL a expiré. Mettez à jour vos <0>Paramètres de chiffrement</0>.",
"form_error_port_range":"Saisissez une valeur de port entre 80 et 65535",
@@ -450,6 +467,7 @@
"form_add_id":"Ajouter identifiant",
"form_client_name":"Saisissez le nom du client",
"name":"Nom",
"client_name":"Client {{id}}",
"client_global_settings":"Utiliser les paramètres généraux",
"client_deleted":"Le client « {{key}} » a été supprimé",
"client_added":"Le client « {{key}} » a été ajouté",
@@ -660,7 +678,7 @@
"use_saved_key":"Utiliser la clef précédemment enregistrée",
"parental_control":"Contrôle parental",
"safe_browsing":"Navigation sécurisée",
"served_from_cache":"{{value}} <i>(depuis le cache)</i>",
"served_from_cache_label":"Servi depuis le cache",
"form_error_password_length":"Le mot de passe doit comporter entre {{min}} et {{max}} caractères",
"anonymizer_notification":"<0>Note :</0> L'anonymisation IP est activée. Vous pouvez la désactiver dans les <1>paramètres généraux</1>.",
"confirm_dns_cache_clear":"Voulez-vous vraiment vider le cache DNS ?",
@@ -722,5 +740,8 @@
"wednesday_short":"Mer.",
"thursday_short":"Jeu.",
"friday_short":"Ven.",
"saturday_short":"Sam."
"saturday_short":"Sam.",
"upstream_dns_cache_configuration":"Configuration du cache DNS en amont",
"enable_upstream_dns_cache":"Activer la mise en cache pour la configuration personnalisée du serveur en amont de ce client",
"example_upstream_reserved":"upstream <0>za određene domene</0>;",
"example_multiple_upstreams_reserved":"višestruke upstream poslužitelje <0>za određene domene</0>;",
"example_upstream_comment":"komentar.",
"upstream_parallel":"Koristi paralelne upite kako bi ubrzali rješavanje istovremenim ispitavanjem svih upstream poslužitelja.",
"parallel_requests":"Paralelni zahtjevi",
@@ -12,14 +13,14 @@
"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.",
"enforced_save_search":"Omogućeno sigurno pretraživanje",
"number_of_dns_query_to_safe_search":"Broj DNS zahtjeva prema pretraživačima za koje je omogućeno Sigurno pretraživanje",
"average_processing_time":"Prosječno vrijeme obrade",
"processing_time":"Vrijeme obrade",
"average_upstream_response_time":"Prosječno vrijeme odziva upstream poslužitelja",
"response_time":"Vrijeme odziva",
"average_processing_time_hint":"Prosječno vrijeme u milisekundama za obradu DNS zahtjeva",
"block_domain_use_filters_and_hosts":"Blokiraj domene koristeći filtre ili hosts datoteke",
"filters_block_toggle_hint":"Pravila blokiranja možete postaviti u postavkama <a>filtara</a>.",
@@ -234,6 +236,7 @@
"updated_upstream_dns_toast":"Uzvodni poslužitelji uspješno su spremljeni",
"dns_test_ok_toast":"Odabrani DNS poslužitelji su trenutno aktivni",
"dns_test_not_ok_toast":"\"{{key}}\" poslužitelja: ne može se upotrijebiti, provjerite jeste li to ispravno napisali",
"dns_test_parsing_error_toast":"Odjeljak {{section}}: redak {{line}}: nije moguće koristiti, provjerite jeste li ispravno napisali",
"dns_test_warning_toast":"Upstream \"{{key}}\" ne odgovara na zahtjeve za testiranje i možda neće raditi ispravno",
"unblock":"Odblokiraj",
"block":"Blokiraj",
@@ -241,6 +244,7 @@
"allow_this_client":"Omogući ovog klijenta",
"block_for_this_client_only":"Blokiraj samo za ovog klijenta",
"unblock_for_this_client_only":"Odblokiraj samo za ovog klijenta",
"add_persistent_client":"Dodaj u spremljene klijente",
"time_table_header":"Vrijeme",
"date":"Datum",
"domain_name_table_header":"Naziv domene",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Koristi prilagođeni IP za EDNS",
"edns_use_custom_ip_desc":"Dopusti korištenje prilagođenog IP-a za EDNS",
"rate_limit_desc":"Broj zahtjeva u sekundi koji su dopušteni po jednom klijentu. Postavljanje na 0 znači neograničeno.",
"rate_limit_subnet_len_ipv4":"Duljina prefiksa podmreže za IPv4 adrese",
"rate_limit_subnet_len_ipv4_desc":"Duljina prefiksa podmreže za IPv4 adrese koje se koriste za ograničavanje brzine. Zadana vrijednost je 24",
"rate_limit_subnet_len_ipv4_error":"Dužina IPv4 prefiksa podmreže trebala bi biti između 0 i 32",
"rate_limit_subnet_len_ipv6":"Duljina prefiksa podmreže za IPv6 adrese",
"rate_limit_subnet_len_ipv6_desc":"Duljina prefiksa podmreže za IPv6 adrese koje se koriste za ograničavanje brzine. Zadana vrijednost je 56",
"rate_limit_subnet_len_ipv6_error":"Dužina IPv6 prefiksa podmreže trebala bi biti između 0 i 128",
"form_enter_rate_limit_subnet_len":"Unesite duljinu prefiksa podmreže za ograničenje brzine",
"rate_limit_whitelist":"Popis dopuštenih za ograničavanje brzine",
"rate_limit_whitelist_desc":"IP adrese isključene iz ograničenja brzine",
"rate_limit_whitelist_placeholder":"Unesite jednu adresu poslužitelja po retku",
"blocking_ipv4_desc":"Povratna IP adresa za blokirane A zahtjeve",
"blocking_ipv6_desc":"Povratna IP adresa za blokirane AAAA zahtjeve",
"blocking_mode_default":"Zadano: Odgovori s nultom IP adresom (0.0.0.0 za A; :: za AAAA) kada ga blokira Adblock slično pravilo; odgovorite s IP adresom definiranom u pravilu kada je blokirano od /etc/hosts sličnog pravila",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Nazivi računala",
"encryption_reset":"Jeste li sigurni da želite poništiti postavke šifriranja?",
"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",
"upstream_parallel":"Használjon párhuzamos lekéréseket a domainek feloldásának felgyorsításához az összes upstream kiszolgálóra való egyidejű lekérdezéssel.",
"blocking_mode_default":"Alapértelmezés: Válaszoljon nulla IP-címmel (vagyis 0.0.0.0 az A-hoz, :: pedig az AAAA-hoz), amikor a blokkolás egy adblock-stílusú szabállyal történik; illetve válaszoljon egy, a szabály által meghatározott IP címmel, amikor a blokkolás egy /etc/hosts stílusú szabállyal történik",
"example_multiple_upstreams_reserved":"beberapa server upstream <0>untuk domain spesifik</0>;",
"example_upstream_comment":"komentar.",
"upstream_parallel":"Gunakan kueri paralel untuk mempercepat resoluasi dengan menanyakan semua server upstream secara bersamaan",
"parallel_requests":"Permintaan paralel",
@@ -9,7 +10,7 @@
"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.",
"fallback_dns_title":"Server DNS cadangan",
"fallback_dns_desc":"Daftar server DNS cadangan yang digunakan ketika server DNS hulu tidak merespons. Sintaksnya sama dengan bidang hulu utama di atas.",
"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.",
"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).",
"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 upstream ini. Jika dinonaktifkan, Adguard Home merespon dengan NXDOMAIN untuk semua permintaan PTR tersebut kecuali untuk klien yang diketahui dari DHCP, /etc/hosts, dan seterusnya.",
"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.",
"check_dhcp_servers":"Cek untuk server DHCP",
"save_config":"Simpan pengaturan",
"enabled_dhcp":"Server DHCP diaktifkan",
@@ -67,7 +68,7 @@
"ip":"IP",
"dhcp_table_hostname":"Nama host",
"dhcp_table_expires":"Kadaluwarsa",
"dhcp_warning":"Jika anda ingin mengaktifkan server DHCP bawaan, pastikan tidak ada server DHCP lain yang aktif. Jika tidak, akan memutus koneksi internet pada perangkat yang telah terhubung!",
"dhcp_warning":"Jika Anda tetap ingin mengaktifkan server DHCP, pastikan tidak ada server DHCP lain yang aktif di jaringan Anda, karena hal ini dapat memutus konektivitas Internet untuk perangkat di jaringan!",
"dhcp_error":"AdGuard Home tidak dapat menentukan apakah ada server DHCP aktif lain pada jaringan",
"dhcp_static_ip_error":"Jika ingin menggunakan server DHCP, alamat IP statis harus diatur. AdGuard Home gagal menentukan jika antarmuka jaringan ini dikonfigurasi menggunakan alamat IP statis. Silakan atur alamat IP statis secara manual.",
"dhcp_dynamic_ip_found":"Sistem Anda menggunakan konfigurasi alamat IP dinamis untuk antarmuka <0>{{interfaceName}}</0>. Untuk menggunakan server DHCP, alamat IP statis harus ditetapkan. Alamat IP Anda saat ini adalah <0>{{ipAddress}}</0>. AdGuard Home akan secara otomatis menetapkan alamat IP ini sebagai statis jika Anda menekan tombol Aktifkan DHCP.",
"number_of_dns_query_blocked_24_hours":"Jumlah permintaan DNS yang diblokir oleh filter adblock dan daftar hitam host",
"number_of_dns_query_blocked_24_hours_by_sec":"Jumlah permintaan DNS yang diblokir oleh modul keamanan penjelajahan AdGuard",
"number_of_dns_query_blocked_24_hours_adult":"Jumlah situs web dewasa yang diblokir",
"enforced_save_search":"Paksa pencarian aman",
"number_of_dns_query_to_safe_search":"Jumlah perminataan DNS ke mesin pencari yang dipaksa Pencarian Aman",
"average_processing_time":"Rata-rata waktu pemrosesan",
"processing_time":"Waktu pemrosesan",
"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",
"filters_block_toggle_hint":"Anda dapat menyiapkan aturan pemblokiran di pengaturan <a>Penyaringan</a>.",
"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",
@@ -164,7 +166,7 @@
"encryption_settings":"Pengaturan enkripsi",
"dhcp_settings":"Pengaturan DHCP",
"upstream_dns":"Server DNS hulu",
"upstream_dns_help":"Masukkan alamat server per baris. <a>Pelajari lebih</a> mengenai konfigurasi upstream server DNS.",
"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}}",
"test_upstream_btn":"Uji hulu",
"upstreams":"Upstream",
@@ -190,10 +192,10 @@
"delete_table_action":"Hapus",
"elapsed":"Berlalu",
"filters_and_hosts_hint":"AdGuard Home memahami aturan dasar adblock dan sintak file hosts.",
"no_blocklist_added":"Tiada daftar hitam ditambahkan",
"no_whitelist_added":"Tiada daftar putih ditambahkan",
"add_blocklist":"Tambah daftar hitam",
"add_allowlist":"Tambah daftar putih",
"no_blocklist_added":"Tidak ada daftar hitam yang ditambahkan",
"no_whitelist_added":"Tidak ada daftar putih yang ditambahkan",
"add_blocklist":"Tambahkan daftar hitam",
"add_allowlist":"Tambahkan daftar putih",
"cancel_btn":"Batal",
"enter_name_hint":"Masukkan nama",
"enter_url_or_path_hint":"Masukan sebuah URL atau jalur absolut dari daftar",
"example_upstream_tcp_port":"DNS biasa (melalui TCP, dengan port);",
@@ -234,6 +236,7 @@
"updated_upstream_dns_toast":"Server upstream 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",
"unblock":"Buka Blokir",
"block":"Blok",
@@ -241,6 +244,7 @@
"allow_this_client":"Ijinkan klien ini",
"block_for_this_client_only":"Blok hanya untuk klien ini",
"unblock_for_this_client_only":"Jangan diblok hanya untuk klien ini",
"add_persistent_client":"Tambahkan sebagai klien persisten",
"time_table_header":"Waktu",
"date":"Tanggal",
"domain_name_table_header":"Nama domain",
@@ -287,7 +291,7 @@
"custom_ip":"Custom IP",
"blocking_ipv4":"Blokiran IPv4",
"blocking_ipv6":"Blokiran IPv6",
"blocked_response_ttl":"Respon TLL diblokir",
"blocked_response_ttl":"Respons TTL terblokir",
"blocked_response_ttl_desc":"Menentukan berapa detik klien harus menyimpan respons yang difilter dalam cache",
"form_enter_blocked_response_ttl":"Masukkan TTL respons yang diblokir (detik)",
"dnscrypt":"DNSCrypt",
@@ -308,9 +312,19 @@
"edns_use_custom_ip":"Gunakan IP khusus 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.",
"blocking_ipv4_desc":"Alamat IP akan dikembalikan untuk permintaan A yang diblokir",
"blocking_ipv6_desc":"Alamat IP akan dipulihkan untuk permintaan AAAA yang diblokir",
"blocking_mode_default":"Default: Tanggapi dengan alamat IP nol (0.0.0.0 untuk A; :: untuk AAAA) saat diblokir oleh aturan gaya Adblock; tanggapi dengan alamat IP yang ditentukan dalam aturan ketika diblokir oleh aturan gaya host /etc/",
"rate_limit_subnet_len_ipv4":"Panjang awalan subnet untuk alamat IPv4",
"rate_limit_subnet_len_ipv4_desc":"Panjang awalan subnet untuk alamat IPv4 yang digunakan untuk pembatasan kecepatan. Standarnya adalah 24",
"rate_limit_subnet_len_ipv4_error":"Panjang awalan subnet IPv4 harus antara 0 dan 32",
"rate_limit_subnet_len_ipv6":"Panjang awalan subnet untuk alamat IPv6",
"rate_limit_subnet_len_ipv6_desc":"Panjang awalan subnet untuk alamat IPv6 yang digunakan untuk pembatasan kecepatan. Standarnya adalah 56",
"rate_limit_subnet_len_ipv6_error":"Panjang awalan subnet IPv6 harus antara 0 dan 128",
"form_enter_rate_limit_subnet_len":"Masukkan panjang awalan subnet untuk pembatasan kecepatan",
"rate_limit_whitelist":"Daftar pembatasan tarif yang diizinkan",
"rate_limit_whitelist_desc":"Alamat IP dikecualikan dari pembatasan tarif",
"rate_limit_whitelist_placeholder":"Masukkan satu alamat IP per baris",
"blocking_ipv4_desc":"Alamat IP yang akan dikembalikan untuk permintaan A yang diblokir",
"blocking_ipv6_desc":"Alamat IP yang akan dikembalikan untuk permintaan AAAA yang diblokir",
"blocking_mode_default":"Standar: Tanggapi dengan alamat IP nol (0.0.0.0 untuk A; :: untuk AAAA) saat diblokir oleh aturan gaya Adblock; tanggapi dengan alamat IP yang ditentukan dalam aturan ketika diblokir oleh aturan /etc/hosts-style",
"blocking_mode_refused":"DITOLAK: Respon dengan kode DITOLAK",
"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)",
@@ -318,7 +332,7 @@
"theme_auto":"Auto",
"theme_light":"Terang",
"theme_dark":"Gelap",
"upstream_dns_client_desc":"Jika Anda biarkan bidang ini kosong, AdGuard Home akan memakai server yang dikonfigurasi di<0>Pengaturan DNS</0>.",
"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",
@@ -328,7 +342,7 @@
"unknown_filter":"Penyaringan {{filterId}} tidak dikenal",
"known_tracker":"Pelacak yang dikenal",
"install_welcome_title":"Selamat datang di AdGuard Home!",
"install_welcome_desc":"AdGuard Home adalah sebuah server DNS pemblokiran iklan dan pelacak di jaringan. Tujuannya adalah memungkinkan anda mengkontrol seluruh jaringan dan semua perangkat anda, dan ini tidak membutuhkan aplikasi tambahan di klien",
"install_welcome_desc":"AdGuard Home adalah server DNS pemblokir iklan dan pelacak di seluruh jaringan. Tujuannya untuk memungkinkan Anda mengendalikan seluruh jaringan dan semua perangkat Anda, dan tidak perlu menggunakan program sisi klien.",
"install_submit_desc":"Prosedur pengaturan telah selesai, dan anda siap untuk mulai menggunakan AdGuard Home.",
"install_devices_router":"Router",
"install_devices_router_desc":"Setelan ini akan secara otomatis mencakup semua perangkat yang terhubung ke router rumah anda dan anda tak perlu mengkonfigurasikan secara manual.",
"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_2":"Temukan pengaturan DHCP / DNS. Cari huruf DNS di sebelah bidang yang memungkinkan dua atau tiga set angka, masing-masing dipecah menjadi empat grup dengan satu hingga tiga digit.",
"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_ios_list_2":"Pilih Wi-Fi di menu sebelah kiri (tidak mungkin untuk mengkonfigurasi DNS untuk jaringan seluler).",
"install_devices_ios_list_3":"Ketuk nama jaringan yang saat ini aktif.",
"install_devices_ios_list_4":"Di bidang DNS, masukkan alamat server AdGuard Home anda.",
"install_devices_ios_list_4":"Di kolom DNS, masukkan alamat server AdGuard Home Anda.",
"get_started":"Mari mulai",
"next":"Selanjutnya",
"open_dashboard":"Buka Beranda",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Nama host",
"encryption_reset":"Anda yakin ingin mengatur ulang pengaturan enkripsi?",
"encryption_warning":"Peringatan",
"encryption_plain_dns_enable":"Aktifkan DNS biasa",
"encryption_plain_dns_desc":"DNS biasa diaktifkan secara standar. Anda dapat menonaktifkannya untuk memaksa semua perangkat menggunakan DNS terenkripsi. Untuk melakukan ini, Anda harus mengaktifkan setidaknya satu protokol DNS terenkripsi",
"encryption_plain_dns_error":"Untuk menonaktifkan DNS biasa, aktifkan setidaknya satu protokol DNS terenkripsi",
"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",
@@ -427,7 +444,7 @@
"fix":"Perbaiki",
"dns_providers":"Berikut adalah <0>daftar penyedia DNS yang dikenal</0> untuk dipilih.",
"update_now":"Perbarui sekarang",
"update_failed":"Pembaruan otomatis gagal. Silahkan <a>ikuti petunjuk ini</a> untuk perbarui secara manual.",
"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",
@@ -437,7 +454,7 @@
"table_client":"Klien",
"table_name":"Nama",
"save_btn":"Simpan",
"client_add":"Tambah Klien",
"client_add":"Tambahkan Klien",
"client_new":"Klien Baru",
"client_edit":"Ubah Klien",
"client_identifier":"Identifikasi",
@@ -447,9 +464,10 @@
"form_enter_subnet_ip":"Masukkan alamat IP di subnet \"{{cidr}}\"",
"client_deleted":"Klien \"{{key}}\" berhasil dihapus",
"client_added":"Klien \"{{key}}\" berhasil ditambahkan",
@@ -464,7 +482,7 @@
"access_allowed_title":"Klien yang diizinkan",
"access_allowed_desc":"Daftar CIDR, alamat IP, atau <a>ClientID</a>. Jika daftar ini memiliki entri, AdGuard Home hanya akan menerima permintaan dari klien ini.",
"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. Bidang ini diabaikan jika ada entri di klien yang 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_settings_saved":"Pengaturan akses berhasil disimpan",
@@ -473,7 +491,7 @@
"check_updates_now":"Periksa pembaruan sekarang",
"version_request_error":"Pemeriksaan pembaruan gagal. Harap periksa koneksi internet anda.",
"dns_privacy":"DNS Privasi",
"setup_dns_privacy_1":"<0>DNS-over-TLS:</0> Memakai <1>{{address}}</1> string.",
"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.",
@@ -493,7 +511,7 @@
"rewrite_added":"DNS rewrite untuk \"{{key}}\" berhasil ditambahkan",
"rewrite_deleted":"DNS rewrite untuk \"{{key}}\" berhasil dihapus",
"rewrite_updated":"Penulisan ulang DNS berhasil diperbarui",
"rewrite_add":"Tambah DNS rewrite",
"rewrite_add":"Tambahkan penulisan ulang DNS",
"rewrite_edit":"Edit penulisan ulang DNS",
"rewrite_not_found":"Tidak ada DNS rewrite ditemukan",
"rewrite_confirm_delete":"Apakah anda yakin ingin menghapus DNS rewrite untuk \"{{key}}\"?",
@@ -530,7 +548,7 @@
"domain":"Domain",
"ecs":"ECS",
"punycode":"Kode kecil",
"answer":"Jawab",
"answer":"Jawaban",
"filter_added_successfully":"Filter telah berhasil ditambahkan",
"filter_removed_successfully":"Daftar ini telah sukses dihapus",
"filter_updated":"Daftar telah sukses diperbarui",
@@ -582,10 +600,10 @@
"fastest_addr":"Alamat IP tercepat",
"fastest_addr_desc":"Kuiri semua server DNS dan kembalikan alamat IP tercepat diantara semua tanggapan. Ini memperlambat pencarian DNS Sebagai Rumah AdGuard harus menunggu tanggapan dari semua server DNS, tapi meningkatkan konektivitas keseluruhan.",
"autofix_warning_text":"Apabila anda menekan \"Perbaiki\", AdGuardHome akan mengatur sistem anda untuk menggunakan server DNS AdGuardHome.",
"autofix_warning_list":"Ini akan melakukan tugas berikut: <0>Nonaktifkan sistem DNSStubListener</0> <0>Atur alamat server DNS ke 127.0.0.1</0> <0>Ganti target tautan simbolis /etc/resolv.conf pakai /run/systemd/resolve/resolv.conf</0> <0>Hentikan DNSStubListener (muat ulang layanan sistemd-resolve service)</0>",
"autofix_warning_list":"Ini akan melakukan tugas berikut: <0>Nonaktifkan sistem DNSStubListener</0> <0>Atur alamat server DNS ke 127.0.0.1</0> <0>Ganti target tautan simbolis /etc/resolv.conf dengan /run/systemd/resolve/resolv.conf</0> <0>Hentikan DNSStubListener (muat ulang layanan sistemd-resolved)</0>",
"autofix_warning_result":"Hasilnya, semua permintaan DNS dari sistem anda akan diproses oleh AdGuardHome secara standar.",
"tags_title":"Tag",
"tags_desc":"Anda dapat memilih tag sesuai dengan klien. Tag dapat dimasukkan dalam aturan pemfilteran dan memungkinkan Anda untuk menerapkannya lebih akurat. <0>Pelajari lebih</0>.",
"tags_desc":"Anda dapat memilih tag yang sesuai dengan klien. Sertakan tag dalam aturan pemfilteran untuk menerapkannya dengan lebih akurat. <0>Pelajari lebih lanjut</0>.",
"form_select_tags":"Pilih tag klien",
"check_title":"Periksa penyaringan",
"check_desc":"Periksa apakah nama host telah tersaring.",
@@ -593,7 +611,7 @@
"form_enter_host":"Masukkan nama host",
"filtered_custom_rules":"Tersaring oleh aturan penyaring Buatan",
"choose_from_list":"Pilih dari daftar",
"add_custom_list":"Tambah daftar buatan",
"add_custom_list":"Tambahkan daftar kustom",
"host_whitelisted":"Host didaftar putihkan",
"check_ip":"Alamat IP: {{ip}}",
"check_cname":"CNAME: {{cname}}",
@@ -603,8 +621,8 @@
"check_not_found":"Tidak di temukan di daftar penyaringan anda",
"client_confirm_block":"Apa anda yakin ingin mem-blokir klien ini \"{{ip}}\"?",
"client_confirm_unblock":"Apa anda yakin ingin meng-unblock klien ini \"{{ip}}\"?",
"client_blocked":"Klien \"{{ip}}\" sukses diblokir",
"client_unblocked":"Klien \"{{ip}}\" sukses di unblock",
"client_blocked":"Klien \"{{ip}}\" berhasil diblokir",
"client_unblocked":"Klien \"{{ip}}\" berhasil membuka blokir",
"static_ip":"Alamat IP statis",
"static_ip_desc":"AdGuard Home adalah server jadi perlu alamat IP statis agar berfungsi dengan benar. Jika tidak, pada titik tertentu, router Anda dapat menetapkan alamat IP yang berbeda untuk perangkat ini.",
"set_static_ip":"Atur alamat IP statik",
@@ -622,8 +640,8 @@
"show_whitelisted_responses":"Dalam Daftar Putih",
"show_processed_responses":"Terproses",
"blocked_safebrowsing":"Diblokir oleh Penjelajahan Aman",
"blocked_adult_websites":"Diblok oleh Kontrol Orang tua",
"blocked_threats":"Blokir Ancaman",
"blocked_adult_websites":"Diblokir oleh Kontrol Orang Tua",
"blocked_threats":"Ancaman terblokir",
"allowed":"Dibolehkan",
"filtered":"Tersaring",
"rewritten":"Tulis ulang",
@@ -637,7 +655,7 @@
"enter_cache_size":"Masukkan ukuran cache (bytes)",
"example_multiple_upstreams_reserved":"upstream multipli <0>per domini specifici</0>;",
"example_upstream_comment":"un commento.",
"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. 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",
@@ -143,7 +144,8 @@
"enforced_save_search":"Ricerca sicura forzata",
"number_of_dns_query_to_safe_search":"Numero di richieste DNS dai motori di ricerca per i quali la Ricerca Sicura è stata forzata",
"average_processing_time":"Tempo di elaborazione medio",
"processing_time":"Tempo di elaborazione",
"average_upstream_response_time":"Tempo medio di risposta upstream",
"response_time":"Tempo di risposta",
"average_processing_time_hint":"Tempo medio in millisecondi per elaborare una richiesta DNS",
"block_domain_use_filters_and_hosts":"Blocca domini utilizzando filtri e file hosts",
"filters_block_toggle_hint":"Puoi impostare le regole di blocco nelle impostazioni dei <a>Filtri</a>.",
@@ -234,6 +236,7 @@
"updated_upstream_dns_toast":"I server upstream sono stati salvati correttamente",
"dns_test_ok_toast":"I server DNS specificati funzionano correttamente",
"dns_test_not_ok_toast":"Server \"{{key}}\": non può essere utilizzato, assicurati di averlo digitato correttamente",
"dns_test_parsing_error_toast":"Sezione {{section}}: riga {{line}}: non può essere usata, controlla se l'hai scritta correttamente",
"dns_test_warning_toast":"Upstream \"{{key}}\" non risponde alle richieste di test e potrebbe non funzionare correttamente",
"unblock":"Sblocca",
"block":"Blocca",
@@ -241,6 +244,7 @@
"allow_this_client":"Consenti questo client",
"block_for_this_client_only":"Blocca solo per questo client",
"unblock_for_this_client_only":"Sblocca solo per questo client",
"add_persistent_client":"Aggiungi come client persistente",
"time_table_header":"Ora",
"date":"Data",
"domain_name_table_header":"Nome dominio",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Usa IP personalizzato per EDNS",
"edns_use_custom_ip_desc":"Consentire l'uso di un IP personalizzato per EDNS",
"rate_limit_desc":"Il numero di richieste al secondo consentite da un singolo client. Impostare questo valore a 0 rimuove le limitazioni.",
"rate_limit_subnet_len_ipv4":"Lunghezza prefisso di sottorete per indirizzi IPv4",
"rate_limit_subnet_len_ipv4_desc":"Lunghezza prefisso sottorete per indirizzi IPv4 usati per la limitazione della velocità. Valore predefinito 24",
"rate_limit_subnet_len_ipv4_error":"La lunghezza del prefisso di sottorete IPv4 deve essere compresa tra 0 e 32",
"rate_limit_subnet_len_ipv6":"Lunghezza prefisso di sottorete per indirizzi IPv6",
"rate_limit_subnet_len_ipv6_desc":"Lunghezza prefisso di sottorete per indirizzi IPv6 usati per la limitazione della velocità. Valore predefinito 56",
"rate_limit_subnet_len_ipv6_error":"La lunghezza del prefisso di sottorete IPv6 deve essere compresa tra 0 e 128",
"form_enter_rate_limit_subnet_len":"Inserisci lunghezza prefisso di sottorete per limitazione velocità",
"rate_limit_whitelist":"Lista consentita per limitazione velocità",
"rate_limit_whitelist_desc":"Indirizzi IP esclusi dalla limitazione della velocità",
"rate_limit_whitelist_placeholder":"Inserisci un indirizzo IP per riga",
"blocking_ipv4_desc":"Indirizzo IP per una richiesta DNS IPv4 bloccata",
"blocking_ipv6_desc":"Indirizzo IP restituito per una richiesta DNS IPv6 bloccata",
"blocking_mode_default":"Risponde con un indirizzo IP pari a zero (0.0.0.0 per A; :: per AAAA) quando bloccato da una regola in stile Blocca-annunci; risponde con l'indirizzo IP specificato nella regola quando bloccato da una regola in stile /etc/hosts",
"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",
"encryption_reset":"Sei sicuro di voler ripristinare le impostazioni di crittografia?",
"encryption_warning":"Attenzione",
"encryption_plain_dns_enable":"Abilita DNS semplice",
"encryption_plain_dns_desc":"Il DNS semplice è abilitato per impostazione predefinita. Puoi disabilitarlo per forzare tutti i dispositivi a usare DNS crittografati. Per fare ciò è necessario abilitare almeno un protocollo DNS crittografato",
"encryption_plain_dns_error":"Per disabilitare il DNS semplice, abilitare almeno un protocollo DNS crittografato",
"topline_expiring_certificate":"Il tuo certificato SSL sta per scadere. Aggiorna le<0> Impostazioni di crittografia </ 0>.",
"topline_expired_certificate":"Il tuo certificato SSL è scaduto. Aggiorna le <0> Impostazioni di crittografia </ 0>.",
"form_error_port_range":"Immettere il valore della porta nell'intervallo 80-65535",
@@ -429,7 +446,7 @@
"update_now":"Aggiorna ora",
"update_failed":"Aggiornamento automatico non riuscito. Ti suggeriamo di <a>seguire questi passaggi</a> per aggiornare manualmente.",
"manual_update":"Ti invitiamo a <a>seguire questi passaggi</a> per aggiornare manualmente.",
"processing_update":"Perfavore aspetta, AdGuard Home si sta aggiornando",
"processing_update":"Attendi perfavore, AdGuard Home si sta aggiornando",
"clients_title":"Client persistenti",
"clients_desc":"Configura le registrazioni dei client persistenti per i dispositivi connessi ad AdGuard Home",
"settings_global":"Globale",
@@ -450,6 +467,7 @@
"form_add_id":"Aggiungi identificatore",
"form_client_name":"Inserisci nome client",
"name":"Nome",
"client_name":"Client {{id}}",
"client_global_settings":"Utilizza le impostazioni globali",
"local_ptr_desc":"AdGuard Home がプライベート PTR、SOA、および NS リクエストに使用するDNSサーバー。プライベートIP 範囲内のサブネット (「192.168.12.34」など) を含む ARPA ドメインを要求し、プライベート IP アドレスを持つクライアントから来たリクエストが、プライベートリクエストとみなされます。本設定が特に指定されていない場合、OSのデフォルトDNSリゾルバ(AdGuard Home の IP アドレスを除く)が使用されます。",
"example_multiple_upstreams_reserved":"<0>특정 도메인</0>에 대한 여러 업스트림",
"example_upstream_comment":"댓글.",
"upstream_parallel":"쿼리 처리 속도를 높이려면 모든 업스트림 서버에서 동시에 병렬 쿼리를 사용해주세요.",
"parallel_requests":"병렬 처리 요청",
"load_balancing":"로드 밸런싱",
"load_balancing_desc":"한 번에 하나의 서버씩 질의합니다. AdGuard Home은 가중 랜덤 알고리즘를 사용해서 가장 빠른 서버가 자주 사용되도록 서버를 선택합니다.",
"load_balancing_desc":"한 번에 하나의 업스트림 서버를 쿼리합니다. 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 서버 활성화됨",
@@ -143,7 +144,8 @@
"enforced_save_search":"세이프서치 강제",
"number_of_dns_query_to_safe_search":"세이프서치가 적용된 검색 엔진에 대해 DNS 요청 수",
"average_processing_time":"평균처리 시간",
"processing_time":"처리 시간",
"average_upstream_response_time":"평균 업스트림 응답 시간",
"response_time":"응답 시간",
"average_processing_time_hint":"DNS 요청 처리시 평균 시간(밀리초)",
"block_domain_use_filters_and_hosts":"필터 및 호스트 파일을 사용하여 도메인 차단",
"filters_block_toggle_hint":"차단규칙<a>필터</a>을 설정할 수 있습니다.",
@@ -234,6 +236,7 @@
"updated_upstream_dns_toast":"업스트림 서버가 성공적으로 저장되었습니다",
"dns_test_ok_toast":"지정된 DNS 서버가 올바르게 작동하고 있습니다.",
"dns_test_not_ok_toast":"서버 '{{key}}': 사용할 수 없습니다, 제대로 작성했는지 확인하세요",
"dns_test_parsing_error_toast":"섹션 {{section}}: 줄 {{line}}: 사용할 수 없으며, 올바르게 작성했는지 확인하세요.",
"dns_test_warning_toast":"업스트림 '{{key}}'이(가) 테스트 요청에 응답하지 않으며 제대로 작동하지 않을 수 있습니다",
"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. 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.",
"block_for_this_client_only":"Alleen voor deze cliënt blokkeren",
"unblock_for_this_client_only":"Alleen voor deze cliënt deblokkeren",
"add_persistent_client":"Toevoegen als permanente client",
"time_table_header":"Tijd",
"date":"Datum",
"domain_name_table_header":"Domein naam",
@@ -250,8 +254,8 @@
"response_code":"Reactiecode",
"client_table_header":"Gebruiker",
"empty_response_status":"Leeg",
"show_all_filter_type":"Toon alles",
"show_filtered_type":"Toon gefilterde",
"show_all_filter_type":"Alles weergeven",
"show_filtered_type":"Gefilterde weergeven",
"no_logs_found":"Geen logboeken gevonden",
"refresh_btn":"Verversen",
"previous_btn":"Vorige",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Aangepast IP-adres gebruiken voor EDNS",
"edns_use_custom_ip_desc":"Toestaan om aangepast IP-adres voor EDNS te gebruiken",
"rate_limit_desc":"Het aantal verzoeken per seconde toegelaten per toestel. 0 betekent onbeperkt.",
"rate_limit_subnet_len_ipv4":"Lengte subnetvoorvoegsel voor IPv4-adressen",
"rate_limit_subnet_len_ipv4_desc":"Lengte subnetvoorvoegsel voor IPv4-adressen die worden gebruikt voor snelheidsbeperking. De standaardwaarde is 24",
"rate_limit_subnet_len_ipv4_error":"De lengte van het IPv4-subnetvoorvoegsel moet tussen 0 en 32 liggen",
"rate_limit_subnet_len_ipv6":"Lengte subnetvoorvoegsel voor IPv6-adressen",
"rate_limit_subnet_len_ipv6_desc":"Lengte subnetvoorvoegsel voor IPv6-adressen die worden gebruikt voor snelheidsbeperking. De standaardwaarde is 56",
"rate_limit_subnet_len_ipv6_error":"De lengte van het IPv6-subnetvoorvoegsel moet tussen 0 en 128 liggen",
"form_enter_rate_limit_subnet_len":"Voer de lengte van het subnetvoorvoegsel in voor snelheidsbeperking",
"rate_limit_whitelist":"Toelatingslijst voor snelheidsbeperking",
"rate_limit_whitelist_desc":"IP-adressen uitgesloten van snelheidsbeperking",
"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 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",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Hostnamen",
"encryption_reset":"Ben je zeker dat je de encryptie instellingen wil resetten?",
"encryption_warning":"Waarschuwing",
"encryption_plain_dns_enable":"Gewone DNS inschakelen",
"encryption_plain_dns_desc":"Gewone DNS is standaard ingeschakeld. Je kunt het uitschakelen om alle apparaten te dwingen versleutelde DNS te gebruiken. Om dit te doen, moet je ten minste één versleuteld DNS-protocol inschakelen",
"encryption_plain_dns_error":"Als je gewone DNS wilt uitschakelen, schakel je ten minste één versleuteld DNS-protocol in",
"topline_expiring_certificate":"Jouw SSL-certificaat vervalt binnenkort. Werk de <0>encryptie-instellingen</0> bij.",
"topline_expired_certificate":"Jouw SSL-certificaat is vervallen. Werk de <0>encryptie-instellingen</0> bij.",
"form_error_port_range":"Poortnummer invoeren tussen 80 en 65535",
"client_deleted":"Gebruiker \"{{key}}\" met succes verwijderd",
"client_added":"Gebruiker \"{{key}}\" met succes toegevoegd",
@@ -477,7 +495,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.",
"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",
@@ -12,14 +13,14 @@
"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.",
"rate_limit_whitelist_desc":"Adresy IP wykluczone z ograniczania prędkości",
"rate_limit_whitelist_placeholder":"Wprowadź po jednym adresie IP w każdym wierszu",
"blocking_ipv4_desc":"Adres IP, który ma zostać zwrócony w przypadku zablokowanego żądania A",
"blocking_ipv6_desc":"Adres IP, który ma zostać zwrócony w przypadku zablokowanego żądania AAAA",
"blocking_mode_default":"Domyślna: Odpowiedz z zerowym adresem IP (0.0.0.0 dla A; :: dla AAAA) po zablokowaniu przez regułę Adblock; odpowiedź adresem IP wpisanym w regule, jeśli jest blokowany przez regułę w stylu /etc/hosts",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Nazwy hostów",
"encryption_reset":"Czy na pewno chcesz zresetować ustawienia szyfrowania?",
"encryption_warning":"Ostrzeżenie",
"encryption_plain_dns_enable":"Włącz zwykły DNS",
"encryption_plain_dns_desc":"Zwykły DNS jest domyślnie włączony. Możesz go wyłączyć, aby zmusić wszystkie urządzenia do korzystania z szyfrowanego DNS. Aby to zrobić, musisz włączyć co najmniej jeden szyfrowany protokół DNS",
"encryption_plain_dns_error":"Aby wyłączyć zwykły DNS, włącz co najmniej jeden szyfrowany protokół DNS",
"topline_expiring_certificate":"Twój certyfikat SSL wkrótce wygaśnie. Zaktualizuj <0>Ustawienia szyfrowania</0>.",
"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. 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",
@@ -143,7 +144,8 @@
"enforced_save_search":"Forçar pesquisa segura",
"number_of_dns_query_to_safe_search":"O número de solicitações de DNS para mecanismos de pesquisa para os quais a pesquisa segura foi aplicada",
"average_processing_time":"Tempo médio de processamento",
"processing_time":"Tempo de processamento",
"average_upstream_response_time":"Tempo médio de resposta upstream",
"response_time":"Tempo de resposta",
"average_processing_time_hint":"Tempo médio em milissegundos no processamento de uma solicitação DNS",
"block_domain_use_filters_and_hosts":"Bloquear domínios usando arquivos de filtros e hosts",
"filters_block_toggle_hint":"Você pode configurar as regras de bloqueio nas configurações de <a>Filtros</a>.",
@@ -234,6 +236,7 @@
"updated_upstream_dns_toast":"Servidores DNS primário salvos com sucesso",
"dns_test_ok_toast":"Os servidores DNS especificados estão funcionando corretamente",
"dns_test_not_ok_toast":"O servidor \"{{key}}\": não pôde ser utilizado. Por favor, verifique se você escreveu corretamente",
"dns_test_parsing_error_toast":"A seção {{section}}: linha {{line}}: não pôde ser usada. Verifique se foi escrita corretamente",
"dns_test_warning_toast":"Servidor DNS primário \"{{key}}\" não responde aos Solicitações de teste e pode não funcionar corretamente",
"unblock":"Desbloquear",
"block":"Bloquear",
@@ -241,6 +244,7 @@
"allow_this_client":"Permitir este cliente",
"block_for_this_client_only":"Bloquear apenas para este cliente",
"unblock_for_this_client_only":"Desbloquear apenas para este cliente",
"add_persistent_client":"Adicionar como cliente persistente",
"time_table_header":"Data",
"date":"Data",
"domain_name_table_header":"Nome de domínio",
@@ -301,13 +305,23 @@
"download_mobileconfig_dot":"BAixar .mobileconfig para DNS-sobre-TLS",
"download_mobileconfig":"Baixar arquivo de configuração",
"plain_dns":"DNS simples",
"form_enter_rate_limit":"Insira a taxa limite",
"rate_limit":"Taxa limite",
"form_enter_rate_limit":"Insira a velocidade limite",
"rate_limit":"Velocidade limite",
"edns_enable":"Ativar a sub-rede do cliente EDNS",
"edns_cs_desc":"Adicione a opção de sub-rede de cliente EDNS (ECS) às solicitações de servidor DNS primário e registre os valores enviados pelos clientes no registro de consulta.",
"edns_use_custom_ip":"Usar IP personalizado para EDNS",
"edns_use_custom_ip_desc":"Permitir o uso de IP personalizado para EDNS",
"rate_limit_desc":"O número de solicitações por segundo permitidas por cliente. Definir como 0 significa que não há limite.",
"rate_limit_subnet_len_ipv4":"Comprimento do prefixo de sub-rede para endereços IPv4",
"rate_limit_subnet_len_ipv4_desc":"Comprimento do prefixo de sub-rede para endereços IPv4 usados para limitação de velocidade. O padrão é 24",
"rate_limit_subnet_len_ipv4_error":"O comprimento do prefixo da sub-rede IPv4 deve estar entre 0 e 32",
"rate_limit_subnet_len_ipv6":"Comprimento do prefixo de sub-rede para endereços IPv6",
"rate_limit_subnet_len_ipv6_desc":"Comprimento do prefixo de sub-rede para endereços IPv6 usados para limitação de velocidade. O padrão é 56",
"rate_limit_subnet_len_ipv6_error":"O comprimento do prefixo da sub-rede IPv6 deve estar entre 0 e 128",
"form_enter_rate_limit_subnet_len":"Insira o comprimento do prefixo da sub-rede para limitação de taxa",
"rate_limit_whitelist":"Lista de permissões de limitação de velocidade",
"rate_limit_whitelist_desc":"Endereços IP excluídos da limitação de velocidade",
"rate_limit_whitelist_placeholder":"Insira um endereço IP por linha",
"blocking_ipv4_desc":"Endereço de IP a ser retornado para uma solicitação bloqueada",
"blocking_ipv6_desc":"Endereço de IP a ser retornado para uma solicitação AAAA bloqueada",
"blocking_mode_default":"Padrão: Responder com zero endereço IP (0.0.0.0 para A; :: para AAAA) quando bloqueado pela regra de estilo Adblock; responde com o endereço IP especificado na regra quando bloqueado pela regra /etc/hosts-style",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Nomes dos servidores",
"encryption_reset":"Você tem certeza de que deseja redefinir a configuração de criptografia?",
"encryption_warning":"Aviso",
"encryption_plain_dns_enable":"Ativar DNS simples (sem criptografia)",
"encryption_plain_dns_desc":"O DNS simples (sem criptografia) está ativado por padrão. Você pode desativá-lo para forçar todos os dispositivos a usar DNS criptografado. Para fazer isso, você deve ativar pelo menos um protocolo DNS criptografado",
"encryption_plain_dns_error":"Para desativar o DNS simples, ative pelo menos um protocolo DNS criptografado",
"topline_expiring_certificate":"Seu certificado SSL está prestes a expirar. Atualize suas <0>configurações de criptografia</]0>",
"topline_expired_certificate":"Seu certificado SSL está expirado. Atualize suas <0>configurações de criptografia</0>",
"form_error_port_range":"Digite um número de porta entre 80 e 65535",
"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 a montante de cada vez. O AdGuard Home usa um algoritmo aleatório ponderado para selecionar servidores com o menor número de pesquisas com falha 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",
@@ -143,7 +144,8 @@
"enforced_save_search":"Forçar pesquisa segura",
"number_of_dns_query_to_safe_search":"O número de solicitações de DNS para motores de busca para os quais a pesquisa segura foi aplicada",
"average_processing_time":"Tempo médio de processamento",
"processing_time":"Tempo de processamento",
"average_upstream_response_time":"Tempo médio de resposta upstream",
"response_time":"Tempo de resposta",
"average_processing_time_hint":"Tempo médio em milissegundos no processamento de uma solicitação DNS",
"block_domain_use_filters_and_hosts":"Bloquear domínios usando ficheiros de filtros e hosts",
"filters_block_toggle_hint":"Pode configurar as regras de bloqueio nas configurações de <a>Filtros</a>.",
@@ -234,6 +236,7 @@
"updated_upstream_dns_toast":"Servidores DNS primário guardados com sucesso",
"dns_test_ok_toast":"Os servidores DNS especificados estão a funcionar corretamente",
"dns_test_not_ok_toast":"O servidor \"{{key}}\": não pôde ser utilizado. Por favor, verifique se o escreveu corretamente",
"dns_test_parsing_error_toast":"A seção {{section}}: linha {{line}}: não pôde ser usada. Verifique se foi escrita corretamente",
"dns_test_warning_toast":"Servidor DNS primário \"{{key}}\" não responde aos solicitações de teste e pode não funcionar corretamente",
"unblock":"Desbloquear",
"block":"Bloquear",
@@ -241,6 +244,7 @@
"allow_this_client":"Permitir este cliente",
"block_for_this_client_only":"Bloquear apenas para este cliente",
"unblock_for_this_client_only":"Desbloquear apenas para este cliente",
"add_persistent_client":"Adicionar como cliente persistente",
"time_table_header":"Data",
"date":"Data",
"domain_name_table_header":"Nome do domínio",
@@ -301,13 +305,23 @@
"download_mobileconfig_dot":"Transferir .mobileconfig para DNS-sobre-TLS",
"download_mobileconfig":"Transferir ficheiro de configuração",
"plain_dns":"DNS simples",
"form_enter_rate_limit":"Insira o limite de taxa",
"rate_limit":"Limite de taxa",
"form_enter_rate_limit":"Insira o limite de velocidade",
"rate_limit":"Limite de velocidade",
"edns_enable":"Ativar a sub-rede do cliente EDNS",
"edns_cs_desc":"Adicione a opção de sub-rede de cliente EDNS (ECS) às solicitações de servidor DNS primário e registre os valores enviados pelos clientes no registo de consulta.",
"edns_use_custom_ip":"Usar IP personalizado para EDNS",
"edns_use_custom_ip_desc":"Permitir a utilização de IP personalizado para EDNS",
"rate_limit_desc":"O número de solicitações por segundo permitido por cliente. Configurando para 0 significa sem limite.",
"rate_limit_subnet_len_ipv4":"Comprimento do prefixo de sub-rede para endereços IPv4",
"rate_limit_subnet_len_ipv4_desc":"Comprimento do prefixo de sub-rede para endereços IPv4 usados para limitação de velocidade. O padrão é 24",
"rate_limit_subnet_len_ipv4_error":"O comprimento do prefixo da sub-rede IPv4 deve estar entre 0 e 32",
"rate_limit_subnet_len_ipv6":"Comprimento do prefixo de sub-rede para endereços IPv6",
"rate_limit_subnet_len_ipv6_desc":"Comprimento do prefixo de sub-rede para endereços IPv6 usados para limitação de velocidade. O padrão é 56",
"rate_limit_subnet_len_ipv6_error":"O comprimento do prefixo da sub-rede IPv6 deve situar-se entre 0 e 128",
"form_enter_rate_limit_subnet_len":"Introduza o comprimento do prefixo da sub-rede para limitação da velocidade",
"rate_limit_whitelist":"Lista de permissões de limitação de velocidade",
"rate_limit_whitelist_desc":"Endereços IP excluídos da limitação de velocidade",
"rate_limit_whitelist_placeholder":"Insira um endereço IP por linha",
"blocking_ipv4_desc":"Endereço IP a ser devolvido para uma solicitação A bloqueada",
"blocking_ipv6_desc":"Endereço IP a ser devolvido para uma solicitação AAAA bloqueada",
"blocking_mode_default":"Predefinido: Responder com zero endereço IP (0.0.0.0 para A; :: para AAAA) quando bloqueado pela regra de estilo Adblock; responde com o endereço IP especificado na regra quando bloqueado pela regra /etc/hosts-style",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Nomes dos servidores",
"encryption_reset":"Tem a certeza de que deseja repor a definição de criptografia?",
"encryption_warning":"Cuidado",
"encryption_plain_dns_enable":"Habilitar DNS simples (sem criptografia)",
"encryption_plain_dns_desc":"O DNS simples (sem criptografia) está ativado por padrão. Pode desativá-lo para forçar todos os dispositivos a usar DNS criptografado. Para isso, deve ativar pelo menos um protocolo DNS criptografado",
"encryption_plain_dns_error":"Para desabilitar o DNS simples, habilite pelo menos um protocolo DNS criptografado",
"topline_expiring_certificate":"O seu certificado SSL está prestes a expirar. Atualize as suas <0>definições de criptografia</0>.",
"topline_expired_certificate":"O seu certificado SSL está expirado. Atualize as suas <0>definições de criptografia</0>.",
"form_error_port_range":"Digite um numero de porta entre 80 e 65535",
"number_of_dns_query_to_safe_search":"Numărul de interogări DNS pe motoarele de căutare pentru care a fost impusă Căutarea Sigură",
"average_processing_time":"Timpul mediu de procesare",
"processing_time":"Timp de procesare",
"average_upstream_response_time":"Timpul mediu de răspuns al serverului în amonte",
"response_time":"Timp de răspuns",
"average_processing_time_hint":"Timp mediu în milisecunde la procesarea unei cereri DNS",
"block_domain_use_filters_and_hosts":"Blocați domenii folosind filtre și fișiere hosts",
"filters_block_toggle_hint":"Puteți configura regulile de blocare în setările <a>Filtre</a>.",
@@ -234,6 +236,7 @@
"updated_upstream_dns_toast":"Serverele din amonte au fost salvate cu succes",
"dns_test_ok_toast":"Serverele DNS specificate funcționează corect",
"dns_test_not_ok_toast":"Serverul \"{{key}}\": nu a putut fi utilizat, verificați dacă l-ați scris corect",
"dns_test_parsing_error_toast":"Secțiune {{section}}: linie {{line}}: nu a putut fi folosit, vă rugăm să verificați dacă l-ați scris corect",
"dns_test_warning_toast":"„{{key}}” în amonte nu răspunde la solicitările de testare și s-ar putea să nu funcționeze corect",
"unblock":"Deblocați",
"block":"Blocați",
@@ -241,6 +244,7 @@
"allow_this_client":"Permiteți acest client",
"block_for_this_client_only":"Blocați numai pentru acest client",
"unblock_for_this_client_only":"Deblocați numai pentru acest client",
"add_persistent_client":"Adăugați ca client persistent",
"time_table_header":"Ora",
"date":"Data",
"domain_name_table_header":"Nume domeniu",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Utilizați IP personalizat pentru EDNS",
"edns_use_custom_ip_desc":"Permiteți utilizarea IP-ului personalizat pentru EDNS",
"rate_limit_desc":"Numărul de interogări pe secundă permise pe client. Setarea la 0 înseamnă că nu există limită.",
"rate_limit_subnet_len_ipv4":"Lungimea prefixului de subrețea pentru adrese IPv4",
"rate_limit_subnet_len_ipv4_desc":"Lungimea prefixului de subrețea pentru adresele IPv4 utilizate pentru limitarea ratei. Valoarea implicită este 24",
"rate_limit_subnet_len_ipv4_error":"Lungimea prefixului de subrețea IPv4 ar trebui să fie între 0 și 32",
"rate_limit_subnet_len_ipv6":"Lungimea prefixului de subrețea pentru adrese IPv6",
"rate_limit_subnet_len_ipv6_desc":"Lungimea prefixului de subrețea pentru adresele IPv6 utilizate pentru limitarea ratei. Valoarea implicită este 56",
"rate_limit_subnet_len_ipv6_error":"Lungimea prefixului de subrețea IPv6 ar trebui să fie între 0 și 128",
"form_enter_rate_limit_subnet_len":"Introduceți lungimea prefixului de subrețea pentru limitarea ratei",
"rate_limit_whitelist":"Lista permisă pentru limitarea ratei",
"rate_limit_whitelist_desc":"Adresele IP excluse de la limitarea ratei",
"rate_limit_whitelist_placeholder":"Introduceți o adresă IP per linie",
"blocking_ipv4_desc":"Adresa IP de returnat pentru o cerere A de blocare",
"blocking_ipv6_desc":"Adresa IP de returnat pentru o cerere AAAA de blocare",
"blocking_mode_default":"Implicit: Răspunde cu adresa IP (0.0.0.0 for A; :: pentru AAAA) când sunt blocate de regulă tip Adblock; răspunde cu adresa IP specificată în regulă când sunt blocate de regula tip /etc/hosts",
"upstream_parallel":"Использовать параллельные запросы ко всем серверам одновременно для ускорения обработки запроса.",
"parallel_requests":"Параллельные запросы",
"load_balancing":"Распределение нагрузки\n",
"load_balancing_desc":"Запрашивать по одному серверу за раз. AdGuard Home использует алгоритм взвешенного случайного выбора сервера, так что самый быстрый сервер используется чаще.",
"load_balancing_desc":"Запрашивайте по одному серверу за раз. 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 на все подобные запросы.",
"number_of_dns_query_to_safe_search":"Количество запросов DNS для поисковых систем, для которых был применён Безопасный поиск",
"average_processing_time":"Среднее время обработки запроса",
"processing_time":"Время обработки",
"average_upstream_response_time":"Среднее время ответа upstream-сервера",
"response_time":"Время ответа",
"average_processing_time_hint":"Среднее время для обработки запроса DNS в миллисекундах",
"block_domain_use_filters_and_hosts":"Блокировать домены с использованием фильтров и файлов hosts",
"filters_block_toggle_hint":"Вы можете настроить правила блокировки в <a>«Фильтрах»</a>.",
@@ -234,6 +236,7 @@
"updated_upstream_dns_toast":"DNS-серверы успешно обновлены",
"dns_test_ok_toast":"Указанные серверы DNS работают корректно",
"dns_test_not_ok_toast":"Сервер «{{key}}»: невозможно использовать, проверьте правильность написания",
"dns_test_parsing_error_toast":"Раздел {{section}}: строка {{line}}: невозможно использовать, проверьте правильность написания",
"dns_test_warning_toast":"Upstream «{{key}}» не отвечает на тестовые запросы и может работать некорректно",
"unblock":"Разблокировать",
"block":"Заблокировать",
@@ -241,6 +244,7 @@
"allow_this_client":"Разрешить доступ клиенту",
"block_for_this_client_only":"Заблокировать только для этого клиента",
"unblock_for_this_client_only":"Разблокировать только для этого клиента",
"add_persistent_client":"Добавить в сохранённые клиенты",
"time_table_header":"Время",
"date":"Дата",
"domain_name_table_header":"Домен",
@@ -308,6 +312,16 @@
"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":"Введите по одному адресу на строчку",
"blocking_ipv4_desc":"IP-адрес, возвращаемый при блокировке A-запроса",
"blocking_ipv6_desc":"IP-адрес, возвращаемый при блокировке AAAA-запроса",
"blocking_mode_default":"Стандартный: Отвечает с нулевым IP-адресом, (0.0.0.0 для A; :: для AAAA) когда заблокировано правилом в стиле Adblock; отвечает с IP-адресом, указанным в правиле, когда заблокировано правилом в стиле файлов hosts",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Имена хостов",
"encryption_reset":"Вы уверены, что хотите сбросить настройки шифрования?",
"encryption_plain_dns_desc":"Незашифрованный DNS включён по умолчанию. Вы можете отключить его, чтобы заставить все устройства использовать зашифрованный DNS. Для этого необходимо включить хотя бы один зашифрованный протокол DNS",
"encryption_plain_dns_error":"Чтобы отключить незашифрованный DNS, включите хотя бы один зашифрованный протокол DNS",
"topline_expiring_certificate":"Ваш SSL-сертификат скоро истекает. Обновите <0>Настройки шифрования</0>.",
"example_upstream_reserved":"upstream <0>pre konkrétne domény</0>;",
"example_multiple_upstreams_reserved":"viaceré upstreamy pre <0>konkrétne domény</0>;",
"example_upstream_comment":"komentár.",
"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. 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ý",
"disabled_dhcp":"DHCP server vypnutý",
"unavailable_dhcp":"DHCP nie je dostupné",
"unavailable_dhcp_desc":"AdGuard Home nemôže vo vašom OS prevádzkovať DHCP server",
"unavailable_dhcp_desc":"AdGuard Home nemôže vo Vašom OS prevádzkovať DHCP server",
"dhcp_title":"DHCP server (experimentálne!)",
"dhcp_description":"Ak Váš smerovač neposkytuje možnosť nastaviť DHCP, môžete použiť vlastný zabudovaný DHCP server AdGuard.",
"rate_limit_whitelist_desc":"IP adresy vylúčené z obmedzenia rýchlosti",
"rate_limit_whitelist_placeholder":"Na každý riadok zadajte IP adresu jedného servera",
"blocking_ipv4_desc":"IP adresa, ktorá sa má vrátiť v prípade blokovanej žiadosti A",
"blocking_ipv6_desc":"IP adresa, ktorá sa má vrátiť v prípade blokovanej žiadosti AAAA",
"blocking_mode_default":"Predvolené: Odpovedať nulovou adresou IP (0,0.0.0 pre A; :: pre AAAA), keď je blokovaná pravidlom v štýle Adblock; odpovedať IP adresou uvedenou v pravidle, keď je blokovaná pravidlom v štýle /etc/hosts",
"encryption_plain_dns_desc":"Jednoduchý DNS je predvolene zapnutý. Môžete ho vypnúť, aby ste prinútili všetky zariadenia používať šifrovaný DNS. Ak to chcete urobiť, musíte zapnúť aspoň jeden šifrovaný DNS protokol",
"encryption_plain_dns_error":"Ak chcete vypnúť jednoduchý DNS protokol, zapnite aspoň jeden šifrovaný DNS protokol",
"topline_expiring_certificate":"Váš SSL certifikát čoskoro vyprší. Aktualizujte <0>Nastavenia šifrovania</0>.",
"client_deleted":"\"{{key}}\" klienta bol úspešne vymazaný",
"client_added":"\"{{key}}\" klienta bol úspešne pridaný",
@@ -462,9 +480,9 @@
"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_settings_saved":"Nastavenia prístupu úspešne uložené",
@@ -660,7 +678,7 @@
"use_saved_key":"Použiť predtým uložený kľúč",
"parental_control":"Rodičovská kontrola",
"safe_browsing":"Bezpečné prehliadanie",
"served_from_cache":"{{value}} <i>(prevzatá z cache pamäte)</i>",
"served_from_cache_label":"Prevzaté z cache pamäte",
"form_error_password_length":"Heslo musí mať od {{min}} do {{max}} znakov",
"anonymizer_notification":"<0>Poznámka:</0> Anonymizácia IP je zapnutá. Môžete ju vypnúť vo <1>Všeobecných nastaveniach</1>.",
"average_processing_time_hint":"Povprečni čas v milisekundah pri obdelavi zahteve DNS",
"block_domain_use_filters_and_hosts":"Onemogoči domene s filtri in gostiteljskimi datotekami",
"filters_block_toggle_hint":"Pravila zaviranja lahko nastavite v nastavitvah <a>Filtri</a>.",
@@ -234,6 +236,7 @@
"updated_upstream_dns_toast":"Gorvodni trežniki so uspešno shranjeni",
"dns_test_ok_toast":"Navedeni strežniki DNS delujejo pravilno",
"dns_test_not_ok_toast":"Ni mogoče uporabiti: strežnika \"{{key}}\". Preverite, ali ste ga pravilno napisali",
"dns_test_parsing_error_toast":"Razdelek {{section}}: vrstica {{line}}: ni bilo mogoče uporabiti, preverite, ali ste ga pravilno zapisali",
"dns_test_warning_toast":"Upstream \"{{key}}\" se ne odziva na testne zahteve in morda ne deluje pravilno",
"unblock":"Omogoči",
"block":"Onemogoči",
@@ -241,6 +244,7 @@
"allow_this_client":"Dovoli tega odjemalca",
"block_for_this_client_only":"Onemogoči samo za tega odjemalca",
"unblock_for_this_client_only":"Omogoči samo za tega odjemalca",
"add_persistent_client":"Dodaj kot vztrajnega odjemalca",
"time_table_header":"Čas",
"date":"Datum",
"domain_name_table_header":"Ime domene",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Uporabi IP po meri za EDNS",
"edns_use_custom_ip_desc":"Dovoli uporabo naslova IP po meri za EDNS",
"rate_limit_desc":"Dovoljeno število zahtev na sekundo na odjemalca. Nastavitev na 0 pomeni brez omejitve.",
"rate_limit_subnet_len_ipv4":"Dolžina predpone podomrežja za naslove IPv4",
"rate_limit_subnet_len_ipv4_desc":"Dolžina predpone podomrežja za naslove IPv4, ki se uporabljajo za omejevanje hitrosti. Privzeto je 24",
"rate_limit_subnet_len_ipv4_error":"Dolžina predpone podomrežja IPv4 mora biti med 0 in 32",
"rate_limit_subnet_len_ipv6":"Dolžina predpone podomrežja za naslove IPv4",
"rate_limit_subnet_len_ipv6_desc":"Dolžina predpone podomrežja za naslove IPv6, ki se uporabljajo za omejevanje hitrosti. Privzeta vrednost je 56",
"rate_limit_subnet_len_ipv6_error":"Dolžina podomrežne predpone IPv6 mora biti med 0 in 128",
"form_enter_rate_limit_subnet_len":"Vnesite dolžino predpone podomrežja za omejitev hitrosti",
"rate_limit_whitelist":"Seznam dovoljenih za omejevanje hitrosti",
"rate_limit_whitelist_desc":"Naslovi IP so izključeni iz omejitve hitrosti",
"rate_limit_whitelist_placeholder":"Vnesite en naslov IP na vrstico",
"blocking_ipv4_desc":"IP naslov, ki mora biti vrnjen za onemogočeno zahtevo A",
"blocking_ipv6_desc":"IP naslov, ki mora biti vrnjen za onemogočeno zahtevo AAAA",
"blocking_mode_default":"Privzeto: odgovori z ničelnim naslovom IP (0.0.0.0 za A; :: za AAAA), ko je onemogočen s pravilom v slogu Adblocka; odgovor z naslovom IP, določenim v pravilu, ko je onemogočen s pravilom /etc/hosts",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Imena gostiteljev",
"encryption_reset":"Ali ste prepričani, da želite ponastaviti nastavitve šifriranja?",
"encryption_plain_dns_desc":"Navaden DNS je privzeto omogočen. Lahko ga onemogočite, da vse naprave prisilite k uporabi šifriranega DNS-ja. Če želite to narediti, morate omogočiti vsaj en šifriran protokol DNS",
"encryption_plain_dns_error":"Da onemogočite navaden DNS, omogočite vsaj en šifriran protokol DNS",
"topline_expiring_certificate":"Vaš e digitalno potrdilo SSL bo kmalu poteklol. Posodobite <0>Nastavitve šifriranja</0>.",
"topline_expired_certificate":"Vaše digitalno potrdilo SSL je poteklo. Posodobi <0>Nastavitve šifriranja</0>.",
"form_error_port_range":"Vnesite številko vrat v razponu med 80-65535",
"example_upstream_reserved":"upstream <0>za određene domene</0>;",
"example_multiple_upstreams_reserved":"nekoliko DNS servera <0>za određene domene</0>;",
"example_upstream_comment":"komentar.",
"upstream_parallel":"Koristite paralelne upite da biste ubrzali rešavanje tako što ćete istovremeno ispitati sve uzvodne servere.",
"parallel_requests":"Paralelni zahtevi",
@@ -143,7 +144,8 @@
"enforced_save_search":"Nametni sigurno pretraživanje",
"number_of_dns_query_to_safe_search":"Broj DNS zahteva ka pretraživačima za koje je nametnuto sigurno pretraživanje",
"average_processing_time":"Prosečno vreme obrade",
"processing_time":"Vreme obrade",
"average_upstream_response_time":"Prosečno vreme odziva upstream-servera",
"response_time":"Vreme odziva",
"average_processing_time_hint":"Prosečno vreme u milisekundama za obradu DNS zahteva",
"block_domain_use_filters_and_hosts":"Blokiraj domene koristeći filtere i hosts datoteke",
"filters_block_toggle_hint":"Možete postaviti pravila blokiranja u <a>Filters</a> postavkama.",
@@ -234,6 +236,7 @@
"updated_upstream_dns_toast":"Upstream serveri su uspešno sačuvani",
"dns_test_ok_toast":"Dati DNS serveri rade ispravno",
"dns_test_not_ok_toast":"Server \"{{key}}\": se ne može koristiti. Proverite da li ste ga ispravno uneli",
"dns_test_parsing_error_toast":"Odeljak {{section}}: linija {{line}}: ne može se koristiti, molimo proverite da li ste ga ispravno napisali",
"dns_test_warning_toast":"Apstrim \"{{key}}\" ne odgovara na zahteve za testiranje i možda neće raditi kako treba",
"unblock":"Odblokiraj",
"block":"Blokiraj",
@@ -241,6 +244,7 @@
"allow_this_client":"Dozvoli ovaj klijent",
"block_for_this_client_only":"Blokiraj samo za ovaj klijent",
"unblock_for_this_client_only":"Odblokiraj samo za ovaj klijent",
"add_persistent_client":"Dodati u sačuvane klijente",
"time_table_header":"Vreme",
"date":"Datum",
"domain_name_table_header":"Ime domena",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Koristi prilagođeni IP za EDNS",
"edns_use_custom_ip_desc":"Dozvoli korišćenje prilagođenog IP-a za EDNS",
"rate_limit_desc":"Broj zahteva u sekundi dozvoljen po klijentu. Postavljanje na 0 znači da nema ograničenja.",
"rate_limit_subnet_len_ipv4":"Dužina prefixa podmreže za IPv4 adrese",
"rate_limit_subnet_len_ipv4_desc":"Dužina prefixa podmreže za IPv4 adrese koje se koriste za ograničavanje brzine. Podrazumevano je 24",
"rate_limit_subnet_len_ipv4_error":"Dužina prefixa IPv4 podmreže treba da bude između 0 i 32",
"rate_limit_subnet_len_ipv6":"Dužina prefixa podmreže za IPv6 adrese",
"rate_limit_subnet_len_ipv6_desc":"Dužina prefixa podmreže za IPv6 adrese koje se koriste za ograničavanje brzine. Podrazumevano je 56",
"rate_limit_subnet_len_ipv6_error":"Dužina prefixa IPv6 podmreže treba da bude između 0 i 128",
"form_enter_rate_limit_subnet_len":"Unesite dužinu prefixa podmreže da biste ograničili brzinu",
"rate_limit_whitelist":"Lista dozvoljenih lista za ograničavanje brzine",
"rate_limit_whitelist_desc":"IP adrese koje nisu obuhvaćene ograničenjem brzine",
"rate_limit_whitelist_placeholder":"Unesite jednu IP adresu servera po redu",
"blocking_ipv4_desc":"IP adresa koja će biti vraćena za blokirane zahteve",
"blocking_ipv6_desc":"IP adresa koja će biti vraćena za blokirane AAAA zahteve",
"blocking_mode_default":"Podrazumevano: Odgovara sa REFUSED kada je blokirano od Adblock-style pravila; odgovara sa IP adresom koja je određena u pravilu kada je blokiran od /etc/hosts-style pravila",
"upstream_parallel":"Använd parallella förfrågningar för att snabba upp dessa genom att fråga alla uppströmsservrar samtidigt.",
"parallel_requests":"Parallella förfrågningar",
"load_balancing":"Lastbalansering",
"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",
@@ -140,10 +141,11 @@
"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",
"average_processing_time_hint":"Genomsnittlig processtid i millisekunder för DNS-förfrågning",
"block_domain_use_filters_and_hosts":"Blockera domäner med filter- och värdfiler",
"filters_block_toggle_hint":"Du kan ställa in egna blockerings regler i <a>Filterinställningar</a>.",
@@ -151,7 +153,7 @@
"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.",
"dns_test_ok_toast":"Angivna DNS servrar fungerar korrekt",
"dns_test_not_ok_toast":"Server \"{{key}}\": kunde inte användas. Var snäll och kolla att du skrivit in rätt",
"dns_test_parsing_error_toast":"Avsnitt {{section}}: rad {{line}}: kunde inte användas, kontrollera att du har skrivit det korrekt",
"dns_test_warning_toast":"Uppströms \"{{key}}\" svarar inte på testförfrågningar och kanske inte fungerar korrekt",
"unblock":"Avblockera",
"block":"Blockera",
@@ -241,6 +244,7 @@
"allow_this_client":"Tillåt den här klienten",
"block_for_this_client_only":"Blockera endast för denna klient",
"unblock_for_this_client_only":"Avblockera endast för denna klient",
"add_persistent_client":"Lägg till som beständig klient",
"time_table_header":"Tid",
"date":"Datum",
"domain_name_table_header":"Domännamn",
@@ -308,6 +312,15 @@
"edns_use_custom_ip":"Använd anpassad IP för EDNS",
"edns_use_custom_ip_desc":"Tillåt att använda anpassad IP för EDNS",
"rate_limit_desc":"Antalet förfrågningar per sekund som tillåts per klient. Att sätta den till 0 innebär ingen gräns.",
"rate_limit_subnet_len_ipv4":"Prefixlängd för subnät för IPv4-adresser",
"rate_limit_subnet_len_ipv4_desc":"Subnätprefixlängd för IPv4-adresser som används för hastighetsbegränsning. Standard är 24",
"rate_limit_subnet_len_ipv4_error":"IPv4-subnätets prefixlängd ska vara mellan 0 och 32",
"rate_limit_subnet_len_ipv6":"Prefixlängd för subnät för IPv6-adresser",
"rate_limit_subnet_len_ipv6_desc":"Subnätprefixlängd för IPv6-adresser som används för hastighetsbegränsning. Standard är 56",
"rate_limit_subnet_len_ipv6_error":"IPv6-subnätets prefixlängd ska vara mellan 0 och 128",
"form_enter_rate_limit_subnet_len":"Ange subnätprefixlängd för hastighetsbegränsning",
"rate_limit_whitelist_desc":"IP-adresser uteslutna från hastighetsbegränsning",
"rate_limit_whitelist_placeholder":"Ange en IP-adress per rad",
"blocking_ipv4_desc":"IP adress som ska returneras för en blockerad A förfrågan",
"blocking_ipv6_desc":"IP adress som ska returneras för en blockerad AAAA förfrågan",
"blocking_mode_default":"Standard: Svara med noll IP-adress (0.0.0.0 för A; :: för AAAA) när det blockeras av regel i Adblock-stil; svara med IP-adressen som anges i regeln när den blockeras av regel i /etc/hosts-stil",
"example_upstream_reserved":"<0>belirli alan adları</0> için bir üst sunucusu;",
"example_multiple_upstreams_reserved":"<0>belirli alanlar için</0> birden fazla üst kaynaklar;",
"example_upstream_comment":"bir yorum.",
"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",
@@ -97,7 +98,7 @@
"filters":"Filtreler",
"filter":"Filtre",
"query_log":"Sorgu Günlüğü",
"compact":"Yoğun",
"compact":"Sık",
"nothing_found":"Hiçbir şey bulunamadı",
"faq":"SSS",
"version":"Sürüm",
@@ -143,7 +144,8 @@
"enforced_save_search":"Uygulanan güvenli arama",
"number_of_dns_query_to_safe_search":"Güvenli Aramanın uygulandığı arama motorlarına gönderilen DNS isteklerinin sayısı",
"average_processing_time":"Ortalama işlem süresi",
"processing_time":"İşlem süresi",
"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",
"updated_upstream_dns_toast":"Üst sunucular başarıyla kaydedildi",
"dns_test_ok_toast":"Belirtilen DNS sunucuları düzgün çalışıyor",
"dns_test_not_ok_toast":"Sunucu \"{{key}}\": kullanılamıyor, lütfen doğru yazdığınızdan emin olun",
"dns_test_parsing_error_toast":"{{section}} bölümü: {{line}}. satır: kullanılamadı, lütfen doğru yazdığınızı kontrol edin",
"dns_test_warning_toast":"Üst kaynak \"{{key}}\", test isteklerine yanıt vermiyor ve düzgün çalışmayabilir",
"unblock":"Engeli kaldır",
"block":"Engelle",
@@ -241,6 +244,7 @@
"allow_this_client":"Bu istemciye izin ver",
"block_for_this_client_only":"Yalnızca bu istemci için engelle",
"unblock_for_this_client_only":"Yalnızca bu istemci için engellemeyi kaldır",
"add_persistent_client":"Kalıcı istemci olarak ekle",
"time_table_header":"Saat",
"date":"Tarih",
"domain_name_table_header":"Alan adı",
@@ -308,9 +312,19 @@
"edns_use_custom_ip":"EDNS için özel IP kullan",
"edns_use_custom_ip_desc":"EDNS için özel IP kullanımına izin ver",
"rate_limit_desc":"İstemci başına izin verilen saniyedeki istek sayısı. 0 olarak ayarlamak, sınır olmadığı anlamına gelir.",
"rate_limit_subnet_len_ipv4":"IPv4 adresleri için alt ağ önek uzunluğu",
"rate_limit_subnet_len_ipv4_desc":"Hız sınırlaması için kullanılan IPv4 adreslerinin alt ağ önek uzunluğu. Varsayılan 24'tür",
"rate_limit_subnet_len_ipv4_error":"IPv4 alt ağ önek uzunluğu 0 ile 32 arasında olmalıdır",
"rate_limit_subnet_len_ipv6":"IPv6 adresleri için alt ağ önek uzunluğu",
"rate_limit_subnet_len_ipv6_desc":"Hız sınırlaması için kullanılan IPv6 adreslerinin alt ağ önek uzunluğu. Varsayılan 56'tür",
"rate_limit_subnet_len_ipv6_error":"IPv6 alt ağ önek uzunluğu 0 ile 128 arasında olmalıdır",
"form_enter_rate_limit_subnet_len":"Hız sınırlaması için alt ağ önek uzunluğunu girin",
"rate_limit_whitelist":"Hız sınırlama izin listesi",
"rate_limit_whitelist_desc":"Hız sınırlamasından hariç tutulan IP adresleri",
"rate_limit_whitelist_placeholder":"Her satıra bir IP adresi girin",
"blocking_ipv4_desc":"Engellenen bir A isteği için geri döndürülecek IP adresi",
"blocking_ipv6_desc":"Engellenen bir AAAA isteği için geri döndürülecek IP adresi",
"blocking_mode_default":"Varsayılan: Reklam engelleme tarzı kural tarafından engellendiğinde sıfır IP adresiyle (A için 0.0.0.0; :: AAAA için) yanıt verin; /etc/hosts-tarzı kural tarafından engellendiğinde, kuralda belirtilen IP adresiyle yanıt verin",
"blocking_mode_default":"Varsayılan: Reklam engelleme stili kuralı tarafından engellendiğinde sıfır IP adresiyle (A için 0.0.0.0; :: AAAA için) yanıt verin; /etc/hosts-tarzı kural tarafından engellendiğinde, kuralda belirtilen IP adresiyle yanıt verin",
"encryption_plain_dns_desc":"Düz DNS varsayılan olarak etkindir. Tüm aygıtları şifrelenmiş DNS kullanmaya zorlamak için bunu devre dışı bırakabilirsiniz. Bunu yapmak için en az bir şifrelenmiş DNS protokolünü etkinleştirmeniz gerekir",
"encryption_plain_dns_error":"Düz DNS'i devre dışı bırakmak için en az bir şifrelenmiş DNS protokolünü etkinleştirin",
"topline_expiring_certificate":"SSL sertifikanızın süresi sona üzere. <0>Şifreleme ayarlarını</0> güncelleyin.",
"topline_expired_certificate":"SSL sertifikanızın süresi sona erdi. <0>Şifreleme ayarlarını</0> güncelleyin.",
"form_error_port_range":"80-65535 aralığında geçerli bir bağlantı noktası değeri girin",
@@ -435,7 +452,7 @@
"settings_global":"Genel",
"settings_custom":"Özel",
"table_client":"İstemci",
"table_name":"Ad",
"table_name":"AdAdı",
"save_btn":"Kaydet",
"client_add":"İstemci Ekle",
"client_new":"Yeni İstemci",
@@ -449,7 +466,8 @@
"form_enter_id":"Tanımlayıcı girin",
"form_add_id":"Tanımlayıcı ekle",
"form_client_name":"İstemci ismi girin",
"name":"Ad",
"name":"Adı",
"client_name":"İstemci {{id}}",
"client_global_settings":"Genel ayarları kullan",
"client_deleted":"\"{{key}}\" istemcisi başarıyla silindi",
"client_added":"\"{{key}}\" istemcisi başarıyla eklendi",
"upstream_parallel":"Використовувати паралельні запити, щоб пришвидшити вирішення одночасною чергою всіх оригінальних серверів.",
"parallel_requests":"Паралельні запити",
@@ -67,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-сервер».",
"rate_limit_whitelist_desc":"IP-адреси, на які не поширюється обмеження швидкості",
"rate_limit_whitelist_placeholder":"Вводьте одну адресу на рядок",
"blocking_ipv4_desc":"IP-адреса, яку потрібно видати для заблокованого A запиту",
"blocking_ipv6_desc":"IP-адреса, яку потрібно видати для заблокованого АААА запиту",
"blocking_mode_default":"Усталено: відповідь із нульовою IP-адресою (0.0.0.0 для A; :: для AAAA), якщо заблоковано правилом у Adblock-стилі; відповідь зазначеною у правилі IP-адресою, якщо заблокувано правилом у hosts-стилі",
@@ -350,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 поруч із полем, в яке можна ввести два або три набори чисел, кожен з яких розбитий на чотири групи від однієї до трьох цифр.",
@@ -411,6 +425,9 @@
"encryption_hostnames":"Назви вузлів",
"encryption_reset":"Ви впевнені, що хочете скинути налаштування шифрування?",
"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",
@@ -431,7 +448,7 @@
"manual_update":"Щоб оновити самостійно, <a>виконайте ці кроки</a>.",
"processing_update":"Зачекайте будь ласка, AdGuard Home оновлюється",
"clients_title":"Постійні клієнти",
"clients_desc":"Налаштуйте пристрої, під'єднані до AdGuard Home",
"clients_desc":"Налаштуйте пристрої, які підʼєднано до AdGuard Home",
"settings_global":"Загальні",
"settings_custom":"Власні",
"table_client":"Клієнт",
@@ -450,6 +467,7 @@
"form_add_id":"Додати ідентифікатор",
"form_client_name":"Введіть ім'я клієнта",
"name":"Ім'я",
"client_name":"Клієнт {{id}}",
"client_global_settings":"Використати загальні налаштування",
"client_deleted":"Клієнта «{{key}}» успішно видалено",
"client_added":"Клієнта «{{key}}» успішно додано",
@@ -660,7 +678,7 @@
"use_saved_key":"Використати раніше збережений ключ",
"parental_control":"Батьківський контроль",
"safe_browsing":"Безпечний перегляд",
"served_from_cache":"{{value}} <i>(отримано з кешу)</i>",
"served_from_cache_label":"Отримано з кешу",
"form_error_password_length":"Пароль має містити від {{min}} до {{max}} символів",
"anonymizer_notification":"<0>Примітка:</0> IP-анонімізацію ввімкнено. Ви можете вимкнути його в <1>Загальні налаштування</1> .",
"confirm_dns_cache_clear":"Ви впевнені, що бажаєте очистити кеш DNS?",
@@ -683,7 +701,7 @@
"disable_notify_for_minutes_plural":"Вимкнення захисту на {{count}} хвилин",
"disable_notify_for_hours":"Вимкнення захисту на {{count}} годину",
"disable_notify_for_hours_plural":"Вимкнення захисту на {{count}} годин",
"disable_notify_until_tomorrow":"Відключення захисту до завтра",
"disable_notify_until_tomorrow":"Вимкнути захист до завтра",
"enable_protection_timer":"Захист буде ввімкнено о {{time}}",
"schedule_modal_description":"Цей розклад замінить усі наявні розклади на той самий день тижня. Кожен день тижня може мати тільки один період бездіяльності.",
"example_upstream_reserved":"ngược dòng <0>cho các miền cụ thể</0>;",
"example_multiple_upstreams_reserved":"nhiều máy chủ thượng nguồn <0>cho các miền cụ thể</0>;",
"example_upstream_comment":"một lời bình luận.",
"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",
@@ -143,7 +144,8 @@
"enforced_save_search":"Bắt buộc tìm kiếm an toàn",
"number_of_dns_query_to_safe_search":"Số yêu cầu DNS tới công cụ tìm kiếm đã chuyển thành tìm kiếm an toàn",
"average_processing_time":"Thời gian xử lý trung bình",
"processing_time":"Thời gian xử lý",
"average_upstream_response_time":"Thời gian phản hồi trung bình từ máy chủ thượng nguồn",
"response_time":"Thời gian đáp ứng",
"average_processing_time_hint":"Thời gian trung bình cho một yêu cầu DNS tính bằng mili giây",
"block_domain_use_filters_and_hosts":"Chặn tên miền sử dụng các bộ lọc và file hosts",
"filters_block_toggle_hint":"Bạn có thể thiết lập quy tắc chặn tại cài đặt <a>Bộ lọc</a>.",
@@ -234,6 +236,7 @@
"updated_upstream_dns_toast":"Các máy chủ thượng nguồn đã được lưu thành công",
"dns_test_ok_toast":"Máy chủ DNS có thể sử dụng",
"dns_test_not_ok_toast":"Máy chủ \"{{key}}\"': không thể sử dụng, vui lòng kiểm tra lại",
"dns_test_parsing_error_toast":"Phần {{section}}: dòng {{line}}: không thể sử dụng được, vui lòng kiểm tra xem bạn đã viết đúng chưa",
"dns_test_warning_toast":"Ngược lại \"{{key}}\" không phản hồi các yêu cầu kiểm tra và có thể không hoạt động bình thường",
"unblock":"Bỏ chặn",
"block":"Chặn",
@@ -241,6 +244,7 @@
"allow_this_client":"Cho phép ứng dụng khách này",
"block_for_this_client_only":"Chỉ chặn ứng dụng khách này",
"unblock_for_this_client_only":"Chỉ hủy chặn ứng dụng khách này",
"add_persistent_client":"Thêm làm ứng dụng khách liên tục",
"time_table_header":"Thời gian",
"date":"Ngày",
"domain_name_table_header":"Tên miền",
@@ -308,6 +312,16 @@
"edns_use_custom_ip":"Sử dụng địa chỉ IP tùy chỉnh cho EDNS",
"edns_use_custom_ip_desc":"Cho phép sử dụng địa chỉ IP tùy chỉnh cho EDNS",
"rate_limit_desc":"Số lượng yêu cầu mỗi giây mà một khách hàng được phép thực hiện (0: không giới hạn)",
"rate_limit_subnet_len_ipv4":"Độ dài tiền tố mạng con cho địa chỉ IPv4",
"rate_limit_subnet_len_ipv4_desc":"Độ dài tiền tố mạng con cho các địa chỉ IPv4 được sử dụng để giới hạn tốc độ. Mặc định là 24",
"rate_limit_subnet_len_ipv4_error":"Độ dài tiền tố mạng con IPv4 phải nằm trong khoảng từ 0 đến 32",
"rate_limit_subnet_len_ipv6":"Độ dài tiền tố mạng con cho địa chỉ IPv6",
"rate_limit_subnet_len_ipv6_desc":"Độ dài tiền tố mạng con cho các địa chỉ IPv6 được sử dụng để giới hạn tốc độ. Mặc định là 56",
"rate_limit_subnet_len_ipv6_error":"Độ dài tiền tố mạng con IPv6 phải nằm trong khoảng từ 0 đến 128",
"form_enter_rate_limit_subnet_len":"Nhập độ dài tiền tố mạng con để giới hạn tốc độ",
"rate_limit_whitelist":"Danh sách cho phép giới hạn tỷ lệ",
"rate_limit_whitelist_desc":"Địa chỉ IP bị loại trừ khỏi giới hạn tốc độ",
"rate_limit_whitelist_placeholder":"Nhập một địa chỉ IP trên mỗi dòng",
"blocking_ipv4_desc":"Địa chỉ IP được trả lại cho một yêu cầu A bị chặn",
"blocking_ipv6_desc":"Địa chỉ IP được trả lại cho một yêu cầu AAA bị chặn",
"blocking_mode_default":"Mặc định: Trả lời với NXDOMAIN khi bị chặn bởi quy tắc kiểu Adblock; phản hồi với địa chỉ IP được chỉ định trong quy tắc khi bị chặn bởi quy tắc / etc / hosts-style",
@@ -450,6 +464,7 @@
"form_add_id":"Thêm định danh",
"form_client_name":"Nhập tên máy khách",
"name":"Tên",
"client_name":"Khách hàng {{id}}",
"client_global_settings":"Sử dụng cài đặt toàn cầu",
"client_deleted":"Máy khách \"{{key}}\" đã xóa thành công",
"client_added":"Máy khách \"{{key}}\" đã thêm thành công",
@@ -722,5 +737,8 @@
"wednesday_short":"Thứ 4",
"thursday_short":"Thứ 5",
"friday_short":"Thứ 6",
"saturday_short":"Thứ 7"
"saturday_short":"Thứ 7",
"upstream_dns_cache_configuration":"Cấu hình bộ nhớ đệm upstream của các máy chủ DNS",
"enable_upstream_dns_cache":"Bật bộ nhớ cache cho cấu hình ngược dòng của máy chủ upstream của khách hàng này",
"dns_cache_size":"Kích thước bộ nhớ cache DNS, tính bằng byte"
"load_balancing_desc":"一次查询一台服务器。AdGuard Home 将使用加权随机算法来选择服务器,以便更常使用最快的服务器。",
"load_balancing_desc":"一次查询一台服务器。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 服务器已启用",
@@ -143,7 +144,8 @@
"enforced_save_search":"强制安全搜索",
"number_of_dns_query_to_safe_search":"启用强制安全搜索后对搜索引擎的 DNS 请求总数",
"average_processing_time":"平均处理时间",
"processing_time":"处理时间",
"average_upstream_response_time":"上游服务器的平均响应时间",
"response_time":"响应时间",
"average_processing_time_hint":"处理 DNS 请求的平均时间(毫秒)",
"load_balancing_desc":"一次只查詢一個伺服器。AdGuard Home 會使用加權隨機取樣來選擇使用的查詢結果,以確保速度最快的伺服器能被充分運用。",
"bootstrap_dns":"引導(Boostrap) DNS 伺服器",
"bootstrap_dns_desc":"Bootstrap DNS 伺服器用於解析您所設定的上游 DoH/DoT 解析器的 IP 地址",
"fallback_dns_title":"備用 DNS 伺服器",
"fallback_dns_desc":"備用 DNS 伺服器列表:於主要 DNS 伺服器沒有回應時使用。語法與主要 DNS 伺服器設定欄位相同。",
"fallback_dns_placeholder":"每行輸入一個備用 DNS 伺服器",
"local_ptr_title":"私人 DNS 伺服器",
"local_ptr_desc":"AdGuard Home 用於區域 PTR 查詢的 DNS 伺服器。這些伺服器將用於解析具有私人 IP 位址的用戶端的主機名稱,例如 \"192.168.12.34\",使用 rDNS。如果沒有設定,AdGuard Home 將自動使用您的系統預設 DNS 解析。",
"local_ptr_default_resolver":"AdGuard Home 預設使用以下作為 DNS 反解器:{{ip}}",
@@ -37,17 +41,19 @@
"dhcp_ipv6_settings":"DHCP IPv6 設定",
"form_error_required":"必要欄位",
"form_error_ip4_format":"無效的 IPv4 格式",
"form_error_ip6_format":"無效的 IPv6 格式",
"form_error_ip4_gateway_format":"閘道的 IPv4 位址無效",
"form_error_ip_format":"無效的 IP 位址",
"form_error_ip6_format":"無效的 IPv6 格式",
"form_error_ip_format":"無效的 IP 格式",
"form_error_mac_format":"無效的 「MAC 位址」格式",
"form_error_client_id_format":"無效的「客戶端 ID」格式",
"form_error_server_name":"無效伺服器名稱",
"form_error_subnet":"子網路 \"{{cidr}}\" 不包含 IP 位址 \"{{ip}}\"",
"dhcp_dynamic_ip_found":"您的網路介面 <0>{{interfaceName}}</0> 正在使用動態 IP,要使用 DHCP 伺服器必須指定靜態 IP 給 AdGuard。\n目前您的 IP 位址 <0>{{ipAddress}}</0>,啟用 DHCP 後此 IP 將自動設定為靜態 IP 位址。",
"dhcp_lease_added":"靜態租用 \"{{key}}\" 已新增成功",
"dhcp_lease_deleted":"靜態租用 \"{{key}}\" 已刪除成功",
"dhcp_lease_updated":"靜態租約 \"{{key}}\" 已成功更新",
"dhcp_new_static_lease":"新增靜態租用",
"dhcp_edit_static_lease":"編輯靜態租約",
"dhcp_static_leases_not_found":"找不到 DHCP 靜態租用",
"dhcp_add_static_lease":"新增靜態租用",
"dhcp_reset_leases":"重置所有 DHCP 租約",
@@ -112,7 +120,8 @@
"stats_malware_phishing":"已封鎖惡意軟體/網路釣魚",
"stats_adult":"已封鎖成人網站",
"stats_query_domain":"熱門查詢網域排行",
"for_last_24_hours":"過去 24 小時",
"for_last_hours":"在過去 {{count}} 小時",
"for_last_hours_plural":"在過去 {{count}} 小時裡",
"for_last_days":"最近 {{count}} 天內",
"for_last_days_plural":"最近 {{count}} 天內",
"stats_disabled":"已禁用統計資料。您可以從<0>設定頁面</0>打開它。",
@@ -123,15 +132,20 @@
"top_clients":"熱門用戶端排行",
"no_clients_found":"找不到用戶端",
"general_statistics":"一般統計資料",
"top_upstreams":"熱門上游伺服器",
"no_upstreams_data_found":"找不到上游數據",
"number_of_dns_query_days":"過去 {{count}} 天內 DNS 查詢總數",
"number_of_dns_query_days_plural":"過去 {{count}} 天內 DNS 查詢總數",
"number_of_dns_query_24_hours":"過去 24小時內 DNS 查詢總數",
"number_of_dns_query_hours":"過去 {{count}} 小時處理的 DNS 查詢數量",
"number_of_dns_query_hours_plural":"過去 {{count}} 小時處理的 DNS 查詢數量",
"number_of_dns_query_blocked_24_hours":"已被廣告過濾器與主機黑名單封鎖 DNS 查詢總數",
"number_of_dns_query_blocked_24_hours_by_sec":"已被 AdGuard 瀏覽安全模組封鎖的 DNS 查詢總數",
"load_balancing_desc":"每次查詢一個上游伺服器。AdGuard Home 使用它的加權隨機的演算法來選擇伺服器,以便最快的伺服器被更常使用。",
"load_balancing_desc":"一次查詢一台伺服器。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 伺服器",
"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)伺服器被啟用",
@@ -131,7 +132,7 @@
"top_clients":"熱門用戶端",
"no_clients_found":"無已發現之用戶端",
"general_statistics":"一般的統計資料",
"top_upstreams":"經常請求的上游伺服器",
"top_upstreams":"熱門上游",
"no_upstreams_data_found":"找不到上游伺服器資料",
"number_of_dns_query_days":"在最近的 {{count}} 日內已處理的 DNS 查詢之數量",
"number_of_dns_query_days_plural":"在最近的 {{count}} 日內已處理的 DNS 查詢之數量",
@@ -143,7 +144,8 @@
"enforced_save_search":"已強制執行的安全搜尋",
"number_of_dns_query_to_safe_search":"安全搜尋已被強制執行之屬於搜尋引擎的 DNS 請求之數量",
"average_processing_time":"平均的處理時間",
"processing_time":"處理時間",
"average_upstream_response_time":"平均的上游回應時間",
"response_time":"回應時間",
"average_processing_time_hint":"在處理一項 DNS 請求時以毫秒(ms)計的平均時間",
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.