Rockpro64 Headless Server Reliably Becomes Unresponsive

[Doneganai7]

I have collected more data, but I am not sure what to make of it.

ping -c 4 192.168.0.1 # This is my router

PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=3.15 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.669 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.656 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.808 ms

--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 0.656/1.322/3.156/1.060 ms

ping -c 4 1.1.1.1

PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=56 time=11.1 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=56 time=23.4 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=56 time=13.5 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=56 time=14.1 ms

--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 11.142/15.587/23.474/4.692 ms

ping -c 4 google.com

ping: google.com: Name or service not known

dig google.com

; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached

dig @1.1.1.1 google.com

; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> @1.1.1.1 google.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

dig @8.8.8.8 google.com

; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> @8.8.8.8 google.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

I was also monitoring "dmesg | tail" and nothing new came up between when everything was working, and when it went back to broken.

I am not sure why I would be able to successfully ping a well known DNS server, but not use it to resolve IPs. Does this give any clues as to where to look next?