DNS seems to stop all of a sudden (Stubby w/NextDNS)

I have the Convexa-S running v3.104. I have NextDNS DoT using Stubby. It works fine until it doesn’t. All of a sudden the router stops resolving DNS queries sent by connected devices. When I check the NextDNS log I can see the router set the query but the devices on the network never actually receive the response.

It seems like the way to fix this is to go to 192.168.8.1 > disable DNS over TLS from Cloudflare then re-enable it.

Anyone else facing similar issues?

#NOTE: See ‘/etc/stubby/stubby.yml.default’ for original config file and descriptions

resolution_type: GETDNS_RESOLUTION_STUB

dns_transport_list:

  • GETDNS_TRANSPORT_TLS

tls_authentication: GETDNS_AUTHENTICATION_REQUIRED

tls_query_padding_blocksize: 128

edns_client_subnet_private : 0

round_robin_upstreams: 1

idle_timeout: 10000

timeout: 5000

tls_connection_retries: 5

tls_backoff_time: 300

dnssec_return_status: GETDNS_EXTENSION_TRUE

listen_addresses:

  • 127.0.0.1@53535
  • 0::1@53535

upstream_recursive_servers:

IPv6 addresses

# Cloudflare IPv6

# Cloudflare IPv6 secondary

# Quad 9 IPv6

- address_data: 2620:fe::10

tls_auth_name: “dns.quad9.net

IPv4 addresses

# Cloudflare servers

# Cloudflare servers secondary

Quad 9 service

- address_data: 9.9.9.10

tls_auth_name: “dns.quad9.net