Would unbound be affected when resolv.conf has Google DNS servers init?

Help
1

Expected Behaviour:

_resolv.conf should not have any commercial DNS servers init by default and unbound would only use my IP address.

Actual Behaviour:

This is my /etc/resolv.conf. The first two lines are Google DNS servers by default, I did not put them in.

# Generated by dhcpcd from wlan0.dhcp, wlan0.dhcp6, wlan0.ra
# /etc/resolv.conf.head can replace this line
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 2001:xxx:feed::1
nameserver 2001:xxx:feed::2
nameserver 2601:xxx:2080:xxxx:xxxx::
# /etc/resolv.conf.tail can replace this line

I did a standard test on dnsleaktest.com and only found my IP address but I am worried because unbound has used Google DNS servers in the past without my permission.

Debug Token:

https://tricorder.pi-hole.net/27yiWdlb/

2

You are likely affected by an issue introduced with the recent Bullseye Raspberry Pi OS.

There are several possible solution approaches, e.g. DNS leak test shows Google IP addresses when using unbound - #4 by jfb

We are currently working to update our unbound guide accordingly.

3

I already removed openresolv but /etc/resolv.conf still contains Google DNS servers. Should I change the file or remove it altogether?

4

You can change the file, but the change will not be permanent. After you removed openresolv, nameserver assignments are being handled by dhcpcd. This is populated from file /etc/dhcpcd.conf, and that is where the changes should be made.

5

So this is like disabling resolvconf for unbound in the guide right? I checked the unbound-resolvconf.service by running sudo systemctl status unbound-resolvconf.service and found that the service is inactive (dead)

Full log:

● unbound-resolvconf.service - Unbound DNS server via resolvconf
     Loaded: loaded (/lib/systemd/system/unbound-resolvconf.service; enabled; v>
     Active: inactive (dead)
  Condition: start condition failed at Sat 2021-11-20 15:46:19 PST; 20h ago
             └─ ConditionFileIsExecutable=/sbin/resolvconf was not met

Am I good for now or do I have to do some extra steps to disabling it completely and configure /etc/dhcpcd.conf with a static domain_name_servers= line like the guide said?

6

I also found Google DNS servers: 8.8.8.8 and 8.8.4.4 at static domain_name_servers in my /etc/dhcpcd.conf file. Would they affect my unbound or not?

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
#duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu

# Most distributions have NTP support.
#option ntp_servers

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate SLAAC address using the Hardware Address of the interface
#slaac hwaddr
# OR generate Stable Private IPv6 Addresses based from the DUID
slaac private

# Example static IP configuration:
#interface eth0
#static ip_address=192.168.0.10/24
#static ip6_address=fd51:42f8:caae:d92e::ff/64
#static routers=192.168.0.1
#static domain_name_servers=192.168.0.1 8.8.8.8 fd51:42f8:caae:d92e::1

# It is possible to fall back to a static IP if DHCP fails:
# define static profile
#profile static_eth0
#static ip_address=192.168.1.23/24
#static routers=192.168.1.1
#static domain_name_servers=192.168.1.1

# fallback to static profile on eth0
#interface eth0
#fallback static_eth0
interface wlan0
        static ip_address=192.168.0.151/24
        static routers=192.168.0.1
        static domain_name_servers=8.8.8.8 8.8.4.4
7

No. This is the file that populates /etc/resolv.conf for dhcpcd and is not related to unbound settings

8

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.