I have tried following various threads and help topics to try and get dns working on my DietPi.
PiHole and Unbound used to be install but have since been uninstalled.
I am setup using a static IP and tried setting DNS to gateway and/or google dns.
I can’t update or even ping google.com
root@BioDietPi:~# ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.1.0.252 netmask 255.255.255.0 broadcast 10.1.0.255
ether dc:a6:32:36:4b:ae txqueuelen 1000 (Ethernet)
RX packets 12037 bytes 2777023 (2.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 10595 bytes 2618337 (2.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1000 (Local Loopback)
RX packets 1240 bytes 100136 (97.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1240 bytes 100136 (97.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wg0: flags=209<UP,POINTOPOINT,RUNNING,NOARP> mtu 1420
inet 10.6.0.1 netmask 255.255.255.0 destination 10.6.0.1
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 5380 bytes 1185948 (1.1 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4929 bytes 1336316 (1.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@BioDietPi:~# cat /etc/nsswitch.conf
glibc-doc-reference' and info’ packages installed, try:passwd: files
group: files
shadow: files
gshadow: files
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
root@BioDietPi:~# hosts
-bash: hosts: command not found
root@BioDietPi:~# ping -nc 1 -W 5 dns9.quad9.net
ping: dns9.quad9.net: Name or service not known
root@BioDietPi:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=115 time=16.6 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=115 time=19.1 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=115 time=15.0 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=115 time=17.5 ms
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 14.970/17.053/19.121/1.496 ms
root@BioDietPi:~# hostname
BioDietPi
root@BioDietPi:~# hostname -i
127.0.0.1 127.0.1.1
root@BioDietPi:~# hostname -I
10.1.0.252 10.6.0.1
Can you share following
cat /etc/resolv.conf
root@BioDietPi:/etc/systemd# cat /etc/resolv.conf
domain bio***abs
search bio***abs
nameserver 8.8.8.8
Could you try following
dig google.com
root@BioDietPi:/etc/systemd# dig google.com
; <<>> DiG 9.16.15-Raspbian <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47715
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 145 IN A 142.250.68.174
;; Query time: 20 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Dec 13 10:47:42 CST 2021
;; MSG SIZE rcvd: 55
DNS resolution is working fine as you can see. Your system ask Google DNS and got correct answer.
Flowing is not working still?
ping google.com
root@BioDietPi:/etc/systemd# nslookup google.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: google.com
Address: 142.251.45.78
Name: google.com
Address: 2607:f8b0:4000:806::200e
root@BioDietPi:/etc/systemd# ping google.com
ping: google.com: Name or service not known
Hmm DNS resolution is not your issue. As well nslookup is resolving the domain correctly. Do you have tcpdump installed?
First, thanks so much for your help!
Second, I don’t think tcpdump is installed.
root@BioDietPi:/etc/dhcp# tcpdump
-bash: tcpdump: command not found
What kind of device you are running
Required Information
root@BioDietPi:/# cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=7
G_DIETPI_VERSION_SUB=7
G_DIETPI_VERSION_RC=3
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
G_LIVE_PATCH_STATUS[0]='applied'
root@BioDietPi:/# echo $G_DISTRO_NAME $G_RASPBIAN
bullseye 1
root@BioDietPi:/# uname -a
Linux BioDietPi 5.10.63-v7l+ #1459 SMP Wed Oct 6 16:41:57 BST 2021 armv7l GNU/Linux
root@BioDietPi:/# echo $G_HW_MODEL_NAME
RPi 4 Model B (armv7l)
It’s a remote machine, so rewriting the SD card is out of the option for a month or two. 
Any possibility to transfer files to that device?
Yes, I have ssh over VPN.
ok let’s be creative to get tcpdump installed.
cd /tmp/
wget http://134.76.12.6/pub/linux/debian/raspbian/raspbian/pool/main/libp/libpcap/libpcap0.8_1.10.0-2_armhf.deb
wget http://134.76.12.6/pub/linux/debian/raspbian/raspbian/pool/main/t/tcpdump/tcpdump_4.99.0-2_armhf.deb
dpkg -i tcpdump_4.99.0-2_armhf.deb libpcap0.8_1.10.0-2_armhf.deb
This will download and install tcpdump. I already tried to translate the package source DNS into IP address to avoid using DNS resolution. Once installed we could do some package tracing
On a first SSH session you could run the trace. It will automatically stop until 200 lines are captured or if cancelled
tcpdump -i any -c200 -nn port 53
on a 2nd SSH session you could try to ping Google, but I guess it is failing
ping google.com
To compare, just do a dig as well
dig google.com
root@BioDietPi:/tmp# tcpdump -i any -c200 -nn port 53
tcpdump: data link type LINUX_SLL2
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes
14:57:39.627519 lo In IP 127.0.0.1.47989 > 127.0.0.1.53: 43325+ A? google.com. (28)
14:57:39.627733 lo In IP 127.0.0.1.47989 > 127.0.0.1.53: 28636+ AAAA? google.com. (28)
14:57:39.628004 lo In IP 127.0.0.1.53185 > 127.0.0.1.53: 43325+ A? google.com. (28)
14:57:39.628135 lo In IP 127.0.0.1.53185 > 127.0.0.1.53: 28636+ AAAA? google.com. (28)
14:57:46.754363 eth0 Out IP 10.1.0.252.60972 > 10.1.0.1.53: 43969+ [1au] A? google.com. (51)
14:57:46.769218 eth0 In IP 10.1.0.1.53 > 10.1.0.252.60972: 43969 6/0/1 A 142.250.113.102, A 142.250.113.113, A 142.250.113.138, A 142.250.113.100, A 142.250.113.139, A 142.250.113.101 (135)
14:57:46.844309 lo In IP 127.0.0.1.43728 > 127.0.0.1.53: 28935+ A? 2.debian.pool.ntp.org. (39)
14:57:46.844383 lo In IP 127.0.0.1.43728 > 127.0.0.1.53: 61500+ AAAA? 2.debian.pool.ntp.org. (39)
14:57:46.844512 lo In IP 127.0.0.1.45542 > 127.0.0.1.53: 28935+ A? 2.debian.pool.ntp.org. (39)
14:57:46.844568 lo In IP 127.0.0.1.45542 > 127.0.0.1.53: 61500+ AAAA? 2.debian.pool.ntp.org. (39)
14:57:46.844982 lo In IP 127.0.0.1.44576 > 127.0.0.1.53: 53878+ A? 3.debian.pool.ntp.org. (39)
14:57:46.845039 lo In IP 127.0.0.1.44576 > 127.0.0.1.53: 9315+ AAAA? 3.debian.pool.ntp.org. (39)
14:57:46.845158 lo In IP 127.0.0.1.33979 > 127.0.0.1.53: 53878+ A? 3.debian.pool.ntp.org. (39)
14:57:46.845212 lo In IP 127.0.0.1.33979 > 127.0.0.1.53: 9315+ AAAA? 3.debian.pool.ntp.org. (39)
14:57:46.845608 lo In IP 127.0.0.1.33527 > 127.0.0.1.53: 62195+ A? 0.debian.pool.ntp.org. (39)
14:57:46.845664 lo In IP 127.0.0.1.33527 > 127.0.0.1.53: 8591+ AAAA? 0.debian.pool.ntp.org. (39)
14:57:46.845782 lo In IP 127.0.0.1.52251 > 127.0.0.1.53: 62195+ A? 0.debian.pool.ntp.org. (39)
14:57:46.845837 lo In IP 127.0.0.1.52251 > 127.0.0.1.53: 8591+ AAAA? 0.debian.pool.ntp.org. (39)
14:57:46.846233 lo In IP 127.0.0.1.35068 > 127.0.0.1.53: 56688+ A? 1.debian.pool.ntp.org. (39)
14:57:46.846292 lo In IP 127.0.0.1.35068 > 127.0.0.1.53: 34563+ AAAA? 1.debian.pool.ntp.org. (39)
14:57:46.846410 lo In IP 127.0.0.1.55616 > 127.0.0.1.53: 56688+ A? 1.debian.pool.ntp.org. (39)
14:57:46.846464 lo In IP 127.0.0.1.55616 > 127.0.0.1.53: 34563+ AAAA? 1.debian.pool.ntp.org. (39)
14:57:46.846855 lo In IP 127.0.0.1.36156 > 127.0.0.1.53: 24048+ A? 2.debian.pool.ntp.org. (39)
14:57:46.846914 lo In IP 127.0.0.1.36156 > 127.0.0.1.53: 9191+ AAAA? 2.debian.pool.ntp.org. (39)
14:57:46.847032 lo In IP 127.0.0.1.59479 > 127.0.0.1.53: 24048+ A? 2.debian.pool.ntp.org. (39)
14:57:46.847086 lo In IP 127.0.0.1.59479 > 127.0.0.1.53: 9191+ AAAA? 2.debian.pool.ntp.org. (39)
14:57:46.848093 lo In IP 127.0.0.1.39147 > 127.0.0.1.53: 45934+ A? 3.debian.pool.ntp.org. (39)
14:57:46.848160 lo In IP 127.0.0.1.39147 > 127.0.0.1.53: 43892+ AAAA? 3.debian.pool.ntp.org. (39)
14:57:46.848281 lo In IP 127.0.0.1.34917 > 127.0.0.1.53: 45934+ A? 3.debian.pool.ntp.org. (39)
14:57:46.848337 lo In IP 127.0.0.1.34917 > 127.0.0.1.53: 43892+ AAAA? 3.debian.pool.ntp.org. (39)
14:57:46.848760 lo In IP 127.0.0.1.49787 > 127.0.0.1.53: 35240+ A? 0.debian.pool.ntp.org. (39)
14:57:46.848819 lo In IP 127.0.0.1.49787 > 127.0.0.1.53: 25031+ AAAA? 0.debian.pool.ntp.org. (39)
14:57:46.848941 lo In IP 127.0.0.1.59404 > 127.0.0.1.53: 35240+ A? 0.debian.pool.ntp.org. (39)
14:57:46.848996 lo In IP 127.0.0.1.59404 > 127.0.0.1.53: 25031+ AAAA? 0.debian.pool.ntp.org. (39)
14:57:46.849401 lo In IP 127.0.0.1.39816 > 127.0.0.1.53: 56719+ A? 1.debian.pool.ntp.org. (39)
14:57:46.849459 lo In IP 127.0.0.1.39816 > 127.0.0.1.53: 64163+ AAAA? 1.debian.pool.ntp.org. (39)
14:57:46.849577 lo In IP 127.0.0.1.59509 > 127.0.0.1.53: 56719+ A? 1.debian.pool.ntp.org. (39)
14:57:46.849632 lo In IP 127.0.0.1.59509 > 127.0.0.1.53: 64163+ AAAA? 1.debian.pool.ntp.org. (39)
14:57:46.850036 lo In IP 127.0.0.1.57720 > 127.0.0.1.53: 64820+ A? 2.debian.pool.ntp.org. (39)
14:57:46.850094 lo In IP 127.0.0.1.57720 > 127.0.0.1.53: 20056+ AAAA? 2.debian.pool.ntp.org. (39)
14:57:46.850212 lo In IP 127.0.0.1.42110 > 127.0.0.1.53: 64820+ A? 2.debian.pool.ntp.org. (39)
14:57:46.850268 lo In IP 127.0.0.1.42110 > 127.0.0.1.53: 20056+ AAAA? 2.debian.pool.ntp.org. (39)
14:57:46.850696 lo In IP 127.0.0.1.40857 > 127.0.0.1.53: 30385+ A? 3.debian.pool.ntp.org. (39)
14:57:46.850756 lo In IP 127.0.0.1.40857 > 127.0.0.1.53: 27302+ AAAA? 3.debian.pool.ntp.org. (39)
14:57:46.850875 lo In IP 127.0.0.1.60624 > 127.0.0.1.53: 30385+ A? 3.debian.pool.ntp.org. (39)
14:57:46.850929 lo In IP 127.0.0.1.60624 > 127.0.0.1.53: 27302+ AAAA? 3.debian.pool.ntp.org. (39)
14:57:59.200834 eth0 In IP 10.1.0.12.36590 > 10.1.0.252.53: 54394+ Type65? eas.outlook.com. (33)
14:58:07.221602 lo In IP 127.0.0.1.48547 > 127.0.0.1.53: 49520+ A? google.com. (28)
14:58:07.221769 lo In IP 127.0.0.1.48547 > 127.0.0.1.53: 16790+ AAAA? google.com. (28)
14:58:07.222034 lo In IP 127.0.0.1.50989 > 127.0.0.1.53: 49520+ A? google.com. (28)
14:58:07.222172 lo In IP 127.0.0.1.50989 > 127.0.0.1.53: 16790+ AAAA? google.com. (28)
14:58:08.714548 eth0 Out IP 10.1.0.252.50497 > 10.1.0.1.53: 26479+ [1au] A? google.com. (51)
14:58:08.714831 eth0 In IP 10.1.0.1.53 > 10.1.0.252.50497: 26479 6/0/1 A 142.250.113.101, A 142.250.113.139, A 142.250.113.100, A 142.250.113.138, A 142.250.113.113, A 142.250.113.102 (135)
14:58:13.307681 eth0 In IP 10.1.0.11.20339 > 10.1.0.252.53: 34344+ Type65? captive.apple.com. (35)
14:58:17.095200 lo In IP 127.0.0.1.59641 > 127.0.0.1.53: 31018+ A? 0.debian.pool.ntp.org. (39)
14:58:17.095375 lo In IP 127.0.0.1.59641 > 127.0.0.1.53: 21217+ AAAA? 0.debian.pool.ntp.org. (39)
14:58:17.095701 lo In IP 127.0.0.1.55973 > 127.0.0.1.53: 31018+ A? 0.debian.pool.ntp.org. (39)
14:58:17.095848 lo In IP 127.0.0.1.55973 > 127.0.0.1.53: 21217+ AAAA? 0.debian.pool.ntp.org. (39)
14:58:17.096935 lo In IP 127.0.0.1.34592 > 127.0.0.1.53: 59899+ A? 1.debian.pool.ntp.org. (39)
14:58:17.097087 lo In IP 127.0.0.1.34592 > 127.0.0.1.53: 56960+ AAAA? 1.debian.pool.ntp.org. (39)
14:58:17.097410 lo In IP 127.0.0.1.43992 > 127.0.0.1.53: 59899+ A? 1.debian.pool.ntp.org. (39)
14:58:17.097555 lo In IP 127.0.0.1.43992 > 127.0.0.1.53: 56960+ AAAA? 1.debian.pool.ntp.org. (39)
14:58:17.101091 lo In IP 127.0.0.1.55422 > 127.0.0.1.53: 22839+ A? 2.debian.pool.ntp.org. (39)
14:58:17.101345 lo In IP 127.0.0.1.55422 > 127.0.0.1.53: 4422+ AAAA? 2.debian.pool.ntp.org. (39)
14:58:17.101622 lo In IP 127.0.0.1.49945 > 127.0.0.1.53: 22839+ A? 2.debian.pool.ntp.org. (39)
14:58:17.101746 lo In IP 127.0.0.1.49945 > 127.0.0.1.53: 4422+ AAAA? 2.debian.pool.ntp.org. (39)
14:58:17.102671 lo In IP 127.0.0.1.57194 > 127.0.0.1.53: 32592+ A? 3.debian.pool.ntp.org. (39)
14:58:17.102803 lo In IP 127.0.0.1.57194 > 127.0.0.1.53: 53024+ AAAA? 3.debian.pool.ntp.org. (39)
14:58:17.103069 lo In IP 127.0.0.1.40644 > 127.0.0.1.53: 32592+ A? 3.debian.pool.ntp.org. (39)
14:58:17.103198 lo In IP 127.0.0.1.40644 > 127.0.0.1.53: 53024+ AAAA? 3.debian.pool.ntp.org. (39)
14:58:17.104117 lo In IP 127.0.0.1.58597 > 127.0.0.1.53: 9028+ A? 0.debian.pool.ntp.org. (39)
14:58:17.104248 lo In IP 127.0.0.1.58597 > 127.0.0.1.53: 32568+ AAAA? 0.debian.pool.ntp.org. (39)
14:58:17.104517 lo In IP 127.0.0.1.41100 > 127.0.0.1.53: 9028+ A? 0.debian.pool.ntp.org. (39)
14:58:17.104639 lo In IP 127.0.0.1.41100 > 127.0.0.1.53: 32568+ AAAA? 0.debian.pool.ntp.org. (39)
14:58:17.105563 lo In IP 127.0.0.1.45613 > 127.0.0.1.53: 8058+ A? 1.debian.pool.ntp.org. (39)
14:58:17.105700 lo In IP 127.0.0.1.45613 > 127.0.0.1.53: 13095+ AAAA? 1.debian.pool.ntp.org. (39)
14:58:17.105968 lo In IP 127.0.0.1.57070 > 127.0.0.1.53: 8058+ A? 1.debian.pool.ntp.org. (39)
14:58:17.106091 lo In IP 127.0.0.1.57070 > 127.0.0.1.53: 13095+ AAAA? 1.debian.pool.ntp.org. (39)
14:58:17.106997 lo In IP 127.0.0.1.43934 > 127.0.0.1.53: 14200+ A? 2.debian.pool.ntp.org. (39)
14:58:17.107128 lo In IP 127.0.0.1.43934 > 127.0.0.1.53: 5460+ AAAA? 2.debian.pool.ntp.org. (39)
14:58:17.107401 lo In IP 127.0.0.1.47386 > 127.0.0.1.53: 14200+ A? 2.debian.pool.ntp.org. (39)
14:58:17.107530 lo In IP 127.0.0.1.47386 > 127.0.0.1.53: 5460+ AAAA? 2.debian.pool.ntp.org. (39)
14:58:17.108476 lo In IP 127.0.0.1.38003 > 127.0.0.1.53: 46825+ A? 3.debian.pool.ntp.org. (39)
14:58:17.108607 lo In IP 127.0.0.1.38003 > 127.0.0.1.53: 27615+ AAAA? 3.debian.pool.ntp.org. (39)
14:58:17.108873 lo In IP 127.0.0.1.55017 > 127.0.0.1.53: 46825+ A? 3.debian.pool.ntp.org. (39)
14:58:17.108998 lo In IP 127.0.0.1.55017 > 127.0.0.1.53: 27615+ AAAA? 3.debian.pool.ntp.org. (39)
14:58:17.109929 lo In IP 127.0.0.1.41146 > 127.0.0.1.53: 502+ A? 0.debian.pool.ntp.org. (39)
14:58:17.110067 lo In IP 127.0.0.1.41146 > 127.0.0.1.53: 23067+ AAAA? 0.debian.pool.ntp.org. (39)
14:58:17.110338 lo In IP 127.0.0.1.46985 > 127.0.0.1.53: 502+ A? 0.debian.pool.ntp.org. (39)
14:58:17.110460 lo In IP 127.0.0.1.46985 > 127.0.0.1.53: 23067+ AAAA? 0.debian.pool.ntp.org. (39)
14:58:17.111359 lo In IP 127.0.0.1.50881 > 127.0.0.1.53: 49969+ A? 1.debian.pool.ntp.org. (39)
14:58:17.111491 lo In IP 127.0.0.1.50881 > 127.0.0.1.53: 30988+ AAAA? 1.debian.pool.ntp.org. (39)
14:58:17.111765 lo In IP 127.0.0.1.51577 > 127.0.0.1.53: 49969+ A? 1.debian.pool.ntp.org. (39)
14:58:17.111897 lo In IP 127.0.0.1.51577 > 127.0.0.1.53: 30988+ AAAA? 1.debian.pool.ntp.org. (39)
14:58:22.811562 eth0 Out IP 10.1.0.252.50677 > 10.1.0.1.53: 53480+ A? BioDietPi. (27)
14:58:22.811579 eth0 Out IP 10.1.0.252.50677 > 10.1.0.1.53: 22421+ AAAA? BioDietPi. (27)
14:58:22.811754 eth0 In IP 10.1.0.1.53 > 10.1.0.252.50677: 53480* 1/0/0 A 10.1.0.252 (43)
14:58:22.811824 eth0 In IP 10.1.0.1.53 > 10.1.0.252.50677: 22421 0/0/0 (27)
14:58:22.909468 lo In IP 127.0.0.1.46924 > 127.0.0.1.53: 49909+ A? raspbian.raspberrypi.org. (42)
14:58:22.909468 lo In IP 127.0.0.1.51292 > 127.0.0.1.53: 15349+ A? archive.raspberrypi.org. (41)
14:58:22.909589 lo In IP 127.0.0.1.42696 > 127.0.0.1.53: 15349+ A? archive.raspberrypi.org. (41)
14:58:22.909591 lo In IP 127.0.0.1.33731 > 127.0.0.1.53: 49909+ A? raspbian.raspberrypi.org. (42)
^Z
[1]+ Stopped tcpdump -i any -c200 -nn port 53
root@BioDietPi:~# ping google.com
ping: google.com: Name or service not known
root@BioDietPi:~# dig google.com
; <<>> DiG 9.16.15-Raspbian <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26479
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 237 IN A 142.250.113.101
google.com. 237 IN A 142.250.113.139
google.com. 237 IN A 142.250.113.100
google.com. 237 IN A 142.250.113.138
google.com. 237 IN A 142.250.113.113
google.com. 237 IN A 142.250.113.102
;; Query time: 0 msec
;; SERVER: 10.1.0.1#53(10.1.0.1)
;; WHEN: Tue Dec 14 08:58:08 CST 2021
;; MSG SIZE rcvd: 135