[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Populating IPv6 DNS addresses in resolv.conf





On Mon, Oct 30, 2023 at 11:09 AM Max Nikulin <manikulin@gmail.com> wrote:
On 30/10/2023 20:04, Timothy M Butterworth wrote:
> sudo less /etc/resolv.conf
> domain home.arpa
> search home.arpa
> nameserver 8.8.8.8
> nameserver 8.8.4.4

I do not see "# Generated by NetworkManager" here.

     nmcli connection
NAME                UUID                                  TYPE      DEVICE  
Pixel5              e70d426b-3a26-4b29-bf59-edb3dcdfdbc3  wifi      wlo1
 
     nmcli device
DEVICE  TYPE      STATE                   CONNECTION  
wlo1    wifi      connected               Pixel5     

 
     NetworkManager --print-config
sudo NetworkManager --print-config
# NetworkManager configuration: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)

[main]
# rc-manager=
# auth-polkit=true
# dhcp=internal # Am I correct in thinking that this setting enables the internal DHCP client.
# iwd-config-path=
plugins=ifupdown,keyfile
configure-and-quit=no

[global-dns]
searches=home.arpa

[ifupdown]
managed=false

[logging]
# backend=journal
# audit=true

[device]
# wifi.backend=wpa_supplicant

[device-31-mac-addr-change]
match-device=driver:eagle_sdio,driver:wl
wifi.scan-rand-mac-address=no

# no-auto-default file "/var/lib/NetworkManager/no-auto-default.state"
 
     ls -l /etc/resolv.conf
     lsattr /etc/resolv.conf

I just changed this back to using chattr +i with the IPv6 addresses added.

 
As to /etc/dhcp/dhclient.conf and /etc/network/interfaces, I may be
wrong, but perhaps independent instances for IPv4 and IPv6 may be
running (if actual connection is managed through ifupdown)



--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Reply to: