aboutsummaryrefslogtreecommitdiff
path: root/www/chromium/files/patch-net_dns_public_resolv__reader.cc
diff options
context:
space:
mode:
Diffstat (limited to 'www/chromium/files/patch-net_dns_public_resolv__reader.cc')
-rw-r--r--www/chromium/files/patch-net_dns_public_resolv__reader.cc11
1 files changed, 11 insertions, 0 deletions
diff --git a/www/chromium/files/patch-net_dns_public_resolv__reader.cc b/www/chromium/files/patch-net_dns_public_resolv__reader.cc
new file mode 100644
index 000000000000..95af21540dbb
--- /dev/null
+++ b/www/chromium/files/patch-net_dns_public_resolv__reader.cc
@@ -0,0 +1,11 @@
+--- net/dns/public/resolv_reader.cc.orig 2025-09-06 10:01:20 UTC
++++ net/dns/public/resolv_reader.cc
+@@ -34,7 +34,7 @@ std::unique_ptr<ScopedResState> ResolvReader::GetResSt
+ }
+
+ bool ResolvReader::IsLikelySystemdResolved() {
+-#if BUILDFLAG(IS_LINUX)
++#if BUILDFLAG(IS_LINUX) && !BUILDFLAG(IS_BSD)
+ // Look for a single 127.0.0.53:53 nameserver endpoint. The only known
+ // significant usage of such a configuration is the systemd-resolved local
+ // resolver, so it is then a fairly safe assumption that any DNS queries to