Please follow the below template, it will help us to help you!
standard pi-hole on pi4 .
Expected Behavior:
Allow www.amazon.com . Was allowing until just recently.
Actual Behaviour:
blocking www.amazon.com
Allow www.amazon.com . Was allowing until just recently.
blocking www.amazon.com
In the Admin UI look under Tools -> Search Adlists.
only a "Search Partial match" finds www.amazon.com but includes .auth.sign.in.i360marketing.com
Match found in https://phishing.army/download/phishing_army_blocklist_extended.txt: www.amazon.com.auth.sign.in.i360marketing.com Match found in https://v.firebog.net/hosts/RPiList-Phishing.txt: www.amazon.com.auth.sign.in.i360marketing.com
if I'm reading this right, the entry
www.amazon.com.auth.sign.in.i360marketing.com
is blocking
www.amazon.com ?
also, without any changes made it started working again, then I flushed DNS and it stopped again.
I disabled those two lists and www.amazon.com is working again.
The question is, should I have had to removed them to fix amazon?
www.amazon.com.auth.sign.in.i360marketing.com
is not the same name as
www.amazon.com
Should I add www.amazon.com in the white list?
It's not blocking www.amazon.com it's blocking the domain farther down the list (cname blocking).
Here is my dig output for www.amazon.com and you can see how it drills down to the actual ip address:
; <<>> DiG 9.18.12-0ubuntu0.22.04.2-Ubuntu <<>> www.amazon.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34954
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;www.amazon.com. IN A
;; ANSWER SECTION:
www.amazon.com. 245 IN CNAME tp.47cf2c8c9-frontier.amazon.com.
tp.47cf2c8c9-frontier.amazon.com. 60 IN CNAME d3ag4hukkh62yn.cloudfront.net.
d3ag4hukkh62yn.cloudfront.net. 60 IN A 65.8.169.144
;; Query time: 71 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Fri Aug 11 13:21:22 PDT 2023
;; MSG SIZE rcvd: 138
Search your adlist for d3ag4hukkh62yn.cloudfront.net or white list www.amazon.com.
I added the two list back and updated the db
d3ag4hukkh62yn.cloudfront.net is not found
also, flushed dns and amazon is working again.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.