[latestthing]

I have reset to factory defaults and flashed to latest (Firmware: DD-WRT v3.0-r48432 std (03/01/22).

In an effort to get ANY DNS to work I have tried using default settings (to use my ISP DNS) and that did not work.

I have tried many configurations (and read so many posts and tutorials i can't keep track andam at my wit's end) but currently have it set to use cloudflare DNS. I have attached screenshots of this config. (please let me know if there are other relevant setting I might be missing!)

No matter what I try, nothing can resolve DNS.

[Alozaros]

first make sure your NTP time is working and router receives correct time..
Basic set up>down at the bottom NTP time...

also disable 'Query DNS in strict order'

than try to add those lines to advanced DNSmasq options

no-resolv
server=1.1.1.1
server=1.0.0.1


there may be an option, where your ISP DNS is forcing a strict use of their DNS provided...but, as you tried already ISP dns and its not working this is suspicious...

also to override it, in case of forced DNS try to turn on encrypt DNS option as a last measure...

[egc]

Reset to defaults and put settings in manually.
from CLI interface/Putty:
nvram erase && reboot

For DNS settings On Setup page:
tick/enable "Ignore WAN DNS"

As DNS servers use (Static DNS 1 and 2):
1.1.1.1
1.0.0.1

(1.1.0.0 is not a valid DNS server!)

On services page make sure you Disable "Query DNS in Strict Order"
When you have reset to defaults on a recent build it should already be disabled.

[kernel-panic69]

I still haven't disabled query in strict order. And I don't use any static DNS entries, everything is via additional configs and I use forced DNS redirection option.

[mrjcd]

just throwing this out --- I am a bit 'across the way' since I use the EA8500 ...but anyways:

[latestthing]

Firstly thank you all for the attempts at troubleshooting. I have tried all of the mentioned tips, but the problem remains that I cannot resolve DNS server.

I have noticed that my dnsmasq.conf file has a line that does not seem to be represented in the GUI and I am suspicious that it is causing the issue. I have bolded the suspicious line below (server=127.0.0.1#30)

following images is my config attempting to use quad9 encrypted DNS and here is my dnsmasq.conf file:
interface=br0
resolv-file=/tmp/resolv.dnsmasq
strict-order
server=127.0.0.1#30
no-resolv
dhcp-leasefile=/tmp/dnsmasq.leases
dhcp-lease-max=190
dhcp-option=br0,3,192.168.1.1
dhcp-authoritative
dhcp-range=br0,192.168.1.64,192.168.1.253,255.255.255.0,1440m
bogus-priv
conf-file=/etc/rfc6761.conf
clear-on-reload
stop-dns-rebind
dhcp-option=252,"\n"
cache-size=1500
no-resolv
server=9.9.9.9
server=9.9.9.10





please let me know if anybody knows where that server=127.0.0.1#30 is coming from and if that is normal.

[egc]

Well it does not look like you followed my advice

[foz111]

You can lead a horse to water but you can't make it drink !

[redhawk0]

Try setting your gateway to 192.168.1.1
Enable "Recursive DNS Resolving (Unbound) and Forced DNS Redirection.

Remove all DNS addresses on the Setup>>Basic page.

duplicate my setup on Services>Services

See if that works.

redhawk

[ho1Aetoo]

why are upstream dns servers entered in the additional dnsmasq config if unbound is activated?

makes no sense

[Alozaros]

latestthing using encrypted DNS option, usually adds this line to the DNSmasq.config

server=127.0.0.1#30

and shortly... this is how encrypted DNS works...

than, if you add another lines like those

server=9.9.9.9
server=1.1.1.1

you cause your own mess...as DNSmasq will get messy

you either use one of those options...either encrypted DNS or added servers= in advance DNSmasq box

your best bet is to use only encrypted DNS....
if its not working, than you must have troubles...more often NTP time is not correct...

choose correct time zone and,
add this IP to basic settings>ntp time box
162.159.200.1

this is cloudflare ntp time server...

than save apply and reboot...

for more advanced uses of DNS services check red and green links in my signature...

[latestthing]

just FYI to any others that see this. It simply started working again on its own. My only viable theory is that my ISP (comcast xfinity ) did something that broke custom DNS or even encrypted DNS somehow and then fixed it.

I had encrypted DNS settings and it didn't work for days and then suddenly did with no changes to settings.

[mrjcd]

Check what DNS servers you are using from:

https://www.top10vpn.com/tools/what-is-my-dns-server/
OR
https://ipleak.net/

also NOTE:
the silly mozilla people with last few new FireFox browsers has 'DNS over HTTPS' enabled by default
so that will get around most common router settings unless you disable it...
which I always make sure 'DNS over HTTPS' is disabled because FF default is to use Cloudflare servers
for it AND I am NOT a fan of them