It takes ~1.5min before new DHCP hosts are resolved.
I've mixed results on that one, ranging from a few seconds to something like what you've experienced. _________________ 1x Netgear R7800 (latest); 3x Netgear R7000 (latest); 2x Asus RT-N16 (v3.0-r47656); 2x Fonera 2100 (v3.0-r45454).
Version r50906 seems to include your patches, thank you guys!
For anyone reading this in the future, my current DNS config is:
Apparently there's a small issue with this setup - the router itself can't resolve DNS:
Code:
root@router:/tmp# ping google.com
ping: bad address 'google.com'
No nameserver is included at /tmp/resolv.conf. _________________ 1x Netgear R7800 (latest); 3x Netgear R7000 (latest); 2x Asus RT-N16 (v3.0-r47656); 2x Fonera 2100 (v3.0-r45454).
Joined: 16 Nov 2015 Posts: 6410 Location: UK, London, just across the river..
Posted: Tue Nov 22, 2022 7:27 Post subject:
well...SmartDNS in DDWRT in my case works ok along with DNSmasq via port 6053 it acts like a subresolver...i guess if you use it via port 53 without DNSmasq, it wont be a stubresolving...
i've never tried and wanted to use SmartDNS directly via port 53...moreover you want to use its encrypting capabilities, either via port 853 or 443, so i guess if you use encrypted servers, it wont go over port 53... i believe
if you want to try it without DNSmasq over port 53 you must specify plain DNS servers like just 9.9.9.9 or 1.1.1.1
(well... cloudflare must not be used along other dns's, as its recommended for some odd reason although it works ok) _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Joined: 16 Nov 2015 Posts: 6410 Location: UK, London, just across the river..
Posted: Tue Nov 22, 2022 10:46 Post subject:
ho1Aetoo wrote:
are you seriously claiming that you have to start smartdns on a specific port to use DoH or DoT?
so the complete dd-wrt implementation is faulty?
i don't know how my router does it but it can resolve dns very well
well...I'm away to do any tests...but speaking of logic and functionality...with DDWRT, to my understanding SmartDNS can works either as a stubresolver via port 6053 or as a normal DNS resolver via port 53...with or without DNSmasq (never tried the second option)
So, ho1Aetoo do you think encrypted servers with work via port 53...
As i said above i never wanted to use SmartDNS on default port 53...unencrypted
As well as you know DoT & DoH are over 853 & 443...
Things that i ve never tried too:
-is to use other local port different than 6053...like i use with Stubby...
-or use SmartDNS as a normal resolver via port 53...as im chasing a different functionality of it..
-never tried to see via (wireshark) if SmartDNS encrypts the load..but tested it using cloudflare via 853 and their testing site...
TCB13if you have ticked SmartDNS servers only option, you dont have to put any DNS IP in the standard DNS x3 box, as this will ignore any DNS set anywhere else, and use those set in SmartDNS box only..
in general SmartDNS (in DDWRT) nowadays works out of the box, you just have to put servers in its box and tick SmartDNS servers only option...and im very happy chappy with this option and encrypted functionality, thanks to anyone who contributed towards this functionality...mainly egc, bs, the joker and others.. _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Last edited by Alozaros on Tue Nov 22, 2022 10:56; edited 1 time in total
Joined: 16 Nov 2015 Posts: 6410 Location: UK, London, just across the river..
Posted: Tue Nov 22, 2022 11:01 Post subject:
ho1Aetoo wrote:
It doesn't matter on which port smardns is running, this is the port in the internal network with which unencrypted clients connect.
Depending on the configured server smartdns forwards the requests to an upstream server via DoH or DoT.
yes internally yes you are very much correct , it should be like that, unless BS fixed it to 6053 only, but i doubt... this is not the case here i believe ..and there is no point of using port 53 locally as the stubresolver usually drops the traffic on port 53 and uses 127.0.0.1:6053 (or whatever) may be it will get confused if port 53 is used locally i donno, in your case yes, it is working
to TBC your spelling looks different than the one i use in SmartDNS