Skip to content

Difference in Resolution/Blocking between PiHole and RethinkDNS #2440

@yoshimo

Description

@yoshimo

blog.joinmastodon.org

blog.joinmastodon.org.     	600 	CNAME 	mastodon.github.io.
mastodon.github.io.     	3600 	A 	185.199.108.153

this resolved on Pihole just fine
It is blocked on rethinkDNS

Both use the same set of Blocklists, in this case
https://easylist-downloads.adblockplus.org/ruadlist.txt

http://tagesschau-podcast.ard-mcdn.de/

tagesschau-podcast.ard-mcdn.de.     	3600 	CNAME 	tagesschaupodcast-stream.trafficmanager.net.
tagesschaupodcast-stream.trafficmanager.net.     	60 	CNAME 	tagesschau-podcast.ard-mcdn.de.akamaized.net.
tagesschau-podcast.ard-mcdn.de.akamaized.net.     	21600 	CNAME 	a899.dscw4.akamai.net.
a899.dscw4.akamai.net.     	20 	CNAME 	a899.dscw4.akamai.net.0.1.cn.akamaitech.net.
a899.dscw4.akamai.net.0.1.cn.akamaitech.net.     	20 	A 	95.101.137.158
a899.dscw4.akamai.net.0.1.cn.akamaitech.net.     	20 	A 	95.101.137.154

This is hit by by

trafficmanager.net
Microsoft/ParentalControl
(DISABLED)
de.akamaized.net
Blocklist (ph00lt0)↗

Same as above, Pihole resolves this. RethinkDNS does not.
Is this a caching issue, is this a matter of differences in the way these systems do qname minimisation and resolve from the root down?
Are there differences in parsing the Blocklists in ABP format?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions