Score:0

How to resolve list of zones locally

kz flag

My goal is to use some of the rate-limited DNS BLs, on a system configured to use public DNS. Environment includes configured BIND and systemd.

Is there a way / how do I do that by using /etc/resolv.conf - /run/systemd/resolve/stub-resolv.conf? It is important that whole zone including all the subdomains is set to be resolved locally.

For example: dig xxxx.xxxx.xxxx.xxxx.zen.spamhaus.org does not work while dig @127.0.0.53 does, for the same record.

gg flag
So, essentially what you want is for your local BIND instance to respond authoritatively for the zone? That's called split-horizon DNS, essentially what you do is add a zone for the domain to your own BIND, it'll then answer queries from that zone, since in it's mind, it's the authority for that zone.
Miloš Đakonović avatar
kz flag
Thanks. But not sure I should add zone since, like in example, `dig @127.0.0.53` works. What I do not know is how to make the system to ask `127.0.0.53` when resolving a certain zones.
gg flag
Hmm, I think your issue is related to this: https://unix.stackexchange.com/questions/612416/why-does-etc-resolv-conf-point-at-127-0-0-53 Essentially, 127.0.0.53 can mean a lot of things, and it's a bit hard to tell without looking at how the system is set up.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.