adguard only runs on ipv6 on proxmox

[hanscees]

Creating a bug report/issue

Required Information

• DietPi version | cat /boot/dietpi/.version 951

• Distro version | echo $G_DISTRO_NAME $G_RASPBIAN bookworm

• Kernel version | uname -a Linux DietPi 6.1.0-21-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03) x86_64 GNU/Linux

I downloaded proxmox dietpi bookworm and use it on proxmox running on debian.

Additional Information (if applicable)

• Software title | (EG: Nextcloud) Adguard

• Was the software title installed freshly or updated/migrated? freshly installed

• Can this issue be replicated on a fresh installation of DietPi? probably, mine was fresh

Steps to reproduce

1. install adguard from dietpi-software
2. apt install net-tools
3. netstat -tunlp

shows only tcp6 :53

I have corrected this by doing

vi /mnt/dietpi_userdata/adguardhome/AdGuardHome.yaml 

dns:
  bind_hosts:
    - 192.168.0.185

Not a big deal but I thought I should mention it.

now all is well

tcp        0      0 0.0.0.0:8200            0.0.0.0:*               LISTEN      332/minidlnad       
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      351/sshd: /usr/sbin 
tcp        0      0 192.168.0.185:53        0.0.0.0:*               LISTEN      327/AdGuardHome     
tcp6       0      0 :::22                   :::*                    LISTEN      351/sshd: /usr/sbin 
tcp6       0      0 :::5252                 :::*                    LISTEN      328/dietpi-dashboar 
tcp6       0      0 :::8083                 :::*                    LISTEN      327/AdGuardHome     
udp        0      0 192.168.0.185:60579     0.0.0.0:*                           332/minidlnad       
udp        0      0 239.255.255.250:1900    0.0.0.0:*                           332/minidlnad       
udp        0      0 192.168.0.185:53        0.0.0.0:*                           327/AdGuardHome     
udp        0      0 0.0.0.0:67              0.0.0.0:*                           354/dhcpd        

Expected behaviour

• adguard should listen on tcp4

Actual behaviour

• it only listens on tcp6 and cant resolve dns

Extra details

• it is possible that my test was wrong, since I changed two things at the time: the upstream dns was also wrong. If adguard should not listen on an tcp4 socket then my bug is probably void.