diff --git a/etc/systemd/resolved.conf.d/adguard-dot.conf b/etc/systemd/resolved.conf.d/adguard-dot.conf
index 919cd4a0..6ebf6496 100644
--- a/etc/systemd/resolved.conf.d/adguard-dot.conf
+++ b/etc/systemd/resolved.conf.d/adguard-dot.conf
@@ -2,7 +2,7 @@
 # work and captive portals attack? See README.md. Also requires not
 # panicking if tbe user needs something AdGuard is blocking.
 [Resolve]
-DNS=2a00:5a60::ad2:ff#dns.adguard.com 176.103.130.131#dns.adguard.com 2a00:5a60::ad1:ff#dns.adguard.com 176.103.130.130#dns.adguard.com
+DNS=2a10:50c0::ad1:ff#dns.adguard.com 94.140.14.14#dns.adguard.com 2a10:50c0::ad2:ff#dns.adguard.com 94.140.15.15#dns.adguard.com
 Domains=~.
 # non-tech friendliness in case system down for ages. Also DNSSEC ensures
 # the DNS server isn't lying which is a task of adblocking DNS server...
@@ -10,3 +10,5 @@ DNSSEC=allow-downgrade
 # There is no point of disabling this with adblocking DNS
 DNSOverTLS=true
 Cache=true
+
+# Updated for https://adguard.com/en/blog/adguard-dns-new-addresses.html
diff --git a/etc/unbound/unbound.conf.d/dot-adguard.conf b/etc/unbound/unbound.conf.d/dot-adguard.conf
index bc88b9a3..442868b0 100644
--- a/etc/unbound/unbound.conf.d/dot-adguard.conf
+++ b/etc/unbound/unbound.conf.d/dot-adguard.conf
@@ -7,7 +7,9 @@ server:
 forward-zone:
     name: "."
     forward-tls-upstream: yes
-    forward-addr: 2a00:5a60::ad2:ff@853#dns.adguard.com
-    forward-addr: 176.103.130.131@853#dns.adguard.com
-    forward-addr: 2a00:5a60::ad1:ff@853#dns.adguard.com
-    forward-addr: 176.103.130.130@853#dns.adguard.com
+    forward-addr: 2a10:50c0::ad1:ff@853#dns.adguard.com
+    forward-addr: 94.140.14.14@853#dns.adguard.com
+    forward-addr: 2a10:50c0::ad2:ff@853#dns.adguard.com
+    forward-addr: 94.140.15.15@853#dns.adguard.com
+
+# Updated for https://adguard.com/en/blog/adguard-dns-new-addresses.html