I have a router that has DHCP and assigns IP and DNS servers The DNS server assigned are 192.168.50.4 192.168.50.2 fe80::dea6:32ff:fe25:41d2 192.168.50.4 pi-hole 192.168.50.2 Bind DNS recursive fe80::dea6:32ff:fe25:41d2 pi-hole The pi-hole server uses 192.168.50.2 as its DNS name resolution resolvectl returns this Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=allow-downgrade/supported resolv.conf mode: stub Fallback DNS Servers: 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google 2606:4700:4700::1111#cloudflare-dns.com 2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google Link 2 (end0) Current Scopes: DNS Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=allow-downgrade/supported Current DNS Server: fe80::dea6:32ff:fe25:41d2 DNS Servers: 192.168.50.4 192.168.50.2 fe80::dea6:32ff:fe25:41d2 Default Route: yes Link 3 (wlan0) Current Scopes: none Protocols: -DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=allow-downgrade/supported Default Route: no The following for end0 wired connection Current DNS Server: fe80::dea6:32ff:fe25:41d2 changes or cycles through the three DNS servers, changing about every 5 minutes or upon browsing the web with firefox ( firefox is set to use my DNS servers) Is that how resolved really works? I was under the impression that once the "Current DNS Server" was set it would stay that way unless the "Current DNS Server" failed. I there a setting other than /etc/systemd/resolved.conf ? [Resolve] DNS=192.168.50.4 fe80::dea6:32ff:fe25:41d2 Domains=~. I would really like to have it assigned by the router instead of at each client. -- Hindi madali ang maging ako
On Wed, Jul 16, 2025 at 06:16:04PM -0400, Pocket wrote:
Link 2 (end0) Current Scopes: DNS Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=allow-downgrade/supported Current DNS Server: fe80::dea6:32ff:fe25:41d2 DNS Servers: 192.168.50.4 192.168.50.2 fe80::dea6:32ff:fe25:41d2 Default Route: yes
Current DNS Server: fe80::dea6:32ff:fe25:41d2 changes or cycles through the three DNS servers, changing about every 5 minutes or upon browsing the web with firefox ( firefox is set to use my DNS servers)
Is that how resolved really works?
Yes, resolved has the notion that every DNS server that's configured is the same for a certain interface. They expect them to be able to serve queries interchangeably. If you don't want a DNS server to be used, don't assign it to an interface.
On 7/17/25 1:37 AM, Reto wrote:
On Wed, Jul 16, 2025 at 06:16:04PM -0400, Pocket wrote:
Link 2 (end0) Current Scopes: DNS Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=allow-downgrade/supported Current DNS Server: fe80::dea6:32ff:fe25:41d2 DNS Servers: 192.168.50.4 192.168.50.2 fe80::dea6:32ff:fe25:41d2 Default Route: yes
Current DNS Server: fe80::dea6:32ff:fe25:41d2 changes or cycles through the three DNS servers, changing about every 5 minutes or upon browsing the web with firefox ( firefox is set to use my DNS servers)
Is that how resolved really works?
Yes, resolved has the notion that every DNS server that's configured is the same for a certain interface. They expect them to be able to serve queries interchangeably.
If you don't want a DNS server to be used, don't assign it to an interface.
I don't assign a DNS server, the assignment comes from the router via DHCP. The issue is that the pi-hole is being "bypassed" on some queries defeating the purpose of the pi-hole. It looks like I will have to assign the DNS server on each client (pc's) (192.168.50.4) and then set the DNS Fall back as 192.168.50.2. I would have liked to avoid that. BTW clients like ipads and phones work as I intended, the pi-hole is the primary DNS server and when it fails it reverts to the bind server (192.168.50.2). -- Hindi madali ang maging ako
participants (2)
-
Pocket
-
Reto