HowTo add raw lists to pihole server?

Please follow the below template, it will help us to help you!

If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.

no issues, although I messed it up ans started new , need to learn how to add raw or non raw adblock lists to the server

Expected Behaviour:

[Replace this text with what you think should be happening. Please include as much detail as possible including, but not limited to:
-operating system
-hardware]

pi 400 latest builds as of 05/08/22

Actual Behaviour:

[replace this text with what is actually happening]
in the previous installation , I added a rwa list of domains that just messed it up , so i started new as I do not know to remove those lists once added

Debug Token:

[Replace this text with the debug token provided from running pihole -d (or running the debug script through the web interface]

https://tricorder.pi-hole.net/8ppn3MlL/

just so you know I am following that " impossible dream to block googlevideo.com ad servers, and I know they rotate them

my biggest problem at age 64 is my memory is failing me big time, so I rely more and more these days on help from young people

thank you in advance

Please be more specific what you mean by "raw lists"? You can add and remove adlists through the web interface located at http://pi.hole/admin/index.php Group Management -> Adlists.

Side note:
You have two IPs bound to your eth0 interface. Is this on purpose?

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
    192.168.1.2/24
    192.168.1.218/24

the 192.168.1.2 is eth0 and the 192.168.1.219 is the wifi interface . is this wrong ?

Regards

Roman Toledo

Hi the 192.168.1.2 is eth0 and 219 is the wifi interface on the pi.

as for the raw list it's like this

r8.sn-4g5ednzz.googlevideo.com
r8---sn-4g5ednzz.googlevideo.com
r6.sn-4g5ednll.googlevideo.com
r6.sn-4g5edney.googlevideo.com
r6.sn-4g5ednek.googlevideo.com
r6.sn-4g5ednee.googlevideo.com
r6.sn-4g5edn7e.googlevideo.com
r6.sn-4g5e6nez.googlevideo.com
r6---sn-4g5ednll.googlevideo.com
r6---sn-4g5edney.googlevideo.com
r6---sn-4g5ednek.googlevideo.com
r6---sn-4g5ednee.googlevideo.com
r6---sn-4g5edn7e.googlevideo.com
r6---sn-4g5e6nez.googlevideo.com
r5.sn-h0jeenek.googlevideo.com
r5.sn-4g5ednzz.googlevideo.com
r5.sn-4g5ednsz.googlevideo.com
r5.sn-4g5ednsy.googlevideo.com
r5.sn-4g5ednsr.googlevideo.com
r5.sn-4g5ednsl.googlevideo.com
r5.sn-4g5ednsd.googlevideo.com
r5.sn-4g5edns6.googlevideo.com
r5.sn-4g5ednly.googlevideo.com
r5.sn-4g5edn7s.googlevideo.com
r5.sn-4g5e6nzl.googlevideo.com
r5.sn-4g5e6nze.googlevideo.com
r5.sn-4g5e6nz7.googlevideo.com
r5.sn-4g5e6nsz.googlevideo.com
r5.sn-4g5e6nsy.googlevideo.com
r5.sn-4g5e6nss.googlevideo.com
r5.sn-4g5e6nsk.googlevideo.com
r5.sn-4g5e6ns7.googlevideo.com
r5.sn-4g5e6ns6.googlevideo.com
r5.sn-4g5e6nls.googlevideo.com
r5.sn-4g5e6ney.googlevideo.com
r5.sn-4g5e6n7r.googlevideo.com
r5.sn-4g5e6n7k.googlevideo.com
r5---sn-h0jeenek.googlevideo.com
r5---sn-4g5ednzz.googlevideo.com
r5---sn-4g5ednsz.googlevideo.com
r5---sn-4g5ednsy.googlevideo.com
r5---sn-4g5ednsr.googlevideo.com
r5---sn-4g5ednsl.googlevideo.com
r5---sn-4g5ednsd.googlevideo.com
r5---sn-4g5edns6.googlevideo.com
r5---sn-4g5ednly.googlevideo.com
r5---sn-4g5edn7s.googlevideo.com
r5---sn-4g5e6nzl.googlevideo.com
r5---sn-4g5e6nze.googlevideo.com
r5---sn-4g5e6nz7.googlevideo.com
r5---sn-4g5e6nsz.googlevideo.com
r5---sn-4g5e6nsy.googlevideo.com
r5---sn-4g5e6nss.googlevideo.com
r5---sn-4g5e6nsk.googlevideo.com
r5---sn-4g5e6ns7.googlevideo.com
r5---sn-4g5e6ns6.googlevideo.com
r5---sn-4g5e6nls.googlevideo.com
r5---sn-4g5e6ney.googlevideo.com
r5---sn-4g5e6n7r.googlevideo.com
r5---sn-4g5e6n7k.googlevideo.com
r4.sn-4g5ednz7.googlevideo.com
r4.sn-4g5ednsy.googlevideo.com
r4.sn-4g5ednsk.googlevideo.com
r4.sn-4g5ednsd.googlevideo.com
r4---sn-4g5ednz7.googlevideo.com
r4---sn-4g5ednsy.googlevideo.com
r4---sn-4g5ednsk.googlevideo.com
r4---sn-4g5ednsd.googlevideo.com
r3.sn-4g5ednz7.googlevideo.com
r3.sn-4g5ednss.googlevideo.com
r3.sn-4g5ednsd.googlevideo.com
r3.sn-4g5ednls.googlevideo.com
r3.sn-4g5ednll.googlevideo.com
r3.sn-4g5ednee.googlevideo.com
r3.sn-4g5edned.googlevideo.com
r3.sn-4g5edne7.googlevideo.com
r3.sn-4g5edne6.googlevideo.com
r3.sn-4g5e6nzz.googlevideo.com
r3.sn-4g5e6nzs.googlevideo.com
r3.sn-4g5e6nsz.googlevideo.com
r3.sn-4g5e6nsy.googlevideo.com
r3.sn-4g5e6nsk.googlevideo.com
r3.sn-4g5e6nle.googlevideo.com
r3.sn-4g5e6nld.googlevideo.com
r3---sn-4g5ednz7.googlevideo.com
r3---sn-4g5ednss.googlevideo.com
r3---sn-4g5ednsd.googlevideo.com
r3---sn-4g5ednls.googlevideo.com
r3---sn-4g5ednll.googlevideo.com
r3---sn-4g5ednee.googlevideo.com
r3---sn-4g5edned.googlevideo.com
r3---sn-4g5edne7.googlevideo.com
r3---sn-4g5edne6.googlevideo.com
r3---sn-4g5e6nzz.googlevideo.com
r3---sn-4g5e6nzs.googlevideo.com
r3---sn-4g5e6nsz.googlevideo.com
r3---sn-4g5e6nsy.googlevideo.com
r3---sn-4g5e6nsk.googlevideo.com
r3---sn-4g5e6nle.googlevideo.com
r3---sn-4g5e6nld.googlevideo.com
r2.sn-hp57kn6e.googlevideo.com
r2.sn-h0jeln7e.googlevideo.com
r2.sn-h0jeener.googlevideo.com
r2.sn-h0jeen76.googlevideo.com
r2.sn-4g5ednzz.googlevideo.com
r2.sn-4g5ednly.googlevideo.com
r2.sn-4g5ednls.googlevideo.com
r2.sn-4g5ednle.googlevideo.com
r2.sn-4g5ednee.googlevideo.com
r2.sn-4g5edned.googlevideo.com
r2.sn-4g5edn7y.googlevideo.com
r2.sn-4g5e6nsz.googlevideo.com
r2.sn-4g5e6nsy.googlevideo.com
r2.sn-4g5e6nsk.googlevideo.com
r2.sn-4g5e6ns6.googlevideo.com
r2.sn-4g5e6nl7.googlevideo.com
r2.sn-4g5e6ney.googlevideo.com
r2---sn-hp57kn6e.googlevideo.com
r2---sn-h0jeln7e.googlevideo.com
r2---sn-h0jeener.googlevideo.com
r2---sn-h0jeen76.googlevideo.com
r2---sn-4g5ednzz.googlevideo.com
r2---sn-4g5ednse.googlevideo.com
r2---sn-4g5ednly.googlevideo.com
r2---sn-4g5ednls.googlevideo.com
r2---sn-4g5ednle.googlevideo.com
r2---sn-4g5ednee.googlevideo.com
r2---sn-4g5edned.googlevideo.com
r2---sn-4g5edn7y.googlevideo.com
r2---sn-4g5e6nsz.googlevideo.com
r2---sn-4g5e6nsy.googlevideo.com
r2---sn-4g5e6nsk.googlevideo.com
r2---sn-4g5e6ns6.googlevideo.com
r2---sn-4g5e6nl7.googlevideo.com
r2---sn-4g5e6ney.googlevideo.com
r15.sn-4g5ednzz.googlevideo.com
r15---sn-4g5ednzz.googlevideo.com
r11.sn-4g5ednzz.googlevideo.com
r11---sn-4g5ednzz.googlevideo.com
r10.sn-4g5ednzz.googlevideo.com
r10---sn-4g5ednzz.googlevideo.com
r1.sn-h0jeln7e.googlevideo.com
r1.sn-h0jeened.googlevideo.com
r1.sn-h0jeen76.googlevideo.com
r1.sn-4g5ednsd.googlevideo.com
r1.sn-4g5ednly.googlevideo.com
r1.sn-4g5ednll.googlevideo.com
r1.sn-4g5edne6.googlevideo.com
r1.sn-4g5e6nzz.googlevideo.com
r1.sn-4g5e6nz7.googlevideo.com
r1.sn-4g5e6nsy.googlevideo.com
r1.sn-4g5e6nez.googlevideo.com
r1---sn-h0jeln7e.googlevideo.com
r1---sn-h0jeened.googlevideo.com
r1---sn-h0jeen76.googlevideo.com
r1---sn-4g5ednsd.googlevideo.com
r1---sn-4g5ednly.googlevideo.com
r1---sn-4g5ednll.googlevideo.com
r1---sn-4g5edne6.googlevideo.com
r1---sn-4g5e6nzz.googlevideo.com
r1---sn-4g5e6nz7.googlevideo.com
r1---sn-4g5e6nsy.googlevideo.com
r1---sn-4g5e6ns7.googlevideo.com
r1---sn-4g5e6nez.googlevideo.com
manifest.googlevideo.com
r8.sn-n02xgoxufvg3-2gbs.googlevideo.com
r8---sn-n02xgoxufvg3-2gbs.googlevideo.com
r6.sn-4g5edne7.googlevideo.com
r6---sn-4g5edne7.googlevideo.com
r5.sn-hp57yn7y.googlevideo.com
r5---sn-hp57yn7y.googlevideo.com
r4.sn-h0jeln7l.googlevideo.com
r4.sn-h0jeln7e.googlevideo.com
r4.sn-h0jeened.googlevideo.com
r4.sn-4g5ednzz.googlevideo.com
r4.sn-4g5edns7.googlevideo.com
r4.sn-4g5ednly.googlevideo.com
r4.sn-4g5ednld.googlevideo.com
r4.sn-4g5edney.googlevideo.com
r4.sn-4g5e6nzs.googlevideo.com
r4.sn-4g5e6ns6.googlevideo.com
r4.sn-4g5e6nez.googlevideo.com
r4---sn-h0jeln7l.googlevideo.com
r4---sn-h0jeln7e.googlevideo.com
r4---sn-h0jeened.googlevideo.com
r4---sn-4g5ednzz.googlevideo.com
r4---sn-4g5edns7.googlevideo.com
r4---sn-4g5ednly.googlevideo.com
r4---sn-4g5ednld.googlevideo.com
r4---sn-4g5edney.googlevideo.com
r4---sn-4g5e6nzs.googlevideo.com
r4---sn-4g5e6ns6.googlevideo.com
r4---sn-4g5e6nez.googlevideo.com
r3.sn-4g5ednzz.googlevideo.com
r3.sn-4g5ednsz.googlevideo.com
r3.sn-4g5edns6.googlevideo.com
r3.sn-4g5ednld.googlevideo.com
r3.sn-4g5e6nsr.googlevideo.com
r3.sn-4g5e6nl7.googlevideo.com
r3---sn-4g5ednzz.googlevideo.com
r3---sn-4g5ednsz.googlevideo.com
r3---sn-4g5edns6.googlevideo.com
r3---sn-4g5ednld.googlevideo.com
r3---sn-4g5e6nsr.googlevideo.com
r3---sn-4g5e6nl7.googlevideo.com
r2.sn-4g5ednse.googlevideo.com
r2.sn-4g5ednld.googlevideo.com
r2.sn-4g5e6nzl.googlevideo.com
r2.sn-4g5e6nez.googlevideo.com
r2---sn-4g5ednld.googlevideo.com
r2---sn-4g5e6nzl.googlevideo.com
r2---sn-4g5e6nez.googlevideo.com
r1.sn-4g5ednsr.googlevideo.com
r1.sn-4g5ednsl.googlevideo.com
r1.sn-4g5ednse.googlevideo.com
r1.sn-4g5edned.googlevideo.com
r1.sn-4g5e6ns7.googlevideo.com
r1.sn-4g5e6ns6.googlevideo.com
r1.sn-4g5e6nl6.googlevideo.com
r1.sn-4g5e6ne6.googlevideo.com
r1---sn-4g5ednsr.googlevideo.com
r1---sn-4g5ednsl.googlevideo.com
r1---sn-4g5ednse.googlevideo.com
r1---sn-4g5edned.googlevideo.com
r1---sn-4g5e6ns6.googlevideo.com
r1---sn-4g5e6nl6.googlevideo.com
r1---sn-4g5e6ne6.googlevideo.com

I think I will just add them one by one and test as I go along

As I said: .2 and .218 are assigned to the eth0 interface. .219 is assigned to the wlan0 interface.


Those would be domains and not adlists. You need to enter them via Group management -> Domains. You should be able to copy & past them all at the same time into the input field.

thank you for the reply. I have had a difficult time forcing x.x.x.2 to eth0 . so I got the pi now doing the static as well as the router. so I will look around in the pi settings to remove the .218 . thank you again.

I hope this is not outside the focus of this thread:

how and where in linux or windows can I see a list of the dns lookups ? just to play with youtube in one machine and see what ad servers are looked up?

any links on how to do this is highly appreciated (I am running BIND inside win11 and if I did not mess it up , it's supposed to be logging

I don't think you can see this directly on your client's OS, but rather at your DNS server's log (which is Pi-hole in your case)

ok I used to be the guy that hated asking dumb questions, and often said RTFM . oh well my time is here.

I just compiled to the latest ftl 5.15 will look around and see where that is kept , just burning time doing this as my newest hobby.

here is my new debug link

https://tricorder.pi-hole.net/4osnsbj0/

You can use the query log of the web interface or /var/log/pihole.log

1 Like

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.