[HELP] How does blocky (dns ad bloking) work

[javierspn]

Hi! First and foremost, congratulations for the project!

I intend to use it for my homelab but I am pretty unsure on how blocky is integrated here. My plan is to use this on containers.

The thing is I have read the documentation and it is unclear (maybe I am dense) on how the ad blocking works.

I see that there are Zone handlers and I get that once a DNS request is received, the order configured on the zone are queried in order:

- cache_ttl: "3600"
  to: 8.8.8.8:53
  type: forward_blocky
- to: 8.8.8.8:53
  type: forward_ip

Let's say I have a Gravity server with IP 10.10.10.10 and a client. I have a single DNS record on a sigle zone there : server.lan --> 10.10.10.110.

1. Query one: adservices.google.com

Gravity server receives the query and first it checks on blocky if it is part of the list of ad domains and blocks it.

2. Query two: server.lan

Gravity server receives the query and first it checks on blocky if it is part of the list of ad domains. As it is not blocked, neither is an external domain resolution, it replies with server.lan --> 10.10.10.110

Is my assumption right?

Sorry to bother you all with such a simple question but as said it is not clear for me within the documentation. Probably some of you have already a similar setup...

I

[BeryJu]

The assumption is mostly light, however the blocky handler does both parts, i.e. it will automatically resolve the query with whatever is set in to if its not blocked

For the second scenario, this will happen if the zone has an etcd handler, which uses the records created in gravity as a database to resolve from