DNS Failing Randomly

Support / Troubleshooting
1

Hello,

I recently started using Twingate on my F36 box and I’m having an issue where after some time, all DNS queries begin to lag and fail. It takes around ~10 minutes post connection for the issue to arise. Here’s what I’ve got from the logs:

Sep  7 09:23:02 Lappy twingated[1474468]: [msg] Nameserver 192.168.1.1:53 has failed: request timed out.
Sep  7 09:23:02 Lappy twingated[1474468]: [msg] All nameservers have failed
[root@Lappy log]# telnet 192.168.1.1 53
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
[root@Lappy log]# dig @192.168.1.1 google.com

; <<>> DiG 9.16.40-RH <<>> @192.168.1.1 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 135
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             95      IN      A       172.253.115.100
google.com.             95      IN      A       172.253.115.113
google.com.             95      IN      A       172.253.115.139
google.com.             95      IN      A       172.253.115.138
google.com.             95      IN      A       172.253.115.101
google.com.             95      IN      A       172.253.115.102

;; Query time: 1 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Sep 07 09:24:39 EDT 2023
;; MSG SIZE  rcvd: 135

[root@Lappy log]# dig google.com

; <<>> DiG 9.16.40-RH <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached

[root@Lappy log]# cat /etc/resolv.conf
nameserver 127.0.0.53
options edns0 trust-ad
search .

[root@Lappy log]# NetworkManager -V
1.38.6-1.fc36

As seen above, Twingate says my DNS server is down, but it’s clearly still able to resolve queries, though NetworkManager is not.

Any ideas what may be causing this?

2

I’ve been having a similar experience lately and haven’t been able to nail down the issue. It seems to be rather inconsistent.

1 Like
3

Hi there,

This could be a number of things – if you put your connector into Debug mode and get some logs as per this knowledge base article (after the issue has occurred), there may be more relevant information as to what’s going on.

Is the machine going to sleep at all or anything like that, or staying powered up and just suddenly failing after the period of time?

-arthur

4

I will grab those debug logs :). This computer is configured to not sleep, and I’ve had the problem occur suddenly while performing day to day tasks.