0

Improve URL target accuracy — some legitimate download links are inaccessible.

Hey everyone,

Has anyone else run into issues where legitimate download links from well-known services just won’t load while using NextDNS?

For example, I recently tried to download a browser app (Comet by P*rplex*y), and clicking the download button just led to a dead end, the page wouldn’t load at all. As soon as I disabled NextDNS, the link worked perfectly fine.

My guess is that some redirect URLs or CDN domains used by these services are getting caught by one of the blocklists. It’s a bit annoying because the source is completely legitimate.

A few things I’m curious about:
    •    Has anyone experienced something similar with other download links?
    •    Were you able to figure out which specific domain was being blocked?
    •    Any recommended way to quickly identify and whitelist the affected domain without having to disable NextDNS entirely?

It would also be great if the NextDNS team could improve the targeting accuracy for these kinds of redirect/CDN URLs so legit downloads don’t get caught in the crossfire.

Appreciate any help or insights. Thanks!
 

1 reply

null
    • losnad
    • 6 hrs ago
    • Reported - view

    «Has anyone else run into issues where legitimate download links from well-known services just won’t load while using NextDNS?» Yes

    «For example, I recently tried to download a browser app (Comet by P*rplex*y), and clicking the download button just led to a dead end, the page wouldn’t load at all. As soon as I disabled NextDNS, the link worked perfectly fine.»

    I don't understand why you felt the need to put the stars in the name... https://www.perplexity.ai/comet > when you click on the download: perplexity.sng.link which if you look in the logs (what you should always do when encounter a issue) : Blocked by Online Gaming after you add it to the Allowlist it will redirect you to the https://www.perplexity.ai/download-comet

    «My guess is that some redirect URLs or CDN domains used by these services are getting caught by one of the blocklists. It’s a bit annoying because the source is completely legitimate.»

    «Were you able to figure out which specific domain was being blocked?» 

    «Any recommended way to quickly identify and whitelist the affected domain without having to disable NextDNS entirely?» 

    You don't need to guess anything, just check the logs on my.nextdns.io you can look immediately and see what is on top of the logs or you can select to see only the blocked domains and also look at the details to see why it was blocked. After you add to the Allowlist or you disable the setting/blocking list wait 5 minutes from the moment it was blocked in the logs before trying again.

Content aside

  • 6 hrs agoLast active
  • 1Replies
  • 14Views
  • 1 Following