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.
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.
## General recommendations
- 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].
Please don't:
- file issues about a particular filtering-rule list misbehaving. These are tracked through the [separate form for filtering issues][form].
* 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.
- 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.
* 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
* file issues about a particular filtering-rule list misbehaving. These are
tracked through the [separate form for filtering issues][form].
* send 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 once before each Beta and Release build.
Please do:
Please do:
- follow the template instructions and provide data for reproducing issues.
* 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.
* 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.
## Issues
### Search first
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,
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
### Follow the issue template
### Discuss your changes first
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.
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.
## 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.
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.
### Test your changes
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].
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
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].
### <a href="#api" id="api" name="api">API</a>
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
## <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>
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" id="comparison" name="comparison">Comparing AdGuard Home to other solutions</a>
- Choose what exactly the server blocks and permits.
### <a href="#comparison-adguard-dns" id="comparison-adguard-dns" name="comparison-adguard-dns">How is this different from public AdGuard DNS servers?</a>
- Monitor your network activity.
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:
- Add your own custom filtering rules.
* Choose what exactly the server blocks and permits.
- **Most importantly, it's your own server, and you are the only one who's in control.**
* Monitor your network activity.
### <a href="#comparison-pi-hole" id="comparison-pi-hole" name="comparison-pi-hole">How does AdGuard Home compare to Pi-Hole</a>
* Add your own custom filtering rules.
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.
* **Most importantly, it's your own server, and you are the only one who's in
control.**
> [!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.
> [!NOTE]
### <a href="#comparison-pi-hole" id="comparison-pi-hole" name="comparison-pi-hole">How does AdGuard Home compare to Pi-Hole</a>
> 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.
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.
### <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.
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
Here are some examples of what cannot be blocked by a DNS-level blocker:
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 href="#building-node" id="building-node" name="building-node">Building with Node.js 17 and later</a>
**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
In order to build AdGuard Home with Node.js 17 and later, specify `--openssl-legacy-provider` option.
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`.
```sh
exportNODE_OPTIONS=--openssl-legacy-provider
```
> [!WARNING]
> The non-standard `-j` flag is currently not supported, so building with `make -j 4` or setting your `MAKEFLAGS` to include, for example, `-j 4` is likely to break the build. If you do have your `MAKEFLAGS` set to that, and you don't want to change it, you can override it by running `make -j 1`.
Check the [`Makefile`][src-makefile] to learn about other commands.
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
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:
You may need to prepare before using these builds:
- (Linux-only) Install Qemu:
* (Linux-only) Install Qemu:
```sh
```sh
docker run --rm --privileged multiarch/qemu-user-static --reset -p yes --credential yes
docker run --rm --privileged multiarch/qemu-user-static --reset -p yes --credential yes
See the [`build-docker` target documentation][targ-docker].
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
```sh
( cd ./client/ && env NODE_ENV='development' npm run watch )
( 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.
### <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].
### <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].
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)).
* [OpenWrt LUCI app](https://github.com/kongfl888/luci-app-adguardhome) by
[@kongfl888](https://github.com/kongfl888) (originally by
- [AdGuardHome sync](https://github.com/bakito/adguardhome-sync) by [@bakito](https://github.com/bakito).
* [Prometheus exporter for AdGuard
Home](https://github.com/ebrianne/adguard-exporter) by
[@ebrianne](https://github.com/ebrianne).
- [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).
- [Asuswrt-Merlin-AdGuardHome-Installer](https://github.com/jumpsmm7/Asuswrt-Merlin-AdGuardHome-Installer) by [@jumpsmm7](https://github.com/jumpsmm7) aka [@SomeWhereOverTheRainBow](https://www.snbforums.com/members/somewhereovertherainbow.64179/).
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
1. Make sure that the message body contains a clear description of the vulnerability.
2. 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.
"dns_test_warning_toast":"Upstream «{{key}}» не адказвае на тэставыя запыты і можа не працаваць належным чынам",
"dns_test_warning_toast":"Upstream «{{key}}» не адказвае на тэставыя запыты і можа не працаваць належным чынам",
"unblock":"Адблакаваць",
"unblock":"Адблакаваць",
"block":"Заблакаваць",
"block":"Заблакаваць",
@@ -244,7 +240,6 @@
"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":"Дадаць у захаваныя кліенты",
"time_table_header":"Час",
"time_table_header":"Час",
"date":"Дата",
"date":"Дата",
"domain_name_table_header":"Дамен",
"domain_name_table_header":"Дамен",
@@ -312,15 +307,6 @@
"edns_use_custom_ip":"Выкарыстоўваць указаны IP для DNS",
"edns_use_custom_ip":"Выкарыстоўваць указаны IP для DNS",
"edns_use_custom_ip_desc":"Дазволіць выкарыстоўваць уласны IP для DNS",
"edns_use_custom_ip_desc":"Дазволіць выкарыстоўваць уласны IP для DNS",
"rate_limit_desc":"Абмежаванне на колькасць запытаў у секунду для кожнага кліента (0 — неабмежавана)",
"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":"Увядзіце па адным адрасе на радок",
"rate_limit_whitelist_placeholder":"Увядзіце па адным адрасе на радок",
"blocking_ipv4_desc":"IP-адрас, што вяртаецца пры блакаванню A-запыту",
"blocking_ipv4_desc":"IP-адрас, што вяртаецца пры блакаванню A-запыту",
"blocking_ipv6_desc":"IP-адрас, што вяртаецца пры блакаванню AAAA-запыту",
"blocking_ipv6_desc":"IP-адрас, што вяртаецца пры блакаванню AAAA-запыту",
"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>.",
"topline_expiring_certificate":"Váš SSL certifikát brzy vyprší. Aktualizujte <0>Nastavení šifrování</0>.",
"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_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>.",
"topline_expired_certificate":"Dit SSL-certifikat er udløbet. Opdatér <0>Krypteringsindstillinger</0>.",
"form_error_port_range":"Angiv portnummer i intervallet 80-65535",
"form_error_port_range":"Angiv portnummer i intervallet 80-65535",
"dns_test_not_ok_toast":"Server „{{key}}“: konnte nicht verwendet werden, bitte überprüfen Sie die korrekte Schreibweise",
"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",
"dns_test_warning_toast":"Upstream „{{key}}“ reagiert nicht auf Testanfragen und funktioniert möglicherweise nicht fehlerfrei",
"unblock":"Entsperren",
"unblock":"Entsperren",
"block":"Sperren",
"block":"Sperren",
@@ -244,7 +243,6 @@
"allow_this_client":"Diesen Client zulassen",
"allow_this_client":"Diesen Client zulassen",
"block_for_this_client_only":"Nur für diesen Client sperren",
"block_for_this_client_only":"Nur für diesen Client sperren",
"unblock_for_this_client_only":"Nur für diesen Client freigeben",
"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_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}}",
"rule_added_to_custom_filtering_toast":"Regel wurde zu den benutzerdefinierten Filterregeln hinzugefügt: {{rule}}",
@@ -425,9 +423,6 @@
"encryption_hostnames":"Hostnamen",
"encryption_hostnames":"Hostnamen",
"encryption_reset":"Möchten Sie die Verschlüsselungseinstellungen wirklich zurücksetzen?",
"encryption_reset":"Möchten Sie die Verschlüsselungseinstellungen wirklich zurücksetzen?",
"encryption_warning":"Warnhinweis",
"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_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>.",
"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",
"form_error_port_range":"Geben Sie die Portnummer zwischen 80 und 65535 ein",
"dns_test_ok_toast":"Specified DNS servers are working correctly",
"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_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",
"dns_test_warning_toast":"Upstream \"{{key}}\" does not respond to test requests and may not work properly",
"unblock":"Unblock",
"unblock":"Unblock",
"block":"Block",
"block":"Block",
@@ -244,7 +243,6 @@
"allow_this_client":"Allow this client",
"allow_this_client":"Allow this client",
"block_for_this_client_only":"Block for this client only",
"block_for_this_client_only":"Block for this client only",
"unblock_for_this_client_only":"Unblock 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",
"time_table_header":"Time",
"date":"Date",
"date":"Date",
"domain_name_table_header":"Domain name",
"domain_name_table_header":"Domain name",
@@ -425,9 +423,6 @@
"encryption_hostnames":"Hostnames",
"encryption_hostnames":"Hostnames",
"encryption_reset":"Are you sure you want to reset encryption settings?",
"encryption_reset":"Are you sure you want to reset encryption settings?",
"encryption_warning":"Warning",
"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_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>.",
"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",
"form_error_port_range":"Enter port number in the range of 80-65535",
"updated_upstream_dns_toast":"Servidores DNS de subida guardados correctamente",
"updated_upstream_dns_toast":"Servidores DNS de subida guardados correctamente",
"dns_test_ok_toast":"Los servidores DNS especificados funcionan 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_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",
"dns_test_warning_toast":"DNS de subida \"{{key}}\" no responde a las peticiones de prueba y es posible que no funcione correctamente",
"unblock":"Desbloquear",
"unblock":"Desbloquear",
"block":"Bloquear",
"block":"Bloquear",
@@ -244,7 +243,6 @@
"allow_this_client":"Permitir a este cliente",
"allow_this_client":"Permitir a este cliente",
"block_for_this_client_only":"Bloquear solo para este cliente",
"block_for_this_client_only":"Bloquear solo para este cliente",
"unblock_for_this_client_only":"Desbloquear 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",
"time_table_header":"Hora",
"date":"Fecha",
"date":"Fecha",
"domain_name_table_header":"Nombre del dominio",
"domain_name_table_header":"Nombre del dominio",
@@ -425,9 +423,6 @@
"encryption_hostnames":"Nombres de hosts",
"encryption_hostnames":"Nombres de hosts",
"encryption_reset":"¿Estás seguro de que deseas restablecer la configuración de cifrado?",
"encryption_reset":"¿Estás seguro de que deseas restablecer la configuración de cifrado?",
"encryption_warning":"Advertencia",
"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_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>.",
"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",
"form_error_port_range":"Ingresa el número del puerto en el rango de 80 a 65535",
@@ -467,7 +462,6 @@
"form_add_id":"Añadir identificador",
"form_add_id":"Añadir identificador",
"form_client_name":"Ingresa el nombre del cliente",
"form_client_name":"Ingresa el nombre del cliente",
"encryption_reset":"Haluatko varmasti palauttaa salausasetukset?",
"encryption_reset":"Haluatko varmasti palauttaa salausasetukset?",
"encryption_warning":"Varoitus",
"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_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>.",
"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_desc":"Tässä voidaan määrittää AdGuard Homen DNS-palvelimen käyttöoikeussääntöjä.",
"access_allowed_title":"Sallitut päätelaitteet",
"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_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_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 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^\".",
"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^\".",
"updated_upstream_dns_toast":"Serveurs en amont enregistrés",
"updated_upstream_dns_toast":"Serveurs en amont enregistrés",
"dns_test_ok_toast":"Les serveurs DNS spécifiés fonctionnent correctement",
"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_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",
"dns_test_warning_toast":"L'amont « {{key}} » ne répond pas aux demandes de test et peut ne pas fonctionner correctement",
"unblock":"Débloquer",
"unblock":"Débloquer",
"block":"Bloquer",
"block":"Bloquer",
@@ -244,7 +243,6 @@
"allow_this_client":"Autoriser ce client",
"allow_this_client":"Autoriser ce client",
"block_for_this_client_only":"Bloquer uniquement pour ce client",
"block_for_this_client_only":"Bloquer uniquement pour ce client",
"unblock_for_this_client_only":"Dé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",
"time_table_header":"Temps",
"date":"Date",
"date":"Date",
"domain_name_table_header":"Nom de domaine",
"domain_name_table_header":"Nom de domaine",
@@ -312,15 +310,6 @@
"edns_use_custom_ip":"Utiliser une IP personnalisée pour EDNS",
"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",
"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_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",
"rate_limit_whitelist_placeholder":"Saisissez une adresse IP par ligne",
"blocking_ipv4_desc":"Adresse IP à renvoyer pour une demande A bloquée",
"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_ipv6_desc":"Adresse IP à renvoyer pour une demande AAAA bloquée",
@@ -425,9 +414,6 @@
"encryption_hostnames":"Noms d'hôte",
"encryption_hostnames":"Noms d'hôte",
"encryption_reset":"Voulez-vous vraiment réinitialiser les paramètres de chiffrement ?",
"encryption_reset":"Voulez-vous vraiment réinitialiser les paramètres de chiffrement ?",
"encryption_warning":"Attention",
"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_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>.",
"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",
"form_error_port_range":"Saisissez une valeur de port entre 80 et 65535",
@@ -467,7 +453,6 @@
"form_add_id":"Ajouter identifiant",
"form_add_id":"Ajouter identifiant",
"form_client_name":"Saisissez le nom du client",
"form_client_name":"Saisissez le nom du client",
"name":"Nom",
"name":"Nom",
"client_name":"Client {{id}}",
"client_global_settings":"Utiliser les paramètres généraux",
"client_global_settings":"Utiliser les paramètres généraux",
"client_deleted":"Le client « {{key}} » a été supprimé",
"client_deleted":"Le client « {{key}} » a été supprimé",
"client_added":"Le client « {{key}} » a été ajouté",
"client_added":"Le client « {{key}} » a été ajouté",
@@ -678,7 +663,7 @@
"use_saved_key":"Utiliser la clef précédemment enregistrée",
"use_saved_key":"Utiliser la clef précédemment enregistrée",
"parental_control":"Contrôle parental",
"parental_control":"Contrôle parental",
"safe_browsing":"Navigation sécurisée",
"safe_browsing":"Navigation sécurisée",
"served_from_cache_label":"Servi depuis le cache",
"served_from_cache":"{{value}} <i>(depuis le cache)</i>",
"form_error_password_length":"Le mot de passe doit comporter entre {{min}} et {{max}} caractères",
"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>.",
"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 ?",
"confirm_dns_cache_clear":"Voulez-vous vraiment vider le cache DNS ?",
@@ -740,8 +725,5 @@
"wednesday_short":"Mer.",
"wednesday_short":"Mer.",
"thursday_short":"Jeu.",
"thursday_short":"Jeu.",
"friday_short":"Ven.",
"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",
"bootstrap_dns_desc":"Alamat IP server DNS yang digunakan untuk menyelesaikan alamat IP resolver DoH/DoT yang Anda tentukan sebagai upstream. Komentar tidak diizinkan.",
"bootstrap_dns_desc":"Alamat IP server DNS yang digunakan untuk menyelesaikan alamat IP resolver DoH/DoT yang Anda tentukan sebagai upstream. Komentar tidak diizinkan.",
"fallback_dns_title":"Server DNS cadangan",
"fallback_dns_title":"Server DNS cadangan",
"fallback_dns_desc":"Daftar server DNS cadangan yang digunakan ketika server hulu DNS tidak merespons. Sintaksnya sama dengan kolom hulu utama di atas.",
"fallback_dns_desc":"Daftar server DNS cadangan yang digunakan ketika server DNS hulu tidak merespons. Sintaksnya sama dengan bidang hulu utama di atas.",
"fallback_dns_placeholder":"Masukkan satu server DNS cadangan per baris",
"fallback_dns_placeholder":"Masukkan satu server DNS cadangan per baris",
"local_ptr_title":"Server pembalik DNS pribadi",
"local_ptr_title":"Server pembalik DNS pribadi",
"local_ptr_desc":"Server DNS yang digunakan AdGuard Home untuk kueri PTR lokal. Server ini digunakan untuk menyelesaikan nama host klien dengan alamat IP pribadi, misalnya \"192.168.12.34\", menggunakan DNS terbalik. Jika tidak disetel, AdGuard Home menggunakan alamat resolver DNS default OS Anda kecuali untuk alamat AdGuard Home itu sendiri.",
"local_ptr_desc":"Server DNS yang digunakan 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).",
"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_title":"Gunakan server pembalik DNS pribadi",
"use_private_ptr_resolvers_desc":"Lakukan pencarian DNS terbalik untuk alamat yang disajikan secara lokal menggunakan server hulu ini. Jika dinonaktifkan, Adguard Home merespons dengan NXDOMAIN untuk semua permintaan PTR tersebut kecuali untuk klien yang diketahui dari DHCP, /etc/hosts, dan seterusnya.",
"use_private_ptr_resolvers_desc":"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.",
"check_dhcp_servers":"Cek untuk server DHCP",
"check_dhcp_servers":"Cek untuk server DHCP",
"save_config":"Simpan pengaturan",
"save_config":"Simpan pengaturan",
"enabled_dhcp":"Server DHCP diaktifkan",
"enabled_dhcp":"Server DHCP diaktifkan",
@@ -68,7 +68,7 @@
"ip":"IP",
"ip":"IP",
"dhcp_table_hostname":"Nama host",
"dhcp_table_hostname":"Nama host",
"dhcp_table_expires":"Kadaluwarsa",
"dhcp_table_expires":"Kadaluwarsa",
"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_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_error":"AdGuard Home tidak dapat menentukan apakah ada server DHCP aktif lain pada 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_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.",
"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_to_safe_search":"Jumlah perminataan DNS ke mesin pencari yang dipaksa 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",
"average_processing_time":"Rata-rata waktu pemrosesan",
"average_upstream_response_time":"Rata-rata waktu respons hulu",
"average_upstream_response_time":"Waktu respons server upstream rata-rata",
"response_time":"Waktu respons",
"response_time":"Waktu respons",
"average_processing_time_hint":"Rata-rata waktu dalam milidetik untuk pemrosesan sebuah permintaan DNS",
"average_processing_time_hint":"Rata-rata waktu dalam milidetik untuk pemrosesan sebuah permintaan DNS",
"block_domain_use_filters_and_hosts":"Blokir domain menggunakan filter dan file hosts",
"block_domain_use_filters_and_hosts":"Blokir domain menggunakan filter dan file hosts",
"filters_block_toggle_hint":"Anda dapat menyiapkan aturan pemblokiran dalam pengaturan <a>Filter</a>.",
"filters_block_toggle_hint":"Anda dapat menyiapkan aturan pemblokiran di pengaturan <a>Penyaringan</a>.",
"use_adguard_browsing_sec":"Gunakan layanan web Keamanan Penjelajahan AdGuard",
"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_browsing_sec_hint":"AdGuard Home akan memeriksa apakah domain diblokir oleh layanan web keamanan penjelajahan. Ini akan menggunakan API pencarian yang ramah privasi untuk melakukan pemeriksaan: hanya awalan singkat dari hash nama domain SHA256 yang dikirim ke server.",
"use_adguard_parental":"Gunakan layanan web kontrol orang tua AdGuard",
"use_adguard_parental":"Gunakan layanan web kontrol orang tua AdGuard",
@@ -166,7 +166,7 @@
"encryption_settings":"Pengaturan enkripsi",
"encryption_settings":"Pengaturan enkripsi",
"dhcp_settings":"Pengaturan DHCP",
"dhcp_settings":"Pengaturan DHCP",
"upstream_dns":"Server DNS hulu",
"upstream_dns":"Server DNS hulu",
"upstream_dns_help":"Masukkan satu alamat server per baris. <a>Pelajari lebih lanjut</a> mengenai cara mengonfigurasi server DNS hulu.",
"upstream_dns_help":"Masukkan alamat server per baris. <a>Pelajari lebih</a> mengenai konfigurasi upstream server DNS.",
"upstream_dns_configured_in_file":"Diatur dalam {{path}}",
"upstream_dns_configured_in_file":"Diatur dalam {{path}}",
"test_upstream_btn":"Uji hulu",
"test_upstream_btn":"Uji hulu",
"upstreams":"Upstream",
"upstreams":"Upstream",
@@ -192,10 +192,10 @@
"delete_table_action":"Hapus",
"delete_table_action":"Hapus",
"elapsed":"Berlalu",
"elapsed":"Berlalu",
"filters_and_hosts_hint":"AdGuard Home memahami aturan dasar adblock dan sintak file hosts.",
"filters_and_hosts_hint":"AdGuard Home memahami aturan dasar adblock dan sintak file hosts.",
"no_blocklist_added":"Tidak ada daftar hitam yang ditambahkan",
"no_blocklist_added":"Tiada daftar hitam ditambahkan",
"no_whitelist_added":"Tidak ada daftar putih yang ditambahkan",
"no_whitelist_added":"Tiada daftar putih ditambahkan",
"add_blocklist":"Tambahkan daftar hitam",
"add_blocklist":"Tambah daftar hitam",
"add_allowlist":"Tambahkan daftar putih",
"add_allowlist":"Tambah daftar putih",
"cancel_btn":"Batal",
"cancel_btn":"Batal",
"enter_name_hint":"Masukkan nama",
"enter_name_hint":"Masukkan nama",
"enter_url_or_path_hint":"Masukan sebuah URL atau jalur absolut dari daftar",
"enter_url_or_path_hint":"Masukan sebuah URL atau jalur absolut dari daftar",
"example_upstream_tcp_port":"DNS biasa (melalui TCP, dengan port);",
"example_upstream_tcp_port":"DNS biasa (melalui TCP, dengan port);",
@@ -236,7 +236,6 @@
"updated_upstream_dns_toast":"Server upstream berhasil disimpan",
"updated_upstream_dns_toast":"Server upstream berhasil disimpan",
"dns_test_ok_toast":"Server DNS yang ditentukan bekerja dengan benar",
"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_not_ok_toast":"Server \"{{key}}\": tidak dapat digunakan, mohon cek bahwa Anda telah menulisnya dengan benar",
"dns_test_parsing_error_toast":"Bagian {{section}}: baris {{line}}: tidak dapat digunakan, mohon cek bahwa Anda telah menulisnya dengan benar",
"dns_test_warning_toast":"Upstream \"{{key}}\" tidak menanggapi permintaan pengujian dan mungkin tidak berfungsi dengan baik",
"dns_test_warning_toast":"Upstream \"{{key}}\" tidak menanggapi permintaan pengujian dan mungkin tidak berfungsi dengan baik",
"unblock":"Buka Blokir",
"unblock":"Buka Blokir",
"block":"Blok",
"block":"Blok",
@@ -244,7 +243,6 @@
"allow_this_client":"Ijinkan klien ini",
"allow_this_client":"Ijinkan klien ini",
"block_for_this_client_only":"Blok hanya untuk klien ini",
"block_for_this_client_only":"Blok hanya untuk klien ini",
"unblock_for_this_client_only":"Jangan diblok 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",
"time_table_header":"Waktu",
"date":"Tanggal",
"date":"Tanggal",
"domain_name_table_header":"Nama domain",
"domain_name_table_header":"Nama domain",
@@ -291,7 +289,7 @@
"custom_ip":"Custom IP",
"custom_ip":"Custom IP",
"blocking_ipv4":"Blokiran IPv4",
"blocking_ipv4":"Blokiran IPv4",
"blocking_ipv6":"Blokiran IPv6",
"blocking_ipv6":"Blokiran IPv6",
"blocked_response_ttl":"Respons TTL terblokir",
"blocked_response_ttl":"Respon TLL diblokir",
"blocked_response_ttl_desc":"Menentukan berapa detik klien harus menyimpan respons yang difilter dalam cache",
"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)",
"form_enter_blocked_response_ttl":"Masukkan TTL respons yang diblokir (detik)",
"dnscrypt":"DNSCrypt",
"dnscrypt":"DNSCrypt",
@@ -322,9 +320,9 @@
"rate_limit_whitelist":"Daftar pembatasan tarif yang diizinkan",
"rate_limit_whitelist":"Daftar pembatasan tarif yang diizinkan",
"rate_limit_whitelist_desc":"Alamat IP dikecualikan dari pembatasan tarif",
"rate_limit_whitelist_desc":"Alamat IP dikecualikan dari pembatasan tarif",
"rate_limit_whitelist_placeholder":"Masukkan satu alamat IP per baris",
"rate_limit_whitelist_placeholder":"Masukkan satu alamat IP per baris",
"blocking_ipv4_desc":"Alamat IP yang akan dikembalikan untuk permintaan A yang diblokir",
"blocking_ipv4_desc":"Alamat IP akan dikembalikan untuk permintaan A yang diblokir",
"blocking_ipv6_desc":"Alamat IP yang akan dikembalikan untuk permintaan AAAA yang diblokir",
"blocking_ipv6_desc":"Alamat IP akan dipulihkan 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_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/",
"blocking_mode_refused":"DITOLAK: Respon dengan kode DITOLAK",
"blocking_mode_refused":"DITOLAK: Respon dengan kode DITOLAK",
"blocking_mode_nxdomain":"NXDOMAIN: Respon pakai kode NXDOMAIN",
"blocking_mode_nxdomain":"NXDOMAIN: Respon pakai kode NXDOMAIN",
"blocking_mode_null_ip":"Null IP: Respon pakai alamat IP kosong (0.0.0.0 untuk A; :: untuk AAAA)",
"blocking_mode_null_ip":"Null IP: Respon pakai alamat IP kosong (0.0.0.0 untuk A; :: untuk AAAA)",
@@ -332,7 +330,7 @@
"theme_auto":"Auto",
"theme_auto":"Auto",
"theme_light":"Terang",
"theme_light":"Terang",
"theme_dark":"Gelap",
"theme_dark":"Gelap",
"upstream_dns_client_desc":"Jika Anda biarkan kolom ini kosong, AdGuard Home akan menggunakan server yang dikonfigurasi di<0>pengaturan DNS</0>.",
"upstream_dns_client_desc":"Jika Anda biarkan bidang ini kosong, AdGuard Home akan memakai server yang dikonfigurasi di<0>Pengaturan DNS</0>.",
"tracker_source":"Sumber pelacak",
"tracker_source":"Sumber pelacak",
"source_label":"Sumber",
"source_label":"Sumber",
"found_in_known_domain_db":"Ditemukan di database domain dikenal",
"found_in_known_domain_db":"Ditemukan di database domain dikenal",
@@ -342,7 +340,7 @@
"unknown_filter":"Penyaringan {{filterId}} tidak dikenal",
"unknown_filter":"Penyaringan {{filterId}} tidak dikenal",
"known_tracker":"Pelacak yang dikenal",
"known_tracker":"Pelacak yang dikenal",
"install_welcome_title":"Selamat datang di AdGuard Home!",
"install_welcome_title":"Selamat datang di AdGuard Home!",
"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_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_submit_desc":"Prosedur pengaturan telah selesai, dan anda siap untuk mulai menggunakan AdGuard Home.",
"install_submit_desc":"Prosedur pengaturan telah selesai, dan anda siap untuk mulai menggunakan AdGuard Home.",
"install_devices_router":"Router",
"install_devices_router":"Router",
"install_devices_router_desc":"Penyiapan ini secara otomatis mencakup semua perangkat yang terhubung ke router rumah Anda, tidak perlu mengkonfigurasi masing-masing perangkat secara manual.",
"install_devices_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_address":"Server DNS AdGuard Home akan menggunakan alamat berikut",
"install_devices_address":"Server DNS AdGuard Home akan menggunakan alamat berikut",
"install_devices_router_list_1":"Buka preferensi untuk router Anda. Biasanya, Anda dapat mengaksesnya dari browser Anda melalui URL, seperti http://192.168.0.1/ atau http://192.168.1.1/. Anda mungkin diminta untuk memasukkan kata sandi. Jika Anda tidak mengingatnya, Anda sering kali dapat mengatur ulang kata sandi dengan menekan tombol pada perute itu sendiri, tetapi perlu diketahui bahwa jika prosedur ini dipilih, Anda mungkin akan kehilangan seluruh konfigurasi perute. Jika router Anda memerlukan aplikasi untuk menyiapkannya, instal aplikasi tersebut di ponsel atau PC Anda dan gunakan untuk mengakses pengaturan router.",
"install_devices_router_list_1":"Buka preferensi untuk router Anda. Biasanya, Anda dapat mengaksesnya dari 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 kolom yang memungkinkan dua atau tiga set angka, masing-masing dipecah menjadi empat kelompok dengan satu hingga tiga digit.",
"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_3":"Masukkan alamat server AdGuard Home disana",
"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_router_list_4":"Anda tidak dapat menyetel server DNS kustom pada beberapa tipe router. Dalam hal ini mungkin membantu jika Anda mengatur AdGuard Home sebagai <0>server DHCP</0>. Jika tidak, Anda harus mencari petunjuk tentang cara mengkustomisasi server DNS untuk model router khusus Anda.",
"install_devices_windows_list_1":"Buka Panel Kontrol melalui menu Start atau pencarian Windows.",
"install_devices_windows_list_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_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_3":"Ketuk nama jaringan yang saat ini aktif.",
"install_devices_ios_list_4":"Di kolom DNS, masukkan alamat server AdGuard Home Anda.",
"install_devices_ios_list_4":"Di bidang DNS, masukkan alamat server AdGuard Home anda.",
"get_started":"Mari mulai",
"get_started":"Mari mulai",
"next":"Selanjutnya",
"next":"Selanjutnya",
"open_dashboard":"Buka Beranda",
"open_dashboard":"Buka Beranda",
@@ -425,9 +423,6 @@
"encryption_hostnames":"Nama host",
"encryption_hostnames":"Nama host",
"encryption_reset":"Anda yakin ingin mengatur ulang pengaturan enkripsi?",
"encryption_reset":"Anda yakin ingin mengatur ulang pengaturan enkripsi?",
"encryption_warning":"Peringatan",
"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_expiring_certificate":"Sertifikat SSL Anda hampir kedaluwarsa. Perbarui <0>Pengaturan enkripsi</0>.",
"topline_expired_certificate":"Sertifikat SSL Anda kedaluwarsa. Perbarui <0>Pengaturan enkripsi</0>.",
"topline_expired_certificate":"Sertifikat SSL Anda kedaluwarsa. Perbarui <0>Pengaturan enkripsi</0>.",
"form_error_port_range":"Masukkan nomor port di kisaran 80-65535",
"form_error_port_range":"Masukkan nomor port di kisaran 80-65535",
@@ -444,7 +439,7 @@
"fix":"Perbaiki",
"fix":"Perbaiki",
"dns_providers":"Berikut adalah <0>daftar penyedia DNS yang dikenal</0> untuk dipilih.",
"dns_providers":"Berikut adalah <0>daftar penyedia DNS yang dikenal</0> untuk dipilih.",
"update_now":"Perbarui sekarang",
"update_now":"Perbarui sekarang",
"update_failed":"Pembaruan otomatis gagal. Silakan <a>ikuti langkah-langkah berikut</a> untuk memperbarui secara manual.",
"update_failed":"Pembaruan otomatis gagal. Silahkan <a>ikuti petunjuk ini</a> untuk perbarui secara manual.",
"manual_update":"Silakan <a>mengikuti 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",
"processing_update":"Silahkan tunggu, AdGuard Home sedang diperbarui",
"clients_title":"Klien yang gigih",
"clients_title":"Klien yang gigih",
@@ -454,7 +449,7 @@
"table_client":"Klien",
"table_client":"Klien",
"table_name":"Nama",
"table_name":"Nama",
"save_btn":"Simpan",
"save_btn":"Simpan",
"client_add":"Tambahkan Klien",
"client_add":"Tambah Klien",
"client_new":"Klien Baru",
"client_new":"Klien Baru",
"client_edit":"Ubah Klien",
"client_edit":"Ubah Klien",
"client_identifier":"Identifikasi",
"client_identifier":"Identifikasi",
@@ -464,10 +459,9 @@
"form_enter_subnet_ip":"Masukkan alamat IP di subnet \"{{cidr}}\"",
"form_enter_subnet_ip":"Masukkan alamat IP di subnet \"{{cidr}}\"",
"client_deleted":"Klien \"{{key}}\" berhasil dihapus",
"client_deleted":"Klien \"{{key}}\" berhasil dihapus",
"client_added":"Klien \"{{key}}\" berhasil ditambahkan",
"client_added":"Klien \"{{key}}\" berhasil ditambahkan",
@@ -482,7 +476,7 @@
"access_allowed_title":"Klien yang diizinkan",
"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_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_title":"Klien yang tidak diizinkan",
"access_disallowed_desc":"Daftar CIDR, alamat IP, atau <a>ClientID</a>. Jika daftar ini memiliki entri, AdGuard Home akan membatalkan permintaan dari klien ini. Kolom ini diabaikan jika ada entri di daftar putih klien.",
"access_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_blocked_title":"Domain yang diblokir",
"access_blocked_title":"Domain yang diblokir",
"access_blocked_desc":"Jangan bingung dengan filter. AdGuard Home menghapus kueri DNS yang cocok dengan domain ini, dan kueri ini bahkan tidak muncul di log kueri. Anda dapat menentukan nama domain, karakter pengganti, atau aturan filter URL yang tepat, mis. \"example.org\", \"*.example.org\", atau \"||example.org^\" yang sesuai.",
"access_blocked_desc":"Jangan 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",
"access_settings_saved":"Pengaturan akses berhasil disimpan",
@@ -491,7 +485,7 @@
"check_updates_now":"Periksa pembaruan sekarang",
"check_updates_now":"Periksa pembaruan sekarang",
"version_request_error":"Pemeriksaan pembaruan gagal. Harap periksa koneksi internet anda.",
"version_request_error":"Pemeriksaan pembaruan gagal. Harap periksa koneksi internet anda.",
"dns_privacy":"DNS Privasi",
"dns_privacy":"DNS Privasi",
"setup_dns_privacy_1":"<0>DNS melalui TLS:</0> Gunakan <1>{{address}}</1> string.",
"setup_dns_privacy_1":"<0>DNS-over-TLS:</0> Memakai <1>{{address}}</1> string.",
"setup_dns_privacy_2":"<0>DNS-over-TLS:</0> Memakai <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_3":"<0>Berikut daftar perangkat lunak yang dapat Anda gunakan.</0>",
"setup_dns_privacy_4":"Di perangkat iOS 14 atau macOS Big Sur, Anda dapat mengunduh file '.mobileconfig' khusus yang menambahkan server <highlight>DNS-over-HTTPS</highlight> atau <highlight>DNS-over-TLS</highlight> ke pengaturan DNS.",
"setup_dns_privacy_4":"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.",
@@ -511,7 +505,7 @@
"rewrite_added":"DNS rewrite untuk \"{{key}}\" berhasil ditambahkan",
"rewrite_added":"DNS rewrite untuk \"{{key}}\" berhasil ditambahkan",
"rewrite_deleted":"DNS rewrite untuk \"{{key}}\" berhasil dihapus",
"rewrite_deleted":"DNS rewrite untuk \"{{key}}\" berhasil dihapus",
"rewrite_updated":"Penulisan ulang DNS berhasil diperbarui",
"rewrite_updated":"Penulisan ulang DNS berhasil diperbarui",
"rewrite_add":"Tambahkan penulisan ulang DNS",
"rewrite_add":"Tambah DNS rewrite",
"rewrite_edit":"Edit penulisan ulang DNS",
"rewrite_edit":"Edit penulisan ulang DNS",
"rewrite_not_found":"Tidak ada DNS rewrite ditemukan",
"rewrite_not_found":"Tidak ada DNS rewrite ditemukan",
"rewrite_confirm_delete":"Apakah anda yakin ingin menghapus DNS rewrite untuk \"{{key}}\"?",
"rewrite_confirm_delete":"Apakah anda yakin ingin menghapus DNS rewrite untuk \"{{key}}\"?",
@@ -548,7 +542,7 @@
"domain":"Domain",
"domain":"Domain",
"ecs":"ECS",
"ecs":"ECS",
"punycode":"Kode kecil",
"punycode":"Kode kecil",
"answer":"Jawaban",
"answer":"Jawab",
"filter_added_successfully":"Filter telah berhasil ditambahkan",
"filter_added_successfully":"Filter telah berhasil ditambahkan",
"filter_removed_successfully":"Daftar ini telah sukses dihapus",
"filter_removed_successfully":"Daftar ini telah sukses dihapus",
"filter_updated":"Daftar telah sukses diperbarui",
"filter_updated":"Daftar telah sukses diperbarui",
@@ -600,10 +594,10 @@
"fastest_addr":"Alamat IP tercepat",
"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.",
"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_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 dengan /run/systemd/resolve/resolv.conf</0> <0>Hentikan DNSStubListener (muat ulang layanan sistemd-resolved)</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 pakai /run/systemd/resolve/resolv.conf</0> <0>Hentikan DNSStubListener (muat ulang layanan sistemd-resolve service)</0>",
"autofix_warning_result":"Hasilnya, semua permintaan DNS dari sistem anda akan diproses oleh AdGuardHome secara standar.",
"autofix_warning_result":"Hasilnya, semua permintaan DNS dari sistem anda akan diproses oleh AdGuardHome secara standar.",
"tags_title":"Tag",
"tags_title":"Tag",
"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>.",
"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>.",
"form_select_tags":"Pilih tag klien",
"form_select_tags":"Pilih tag klien",
"check_title":"Periksa penyaringan",
"check_title":"Periksa penyaringan",
"check_desc":"Periksa apakah nama host telah tersaring.",
"check_desc":"Periksa apakah nama host telah tersaring.",
@@ -611,7 +605,7 @@
"form_enter_host":"Masukkan nama host",
"form_enter_host":"Masukkan nama host",
"filtered_custom_rules":"Tersaring oleh aturan penyaring Buatan",
"filtered_custom_rules":"Tersaring oleh aturan penyaring Buatan",
"choose_from_list":"Pilih dari daftar",
"choose_from_list":"Pilih dari daftar",
"add_custom_list":"Tambahkan daftar kustom",
"add_custom_list":"Tambah daftar buatan",
"host_whitelisted":"Host didaftar putihkan",
"host_whitelisted":"Host didaftar putihkan",
"check_ip":"Alamat IP: {{ip}}",
"check_ip":"Alamat IP: {{ip}}",
"check_cname":"CNAME: {{cname}}",
"check_cname":"CNAME: {{cname}}",
@@ -621,8 +615,8 @@
"check_not_found":"Tidak di temukan di daftar penyaringan anda",
"check_not_found":"Tidak di temukan di daftar penyaringan anda",
"client_confirm_block":"Apa anda yakin ingin mem-blokir klien ini \"{{ip}}\"?",
"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_confirm_unblock":"Apa anda yakin ingin meng-unblock klien ini \"{{ip}}\"?",
"client_blocked":"Klien \"{{ip}}\" berhasil diblokir",
"client_blocked":"Klien \"{{ip}}\" sukses diblokir",
"client_unblocked":"Klien \"{{ip}}\" berhasil membuka blokir",
"client_unblocked":"Klien \"{{ip}}\" sukses di unblock",
"static_ip":"Alamat IP statis",
"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.",
"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",
"set_static_ip":"Atur alamat IP statik",
@@ -640,8 +634,8 @@
"show_whitelisted_responses":"Dalam Daftar Putih",
"show_whitelisted_responses":"Dalam Daftar Putih",
"show_processed_responses":"Terproses",
"show_processed_responses":"Terproses",
"blocked_safebrowsing":"Diblokir oleh Penjelajahan Aman",
"blocked_safebrowsing":"Diblokir oleh Penjelajahan Aman",
"blocked_adult_websites":"Diblokir oleh Kontrol Orang Tua",
"blocked_adult_websites":"Diblok oleh Kontrol Orang tua",
"blocked_threats":"Ancaman terblokir",
"blocked_threats":"Blokir Ancaman",
"allowed":"Dibolehkan",
"allowed":"Dibolehkan",
"filtered":"Tersaring",
"filtered":"Tersaring",
"rewritten":"Tulis ulang",
"rewritten":"Tulis ulang",
@@ -655,7 +649,7 @@
"enter_cache_size":"Masukkan ukuran cache (bytes)",
"enter_cache_size":"Masukkan ukuran cache (bytes)",
"updated_upstream_dns_toast":"I server upstream sono stati salvati correttamente",
"updated_upstream_dns_toast":"I server upstream sono stati salvati correttamente",
"dns_test_ok_toast":"I server DNS specificati funzionano 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_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",
"dns_test_warning_toast":"Upstream \"{{key}}\" non risponde alle richieste di test e potrebbe non funzionare correttamente",
"unblock":"Sblocca",
"unblock":"Sblocca",
"block":"Blocca",
"block":"Blocca",
@@ -244,7 +243,6 @@
"allow_this_client":"Consenti questo client",
"allow_this_client":"Consenti questo client",
"block_for_this_client_only":"Blocca solo per questo client",
"block_for_this_client_only":"Blocca solo per questo client",
"unblock_for_this_client_only":"Sblocca 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",
"time_table_header":"Ora",
"date":"Data",
"date":"Data",
"domain_name_table_header":"Nome dominio",
"domain_name_table_header":"Nome dominio",
@@ -312,15 +310,6 @@
"edns_use_custom_ip":"Usa IP personalizzato per EDNS",
"edns_use_custom_ip":"Usa IP personalizzato per EDNS",
"edns_use_custom_ip_desc":"Consentire l'uso di un 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_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",
"rate_limit_whitelist_placeholder":"Inserisci un indirizzo IP per riga",
"blocking_ipv4_desc":"Indirizzo IP per una richiesta DNS IPv4 bloccata",
"blocking_ipv4_desc":"Indirizzo IP per una richiesta DNS IPv4 bloccata",
"blocking_ipv6_desc":"Indirizzo IP restituito per una richiesta DNS IPv6 bloccata",
"blocking_ipv6_desc":"Indirizzo IP restituito per una richiesta DNS IPv6 bloccata",
@@ -425,9 +414,6 @@
"encryption_hostnames":"Nomi host",
"encryption_hostnames":"Nomi host",
"encryption_reset":"Sei sicuro di voler ripristinare le impostazioni di crittografia?",
"encryption_reset":"Sei sicuro di voler ripristinare le impostazioni di crittografia?",
"encryption_warning":"Attenzione",
"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_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>.",
"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",
"form_error_port_range":"Immettere il valore della porta nell'intervallo 80-65535",
@@ -467,7 +453,6 @@
"form_add_id":"Aggiungi identificatore",
"form_add_id":"Aggiungi identificatore",
"form_client_name":"Inserisci nome client",
"form_client_name":"Inserisci nome client",
"name":"Nome",
"name":"Nome",
"client_name":"Client {{id}}",
"client_global_settings":"Utilizza le impostazioni globali",
"client_global_settings":"Utilizza le impostazioni globali",
"block_for_this_client_only":"Alleen voor deze cliënt blokkeren",
"block_for_this_client_only":"Alleen voor deze cliënt blokkeren",
"unblock_for_this_client_only":"Alleen voor deze cliënt deblokkeren",
"unblock_for_this_client_only":"Alleen voor deze cliënt deblokkeren",
"add_persistent_client":"Toevoegen als permanente client",
"time_table_header":"Tijd",
"time_table_header":"Tijd",
"date":"Datum",
"date":"Datum",
"domain_name_table_header":"Domein naam",
"domain_name_table_header":"Domein naam",
@@ -425,9 +423,6 @@
"encryption_hostnames":"Hostnamen",
"encryption_hostnames":"Hostnamen",
"encryption_reset":"Ben je zeker dat je de encryptie instellingen wil resetten?",
"encryption_reset":"Ben je zeker dat je de encryptie instellingen wil resetten?",
"encryption_warning":"Waarschuwing",
"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_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.",
"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",
"form_error_port_range":"Poortnummer invoeren tussen 80 en 65535",
"updated_upstream_dns_toast":"Serwery nadrzędne zostały pomyślnie zapisane",
"updated_upstream_dns_toast":"Serwery nadrzędne zostały pomyślnie zapisane",
"dns_test_ok_toast":"Określone serwery DNS działają poprawnie",
"dns_test_ok_toast":"Określone serwery DNS działają poprawnie",
"dns_test_not_ok_toast":"Serwer \"{{key}}\": nie może być użyte, sprawdź, czy zapisano go poprawnie",
"dns_test_not_ok_toast":"Serwer \"{{key}}\": nie może być użyte, sprawdź, czy zapisano go poprawnie",
"dns_test_parsing_error_toast":"Sekcja {{section}}: linia {{line}}: nie może być użyte, sprawdź, czy zapisano go poprawnie",
"dns_test_warning_toast":"Upstream \"{{key}}\" nie odpowiada na zapytania testowe i może nie działać prawidłowo",
"dns_test_warning_toast":"Upstream \"{{key}}\" nie odpowiada na zapytania testowe i może nie działać prawidłowo",
"unblock":"Odblokuj",
"unblock":"Odblokuj",
"block":"Zablokuj",
"block":"Zablokuj",
@@ -244,7 +243,6 @@
"allow_this_client":"Pozwól temu klientowi",
"allow_this_client":"Pozwól temu klientowi",
"block_for_this_client_only":"Zablokuj tylko tego klienta",
"block_for_this_client_only":"Zablokuj tylko tego klienta",
"unblock_for_this_client_only":"Odblokuj tylko tego klienta",
"unblock_for_this_client_only":"Odblokuj tylko tego klienta",
"add_persistent_client":"Dodaj do zapisanych klientów",
"time_table_header":"Czas",
"time_table_header":"Czas",
"date":"Data",
"date":"Data",
"domain_name_table_header":"Nazwa domeny",
"domain_name_table_header":"Nazwa domeny",
@@ -425,9 +423,6 @@
"encryption_hostnames":"Nazwy hostów",
"encryption_hostnames":"Nazwy hostów",
"encryption_reset":"Czy na pewno chcesz zresetować ustawienia szyfrowania?",
"encryption_reset":"Czy na pewno chcesz zresetować ustawienia szyfrowania?",
"encryption_warning":"Ostrzeżenie",
"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>.",
"topline_expiring_certificate":"Twój certyfikat SSL wkrótce wygaśnie. Zaktualizuj <0>Ustawienia szyfrowania</0>.",
"updated_upstream_dns_toast":"Servidores DNS primário salvos com sucesso",
"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_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_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",
"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",
"unblock":"Desbloquear",
"block":"Bloquear",
"block":"Bloquear",
@@ -244,7 +243,6 @@
"allow_this_client":"Permitir este cliente",
"allow_this_client":"Permitir este cliente",
"block_for_this_client_only":"Bloquear apenas para este cliente",
"block_for_this_client_only":"Bloquear apenas para este cliente",
"unblock_for_this_client_only":"Desbloquear 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",
"time_table_header":"Data",
"date":"Data",
"date":"Data",
"domain_name_table_header":"Nome de domínio",
"domain_name_table_header":"Nome de domínio",
@@ -425,9 +423,6 @@
"encryption_hostnames":"Nomes dos servidores",
"encryption_hostnames":"Nomes dos servidores",
"encryption_reset":"Você tem certeza de que deseja redefinir a configuração de criptografia?",
"encryption_reset":"Você tem certeza de que deseja redefinir a configuração de criptografia?",
"encryption_warning":"Aviso",
"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_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>",
"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",
"form_error_port_range":"Digite um número de porta entre 80 e 65535",
"updated_upstream_dns_toast":"Servidores DNS primário guardados com sucesso",
"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_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_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",
"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",
"unblock":"Desbloquear",
"block":"Bloquear",
"block":"Bloquear",
@@ -244,7 +243,6 @@
"allow_this_client":"Permitir este cliente",
"allow_this_client":"Permitir este cliente",
"block_for_this_client_only":"Bloquear apenas para este cliente",
"block_for_this_client_only":"Bloquear apenas para este cliente",
"unblock_for_this_client_only":"Desbloquear 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",
"time_table_header":"Data",
"date":"Data",
"date":"Data",
"domain_name_table_header":"Nome do domínio",
"domain_name_table_header":"Nome do domínio",
@@ -425,9 +423,6 @@
"encryption_hostnames":"Nomes dos servidores",
"encryption_hostnames":"Nomes dos servidores",
"encryption_reset":"Tem a certeza de que deseja repor a definição de criptografia?",
"encryption_reset":"Tem a certeza de que deseja repor a definição de criptografia?",
"encryption_warning":"Cuidado",
"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_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>.",
"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",
"form_error_port_range":"Digite um numero de porta entre 80 e 65535",
"encryption_plain_dns_desc":"Незашифрованный DNS включён по умолчанию. Вы можете отключить его, чтобы заставить все устройства использовать зашифрованный DNS. Для этого необходимо включить хотя бы один зашифрованный протокол DNS",
"encryption_plain_dns_error":"Чтобы отключить незашифрованный DNS, включите хотя бы один зашифрованный протокол DNS",
"topline_expiring_certificate":"Ваш SSL-сертификат скоро истекает. Обновите <0>Настройки шифрования</0>.",
"topline_expiring_certificate":"Ваш SSL-сертификат скоро истекает. Обновите <0>Настройки шифрования</0>.",
"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>.",
"topline_expiring_certificate":"Váš SSL certifikát čoskoro vyprší. Aktualizujte <0>Nastavenia šifrovania</0>.",
"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_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>.",
"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",
"form_error_port_range":"Vnesite številko vrat v razponu med 80-65535",
"updated_upstream_dns_toast":"Üst sunucular başarıyla kaydedildi",
"updated_upstream_dns_toast":"Üst sunucular başarıyla kaydedildi",
"dns_test_ok_toast":"Belirtilen DNS sunucuları düzgün çalışıyor",
"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_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",
"dns_test_warning_toast":"Üst kaynak \"{{key}}\", test isteklerine yanıt vermiyor ve düzgün çalışmayabilir",
"unblock":"Engeli kaldır",
"unblock":"Engeli kaldır",
"block":"Engelle",
"block":"Engelle",
@@ -244,7 +243,6 @@
"allow_this_client":"Bu istemciye izin ver",
"allow_this_client":"Bu istemciye izin ver",
"block_for_this_client_only":"Yalnızca bu istemci için engelle",
"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",
"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",
"time_table_header":"Saat",
"date":"Tarih",
"date":"Tarih",
"domain_name_table_header":"Alan adı",
"domain_name_table_header":"Alan adı",
@@ -324,7 +322,7 @@
"rate_limit_whitelist_placeholder":"Her satıra bir IP adresi girin",
"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_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_ipv6_desc":"Engellenen bir AAAA isteği için geri döndürülecek IP adresi",
"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",
"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",
"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_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.",
"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",
"form_error_port_range":"80-65535 aralığında geçerli bir bağlantı noktası değeri girin",
@@ -467,7 +462,6 @@
"form_add_id":"Tanımlayıcı ekle",
"form_add_id":"Tanımlayıcı ekle",
"form_client_name":"İstemci ismi girin",
"form_client_name":"İstemci ismi girin",
"name":"Adı",
"name":"Adı",
"client_name":"İstemci {{id}}",
"client_global_settings":"Genel ayarları kullan",
"client_global_settings":"Genel ayarları kullan",
"client_deleted":"\"{{key}}\" istemcisi başarıyla silindi",
"client_deleted":"\"{{key}}\" istemcisi başarıyla silindi",
"client_added":"\"{{key}}\" istemcisi başarıyla eklendi",
"client_added":"\"{{key}}\" istemcisi başarıyla eklendi",
"encryption_plain_dns_desc":"Звичайний DNS усталено увімкнений. Ви можете вимкнути його, щоб змусити всі пристрої використовувати зашифрований DNS. Для цього необхідно увімкнути хоча б один зашифрований протокол DNS",
"encryption_plain_dns_error":"Щоб вимкнути звичайний DNS, увімкніть принаймні один зашифрований протокол DNS",
"topline_expiring_certificate":"Ваш сертифікат SSL скоро закінчиться. Оновіть <0>Налаштування шифрування</0>.",
"topline_expiring_certificate":"Ваш сертифікат SSL скоро закінчиться. Оновіть <0>Налаштування шифрування</0>.",
"topline_expired_certificate":"Термін дії вашого сертифіката SSL закінчився. Оновіть <0>Налаштування шифрування</0>.",
"topline_expired_certificate":"Термін дії вашого сертифіката SSL закінчився. Оновіть <0>Налаштування шифрування</0>.",
"form_error_port_range":"Введіть значення порту в діапазоні 80−65535",
"form_error_port_range":"Введіть значення порту в діапазоні 80−65535",
@@ -467,7 +462,6 @@
"form_add_id":"Додати ідентифікатор",
"form_add_id":"Додати ідентифікатор",
"form_client_name":"Введіть ім'я клієнта",
"form_client_name":"Введіть ім'я клієнта",
"name":"Ім'я",
"name":"Ім'я",
"client_name":"Клієнт {{id}}",
"client_global_settings":"Використати загальні налаштування",
"client_global_settings":"Використати загальні налаштування",
"client_deleted":"Клієнта «{{key}}» успішно видалено",
"client_deleted":"Клієнта «{{key}}» успішно видалено",
"client_added":"Клієнта «{{key}}» успішно додано",
"client_added":"Клієнта «{{key}}» успішно додано",
@@ -678,7 +672,7 @@
"use_saved_key":"Використати раніше збережений ключ",
"use_saved_key":"Використати раніше збережений ключ",
"parental_control":"Батьківський контроль",
"parental_control":"Батьківський контроль",
"safe_browsing":"Безпечний перегляд",
"safe_browsing":"Безпечний перегляд",
"served_from_cache_label":"Отримано з кешу",
"served_from_cache":"{{value}} <i>(отримано з кешу)</i>",
"form_error_password_length":"Пароль має містити від {{min}} до {{max}} символів",
"form_error_password_length":"Пароль має містити від {{min}} до {{max}} символів",
"anonymizer_notification":"<0>Примітка:</0> IP-анонімізацію ввімкнено. Ви можете вимкнути його в <1>Загальні налаштування</1> .",
"anonymizer_notification":"<0>Примітка:</0> IP-анонімізацію ввімкнено. Ви можете вимкнути його в <1>Загальні налаштування</1> .",
"confirm_dns_cache_clear":"Ви впевнені, що бажаєте очистити кеш DNS?",
"confirm_dns_cache_clear":"Ви впевнені, що бажаєте очистити кеш DNS?",
"load_balancing_desc":"一次只查詢一個伺服器。AdGuard Home 會使用加權隨機取樣來選擇使用的查詢結果,以確保速度最快的伺服器能被充分運用。",
"load_balancing_desc":"一次只查詢一個伺服器。AdGuard Home 會使用加權隨機取樣來選擇使用的查詢結果,以確保速度最快的伺服器能被充分運用。",
"bootstrap_dns":"引導(Boostrap) DNS 伺服器",
"bootstrap_dns":"引導(Boostrap) DNS 伺服器",
"bootstrap_dns_desc":"Bootstrap DNS 伺服器用於解析您所設定的上游 DoH/DoT 解析器的 IP 地址",
"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_title":"私人 DNS 伺服器",
"local_ptr_desc":"AdGuard Home 用於區域 PTR 查詢的 DNS 伺服器。這些伺服器將用於解析具有私人 IP 位址的用戶端的主機名稱,例如 \"192.168.12.34\",使用 rDNS。如果沒有設定,AdGuard Home 將自動使用您的系統預設 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}}",
"local_ptr_default_resolver":"AdGuard Home 預設使用以下作為 DNS 反解器:{{ip}}",
@@ -41,19 +37,17 @@
"dhcp_ipv6_settings":"DHCP IPv6 設定",
"dhcp_ipv6_settings":"DHCP IPv6 設定",
"form_error_required":"必要欄位",
"form_error_required":"必要欄位",
"form_error_ip4_format":"無效的 IPv4 格式",
"form_error_ip4_format":"無效的 IPv4 格式",
"form_error_ip4_gateway_format":"閘道的 IPv4 位址無效",
"form_error_ip6_format":"無效的 IPv6 格式",
"form_error_ip6_format":"無效的 IPv6 格式",
"form_error_ip_format":"無效的 IP 格式",
"form_error_ip4_gateway_format":"閘道的 IPv4 位址無效",
"form_error_ip_format":"無效的 IP 位址",
"form_error_mac_format":"無效的 「MAC 位址」格式",
"form_error_mac_format":"無效的 「MAC 位址」格式",
"form_error_client_id_format":"無效的「客戶端 ID」格式",
"form_error_client_id_format":"無效的「客戶端 ID」格式",
"form_error_server_name":"無效伺服器名稱",
"form_error_server_name":"無效伺服器名稱",
"form_error_subnet":"子網路 \"{{cidr}}\" 不包含 IP 位址 \"{{ip}}\"",
"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_dynamic_ip_found":"您的網路介面 <0>{{interfaceName}}</0> 正在使用動態 IP,要使用 DHCP 伺服器必須指定靜態 IP 給 AdGuard。\n目前您的 IP 位址 <0>{{ipAddress}}</0>,啟用 DHCP 後此 IP 將自動設定為靜態 IP 位址。",
"dhcp_lease_added":"靜態租用 \"{{key}}\" 已新增成功",
"dhcp_lease_added":"靜態租用 \"{{key}}\" 已新增成功",
"dhcp_lease_deleted":"靜態租用 \"{{key}}\" 已刪除成功",
"dhcp_lease_deleted":"靜態租用 \"{{key}}\" 已刪除成功",
"dhcp_lease_updated":"靜態租約 \"{{key}}\" 已成功更新",
"dhcp_new_static_lease":"新增靜態租用",
"dhcp_new_static_lease":"新增靜態租用",
"dhcp_edit_static_lease":"編輯靜態租約",
"dhcp_static_leases_not_found":"找不到 DHCP 靜態租用",
"dhcp_static_leases_not_found":"找不到 DHCP 靜態租用",
"dhcp_add_static_lease":"新增靜態租用",
"dhcp_add_static_lease":"新增靜態租用",
"dhcp_reset_leases":"重置所有 DHCP 租約",
"dhcp_reset_leases":"重置所有 DHCP 租約",
@@ -120,8 +112,7 @@
"stats_malware_phishing":"已封鎖惡意軟體/網路釣魚",
"stats_malware_phishing":"已封鎖惡意軟體/網路釣魚",
"stats_adult":"已封鎖成人網站",
"stats_adult":"已封鎖成人網站",
"stats_query_domain":"熱門查詢網域排行",
"stats_query_domain":"熱門查詢網域排行",
"for_last_hours":"在過去 {{count}} 小時",
"for_last_24_hours":"過去 24 小時",
"for_last_hours_plural":"在過去 {{count}} 小時裡",
"for_last_days":"最近 {{count}} 天內",
"for_last_days":"最近 {{count}} 天內",
"for_last_days_plural":"最近 {{count}} 天內",
"for_last_days_plural":"最近 {{count}} 天內",
"stats_disabled":"已禁用統計資料。您可以從<0>設定頁面</0>打開它。",
"stats_disabled":"已禁用統計資料。您可以從<0>設定頁面</0>打開它。",
@@ -132,20 +123,15 @@
"top_clients":"熱門用戶端排行",
"top_clients":"熱門用戶端排行",
"no_clients_found":"找不到用戶端",
"no_clients_found":"找不到用戶端",
"general_statistics":"一般統計資料",
"general_statistics":"一般統計資料",
"top_upstreams":"熱門上游伺服器",
"no_upstreams_data_found":"找不到上游數據",
"number_of_dns_query_days":"過去 {{count}} 天內 DNS 查詢總數",
"number_of_dns_query_days":"過去 {{count}} 天內 DNS 查詢總數",
"number_of_dns_query_days_plural":"過去 {{count}} 天內 DNS 查詢總數",
"number_of_dns_query_days_plural":"過去 {{count}} 天內 DNS 查詢總數",
"number_of_dns_query_hours":"過去 {{count}} 小時處理的 DNS 查詢數量",
"number_of_dns_query_24_hours":"過去 24小時內 DNS 查詢總數",
"number_of_dns_query_hours_plural":"過去 {{count}} 小時處理的 DNS 查詢數量",
"number_of_dns_query_blocked_24_hours":"已被廣告過濾器與主機黑名單封鎖 DNS 查詢總數",
"number_of_dns_query_blocked_24_hours":"已被廣告過濾器與主機黑名單封鎖 DNS 查詢總數",
"number_of_dns_query_blocked_24_hours_by_sec":"已被 AdGuard 瀏覽安全模組封鎖的 DNS 查詢總數",
"number_of_dns_query_blocked_24_hours_by_sec":"已被 AdGuard 瀏覽安全模組封鎖的 DNS 查詢總數",
// TODO(a.garipov): Use a better way if golang/go#44279 is ever resolved.
sysDir,err:=windows.GetSystemDirectory()
iferr!=nil{
log.Error("aghos: getting root filesystem: %s; using C:",err)
// Assume that C: is the safe default.
returnos.DirFS("C:")
}
returnos.DirFS(filepath.VolumeName(sysDir))
}
funcsetRlimit(valuint64)(errerror){
funcsetRlimit(valuint64)(errerror){
returnUnsupported("setrlimit")
returnUnsupported("setrlimit")
}
}
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.