▲ 828 ▼ Amazon is now automatically playing fullscreen video ads on Fire TV (9to5google.com) submitted 2 years ago by throws_lemy@lemmy.nz to c/technology@lemmy.world 262 comments fedilink hide all child comments
[–] ultranaut@lemmy.world 1 point 2 years ago (1 child) Do you know what you had to block to stop the Roku ads? permalink fedilink source parent hideshow 2 child comments replies: [–] linearchaos@lemmy.world 5 points 2 years ago* (last edited 2 years ago) (1 child) It came free with one of the standardized block lists. Let me go see what my pi hole is blocking. I can't tell exactly what it's nixing without rebooting it and there's somebody watching it right now. Here are the obvious candidates from the Stephen Black block list P.ads.roku.com Austin.logs.roku.com Mobile.logs.roku.com Scribe.logs.roku.com logs.Roku.com permalink fedilink source parent hideshow 2 child comments replies: [–] ultranaut@lemmy.world 2 points 2 years ago* (1 child) Interesting. I'm using nextdns on my router, I had manually blocked ads.roku.com and now have the Stephen Black block list enabled too but I'm still getting ads. Now that I look through my nextdns logs, I don't see my roku at all so something seems to be up with my config. Thanks for the help! permalink fedilink source parent hideshow 2 child comments replies: [–] linearchaos@lemmy.world 3 points 2 years ago (1 child) If you can't get it straightened out Hit me up again here and I'll restart my Roku and see if I can figure out what else it's hitting permalink fedilink source parent hideshow 2 child comments replies: [–] ultranaut@lemmy.world 4 points 2 years ago (1 child) Thanks! I've just got it working now - something weird is going on with my ddns setup but manually linking my IP to the nextdns profile did it. permalink fedilink source parent hideshow 2 child comments replies: [–] Metacortechs@lemmy.world 5 points 2 years ago Something to be aware of, some devices will straight ignore your DNS settings in DHCP if they can't get to their ads. My iPhone 13 did that. I had to block port 53 udp/tcp for everything but the piholes. I'm sure eventually we're going to see DNS over https doing the same and I'm 100% ready to mitm all devices that pull that bullshit.. permalink fedilink source parent
[–] linearchaos@lemmy.world 5 points 2 years ago* (last edited 2 years ago) (1 child) It came free with one of the standardized block lists. Let me go see what my pi hole is blocking. I can't tell exactly what it's nixing without rebooting it and there's somebody watching it right now. Here are the obvious candidates from the Stephen Black block list P.ads.roku.com Austin.logs.roku.com Mobile.logs.roku.com Scribe.logs.roku.com logs.Roku.com permalink fedilink source parent hideshow 2 child comments replies: [–] ultranaut@lemmy.world 2 points 2 years ago* (1 child) Interesting. I'm using nextdns on my router, I had manually blocked ads.roku.com and now have the Stephen Black block list enabled too but I'm still getting ads. Now that I look through my nextdns logs, I don't see my roku at all so something seems to be up with my config. Thanks for the help! permalink fedilink source parent hideshow 2 child comments replies: [–] linearchaos@lemmy.world 3 points 2 years ago (1 child) If you can't get it straightened out Hit me up again here and I'll restart my Roku and see if I can figure out what else it's hitting permalink fedilink source parent hideshow 2 child comments replies: [–] ultranaut@lemmy.world 4 points 2 years ago (1 child) Thanks! I've just got it working now - something weird is going on with my ddns setup but manually linking my IP to the nextdns profile did it. permalink fedilink source parent hideshow 2 child comments replies: [–] Metacortechs@lemmy.world 5 points 2 years ago Something to be aware of, some devices will straight ignore your DNS settings in DHCP if they can't get to their ads. My iPhone 13 did that. I had to block port 53 udp/tcp for everything but the piholes. I'm sure eventually we're going to see DNS over https doing the same and I'm 100% ready to mitm all devices that pull that bullshit.. permalink fedilink source parent
[–] ultranaut@lemmy.world 2 points 2 years ago* (1 child) Interesting. I'm using nextdns on my router, I had manually blocked ads.roku.com and now have the Stephen Black block list enabled too but I'm still getting ads. Now that I look through my nextdns logs, I don't see my roku at all so something seems to be up with my config. Thanks for the help! permalink fedilink source parent hideshow 2 child comments replies: [–] linearchaos@lemmy.world 3 points 2 years ago (1 child) If you can't get it straightened out Hit me up again here and I'll restart my Roku and see if I can figure out what else it's hitting permalink fedilink source parent hideshow 2 child comments replies: [–] ultranaut@lemmy.world 4 points 2 years ago (1 child) Thanks! I've just got it working now - something weird is going on with my ddns setup but manually linking my IP to the nextdns profile did it. permalink fedilink source parent hideshow 2 child comments replies: [–] Metacortechs@lemmy.world 5 points 2 years ago Something to be aware of, some devices will straight ignore your DNS settings in DHCP if they can't get to their ads. My iPhone 13 did that. I had to block port 53 udp/tcp for everything but the piholes. I'm sure eventually we're going to see DNS over https doing the same and I'm 100% ready to mitm all devices that pull that bullshit.. permalink fedilink source parent
[–] linearchaos@lemmy.world 3 points 2 years ago (1 child) If you can't get it straightened out Hit me up again here and I'll restart my Roku and see if I can figure out what else it's hitting permalink fedilink source parent hideshow 2 child comments replies: [–] ultranaut@lemmy.world 4 points 2 years ago (1 child) Thanks! I've just got it working now - something weird is going on with my ddns setup but manually linking my IP to the nextdns profile did it. permalink fedilink source parent hideshow 2 child comments replies: [–] Metacortechs@lemmy.world 5 points 2 years ago Something to be aware of, some devices will straight ignore your DNS settings in DHCP if they can't get to their ads. My iPhone 13 did that. I had to block port 53 udp/tcp for everything but the piholes. I'm sure eventually we're going to see DNS over https doing the same and I'm 100% ready to mitm all devices that pull that bullshit.. permalink fedilink source parent
[–] ultranaut@lemmy.world 4 points 2 years ago (1 child) Thanks! I've just got it working now - something weird is going on with my ddns setup but manually linking my IP to the nextdns profile did it. permalink fedilink source parent hideshow 2 child comments replies: [–] Metacortechs@lemmy.world 5 points 2 years ago Something to be aware of, some devices will straight ignore your DNS settings in DHCP if they can't get to their ads. My iPhone 13 did that. I had to block port 53 udp/tcp for everything but the piholes. I'm sure eventually we're going to see DNS over https doing the same and I'm 100% ready to mitm all devices that pull that bullshit.. permalink fedilink source parent
[–] Metacortechs@lemmy.world 5 points 2 years ago Something to be aware of, some devices will straight ignore your DNS settings in DHCP if they can't get to their ads. My iPhone 13 did that. I had to block port 53 udp/tcp for everything but the piholes. I'm sure eventually we're going to see DNS over https doing the same and I'm 100% ready to mitm all devices that pull that bullshit.. permalink fedilink source parent