Gar
Very Senior Member
I like the filtering or I'd do the same.I have. Some pages very slow to load, if they load at all.
Quad1 & Quad8 no problem.
I just use Quad1 & job’s done....
I like the filtering or I'd do the same.I have. Some pages very slow to load, if they load at all.
Quad1 & Quad8 no problem.
I just use Quad1 & job’s done....
I have. Some pages very slow to load, if they load at all.
Quad1 & Quad8 no problem.
I just use Quad1 & job’s done....
Yeah, I went back to Quad1 for now. May look into the timeout change, but Cloudflare works fine.
As per my edit above, I tried selecting the Quad9 primary server only, & now works well. Go figure.....
Is it worth me calling asus? I have talked to one of the VPs before, but that was awhile ago.
Yes, I have that same issue even with DNSSEC disabled. You may discover, as I have, that the Quad9 data center you use with normal DNS port 53 are not used with DoT. Without DoT I connect to Quad9 resolvers in Miami, Fl. With DoT enabled the querys go to Berkley, Ca! Cloudflare and CleanBrowsing use resolvers just over 100 miles away. I suspect my ISP is fooling with anycast. Or Quad9 is not fully implemented with DoT.Has anybody else tried Quad9 with DoT and DNSSEC? It randomly won’t resolve pages on occasion requiring several refreshes. I saw people in the stubby thread mention this months ago, guess it’s still a problem.
I just registered to report that I upgraded my AC86U to 45717. I then read the post from RMerlin about the changes. I then tried to install 384.11 and it won't install - it just hangs.
A reboot doesn't solve it and 45717 is still hanging on......
I had installed 45717 and then again migrated back to 384.11 with no issues. I am using Asus 86au and all the scripts are working the same way they were working before the installation of 45717.BTW, Asus's 45717 contains a "security" enhancement that means bad news for me if they did it the way I heard they did. I need to wait for access to GPL code to determine how bad it is. I knew ahead of time of the change, and I could confirm that the change made it into that release when I tested it on an RT-AC88U, however the big question is to see how it was implemented, so I can devise a workaround. For this I will need to wait until I get GPL drops for that release.
For now, be advised that if you install 45717 and then decide to switch back to my firmware, any script you had installed in /jffs/ will no longer work, and will require "fixing". I can't go into any further detail for now, sorry.
Use wipe jffs at next reboot and then flash 384.11. it worked for me and all the scripts are running without any issue.I just registered to report that I upgraded my AC86U to 45717. I then read the post from RMerlin about the changes. I then tried to install 384.11 and it won't install - it just hangs.
A reboot doesn't solve it and 45717 is still hanging on......
Yes, I have that same issue even with DNSSEC disabled. You may discover, as I have, that the Quad9 data center you use with normal DNS port 53 are not used with DoT. Without DoT I connect to Quad9 resolvers in Miami, Fl. With DoT enabled the querys go to Berkley, Ca! Cloudflare and CleanBrowsing use resolvers just over 100 miles away. I suspect my ISP is fooling with anycast. Or Quad9 is not fully implemented with DoT.
On another note, I had fewer issues with Stubby/Entware configuration than with Merlin. Yes, I too jumped at the chance to dump my USB drive and dive into 384.11 alpha, beta and final. I was critical of the Stubby configuration as it was different from Entware. I have not been comfortable with 384.11 Stubby as I can not replace the stubby.yml, the stubby.postconf does not do what I want and am tired of the family saying they can't connect.
So, for the time being I am not using DoT or DNSSEC. Just using plain Quad9 resolvers which do a good job of blocking malicious add sites (fewer hits in AiProtection). Have considered going back to 384.10 or stock Asus with Entware. But...
Sent from my SM-T380 using Tapatalk
OpenDNS has speedy servers, wish they had DoT, as you say. I used to use them and they were great.Interesting, good to know. I was using OpenDNS, but they didn’t support DoT.
I had installed 45717 and then again migrated back to 384.11 with no issues. I am using Asus 86au and all the scripts are working the same way they were working before the installation of 45717.
on mobile (at least for me) I cannot see signatures, I have to switch to desktop version in chrome to be able to see signaturesI for more than I look for it I do not see it, xDDD.
Rotate your phone horizontally, an you will see them...on mobile (at least for me) I cannot see signatures, I have to switch to desktop version in chrome to be able to see signatures
Rotate your phone horizontally, an you will see them...
Has anybody else tried Quad9 with DoT and DNSSEC? It randomly won’t resolve pages on occasion requiring several refreshes. I saw people in the stubby thread mention this months ago, guess it’s still a problem.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!