mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
Legitimate site, blocked #69
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#69
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Oct 21, 2016).
I'm testing Adguard DNS which i've just discovered, works nicely, also via DNSCrypt.
Because of the very nature of this DNS (Ad Blocking & Browsing Security) some urls may be blocked by mistake.
I'm encountering this most legitimate site, blocked only when resolved with Adguard DNS:
Hope this gets fixed- Thanks.
EDIT- Much more problematic in fact
I've just found out that if pluzz.francetv.fr was blocked when resolved by Adguard DNS it is because the resolved url's IP was 87.245.196.91, that this 87.245.196.91 was blocked by my PeerBlock application because it lists 87.245.196.91 as Skytiz Network in its Webexploit filter ...
Indeed, submitting pluzz.francetv.fr to iplookup.flagfox.net shows:
Hostname : pluzz.francetv.fr
IP Address : 62.253.72.81
Disabling PeerBlock allows pluzz.francetv.fr to display correctly. It seems the process transited via Skytiz Network which is why it was blocked by PeerBlock. Is this normal?
Peerblock blocked 87.245.196.91 named as Skytiz Network and 87.245.196.91 is part of PeerBlock's Webexploit filters' list. This list is described at https://www.iblocklist.com/list?list=ghlzqtqxnzctvvajwwag as:
So, is there a problem and if so, where is it?
This was for your information. Interpreting these facts is above my skills.
Thanks
@Alex-302 commented on GitHub (Oct 22, 2016):
Hi
The site works as expected with our DNS, nothing blocked
@ghost commented on GitHub (Oct 22, 2016):
Perhaps you're answering to my post's title only, Alex-202.
I've developed my comment if you read me carefully to point out that pluzz.francetv.fr was blocked by PeerBlock and that PeerBlock was blocking one of AdGuards distribution servers, 87.245.196.91 named as Skytiz Network
Moreover, having a look at https://dnsleaktest.com/ showed several DNS servers (which is good for speed) but that ALL these servers were Google servers. If Adguard DNS is hopping from one Google server to another to resolve my quest then it's not for me.
Good luck.
@ameshkov commented on GitHub (Oct 24, 2016):
@Alex-302 takes care of filtering issues, and we need a dev to answer your question:)
So, what's going on:
87.245.196.91is IP address of one of the Akamai CDN nodes.pluzz.francetv.fruses Akamai CDN.We currently have servers in two locations only: US and RU. Still waiting for EU and asian servers: #33. The ETA is a few weeks from now.
@ghost commented on GitHub (Oct 24, 2016):
@ameshkov , OK, but the point remains all this would have been transparent if the Webexploit filters' list of PeerBlock hadn't blocked 87.245.196.91 - The question is to know if this 87.245.196.91 is founded or not to appear in this Webexploit's list. That is the only question.
@ameshkov commented on GitHub (Oct 24, 2016):
Due to CDN nature their IP are often incorrectly blocked, so the right thing to do is to report it to the list authors.
@ghost commented on GitHub (Oct 24, 2016):
Often maybe not, but this can happen, indeed. As it may not. Incertitude.
Thanks for your concern.
I don't think you should close this thread, it concerns unresolved matter, other users could include their knowledge/experience. It is of course your choice
@ameshkov commented on GitHub (Oct 27, 2016):
I'd prefer to have separate issues for each case.
You see, it'll help with issues search in case if some issue re-occurs.