@0x56
Ah, that should have been obvious. Thanks.

@voltronic - if it were one or two, or would have been. But it's like me trying to read sheet music. I can read a note or two, but a whole page of it shuts down my brain.

@0x56 @voltronic That regex's first bit is also weird: "match either the beginning of the string or following a dot", then a TLD (though one might be unhappy blocking .tv and .ai these days...), then "end of string".

So it'd match "ai" as well as ".ai".

I'd have figured it would be something like '^.*\.(<TLD list goes here>)$'. I wonder if there's something about how the pihole uses these that changes it.

Ahem. Anyway. The weird construct at the beginning makes it weird to read :)

@lenaoflune @voltronic @0x56 Imo, (\..[tlds|go|here])$ makes more sense. Didn't do much testing for edge cases though.

@0x56 @voltronic @lenaoflune Morning brain, this is what I was trying to do: (\.[gg|vu|etc]+)$

@lenaoflune @voltronic - I had assumed it was some pihole specific filter (like my router where I actually can just specify the tld)