@lesbianhacker What you need is a computer (any computer, it doesn't need much in terms of resources), which a static IP address.
That's all you need really. Then you just need to read up on how it works, but it's not very complicated.
@loke Would reverse lookups stop working entirely if I didn't do that? Or could a fallback DNS server handle it?
I've used it before, but if I have to do without it I don't see it being too much of a hassle.
@lesbianhacker Well, a forward lookup simply asks the owner of the domain what the IP address is. You are the owner of the domain, so it will ask whichever DNS server you have told the registrar to use (i.e. yours).
Reverse lookups are the opposite. The DNS will ask the owner of the IP address range (i.e. your ISP) which DNS is responsible for providing the answer. Therefore you need to make sure the ISP returns the correct DNS.
If not, they'll respond themselves, which might be OK.
@loke Oh, okay. I'm only really planning to use this as a way to filter domains that I'd rather not allow my computers to connect to (certain advertising agencies, maybe Facebook eventually), and any sites I actually want to reach I'll be relying on an established DNS.
I'm not planning to allow anyone on the outside of my network to connect to the server. If my ISP does end up playing middleman I'll just have to deal with it lol
Then it's even easier. You don't have to do anything, since you just configure your local machines to connect to your DNS, and you configure it to forward any requests for unknown domain names to the upstream server.
I don't have a tutorial (because I haven't gone out and looked for one yet) but /etc/hosts doesn't let you use wildcard characters, so instead of *.facebook.* I would have to manually add each variation.
There are hundreds of them, and I'd have to make sure to update them every time a new one appeared.
functional.cafe is an instance for people interested in functional programming and languages.