serverless-dns / serverless-dns

The RethinkDNS resolver that deploys to Cloudflare Workers, Deno Deploy, Fastly, and Fly.io

Home Page:https://rethinkdns.com/configure

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Configure page does not reflect actual blocklist selection

vinnyang opened this issue · comments

N__PwDg_wP9_97hAEAYCAQAgKDwH1zqAJA=

Configuration string in screenshot: 1:-N__PwDg_wP9_97hAEAYCAQAgKDwH1zqAJA=

Some blocklists under threat-intelligence-feeds while not being selected in the configuration page, they are shown as included in the Search page. And domains in those deselected blocklists are actually being blocked…

We made some extensive changes to the way we build and use blocklists... it could be that the search page is wrong. I'll take a look at this rather severe bug the first thing when I get free from another unrelated fire-fight. Thanks a lot for reporting this!

And domains in those deselected blocklists are actually being blocked…

You mean the search page is accurate?

Oh wait, I just saw the screenshot of the search page. It is searching from an older version of the blocklists (5 Sep). The current is 12 Nov. Ignore "no matches" (broken right now, will fix it), but drive.google.com is blocked by Bad Sites which is selected in 1:-N__PwDg_wP9_97hAEAYCAQAgKDwH1zqAJA=

screenshot: 12 Nov:

Screenshot 2022-11-14 at 11-56-22 Search RethinkDNS

Hmmm…my original problem was, as you can see in the left of my screenshot, I did not add the two blocklists that block drive.google.com in the Configuration page (their buttons still say Add), but when I go to the Search page, it says that configuration does contain the 2 blocklists I did not select…

Ignore "no matches" (broken right now, will fix it)

Ahh I think I was also confused by this.

Okay, after some struggle, everything should be up and running as expected (on the search page, on the configure page). If that isn't the case, let me know.

(if you do, then try testing (configure, search) in incognito / private browsing mode just to make sure browser's cache isn't getting in the way of the shiny new js files that contain the fixes).

Feel free to reopen in case the bug isn't really fixed or manifests in some other ui flow.