Live data from Hacker News

Self-Hosting DNS

ghostdev.xyz

21–30 of 72 posts

Re: Self-Hosting DNS

#21

>I wanted to be able to access it with a static IP, and I don’t feel like calling my ISP to get one. Not "feeling like" calling your ISP to get a static IP, but also wanting to self-host?

I don't think calling the ISP was actually what they didn't feel like doing. It is more the call itself. Being put on queue with wait music, dealing with first line customer support who have no clue what you are asking, waiting to be connected to the right support, being connected to the wrong support, being put on hold again, suddenly being hung up on, rinse, repeat.

Which is a whole different type of mental challenge compared to figuring out the technical details of self hosting something ;)

Re: Self-Hosting DNS

#22

this seems like a massively overcomplicated exercise. dns-blocking is evil, no matter who does it. stop lying to yourself and install contentblocker on your devices

> dns-blocking is evil, no matter who does it.

You really ought to expand on that line of reasoning in order to get anyone to take this comment seriously.

Re: Self-Hosting DNS

#23
post #18

DNS resolver , which it is deeply silly to not include in the title.

Agree. Title got me hoping for a description of reasonably-solved public zones self-hosting. The actual content is not interesting to me, and reads like an ad for something called AdGuard (I use unbound for most of this).

same here, bait title as it is

Re: Self-Hosting DNS

#24
post #21

>I wanted to be able to access it with a static IP, and I don’t feel like calling my ISP to get one. Not "feeling like" calling your ISP to get a static IP, but also wanting to self-host?

I don't think calling the ISP was actually what they didn't feel like doing. It is more the call itself. Being put on queue with wait music, dealing with first line customer support who have no clue what you are asking, waiting to be connected to the right support, being connected to the wrong support, being put on hold again, suddenly being hung up on, rinse, repeat. Which is a whole different type of mental challen…

especially challenging for introverts

Re: Self-Hosting DNS

#25

Why forward requests to a DNS server like 1.1.1.1 at all? I used to use stuff like pi-hole/dnsmasq, but now I'm using unbound on my opnsense router which supports using blocklists and custom overrides (as well as automatic for DHCP clients). I found the default blocklists in pi-hole broke a few things but not had any problems with the lists I'm using now.

You have to forward requests that aren't in your cache, surely? I don't see how you would resolve public domain names otherwise

That would be a 'recursive resolver'[0], which recursively queries the DNS hierarchy from the top, returns the requested DNS record, and (unless you configure it not to do so) caches the results.

They're easy to set up and unless you're using it to support thousands of DNS requests per second, it's not appreciably (on human scales) slower than forwarding requests to your ISP's servers and/or 8.8.8.8 or 1.1.1.1.

More detail about recursive resolvers and how they work can be found here[1]

[0] https://notes.networklessons.com/dns-recursive-resolver

[1] https://www.akamai.com/glossary/what-is-recursive-dns

Re: Self-Hosting DNS

#27
post #21

>I wanted to be able to access it with a static IP, and I don’t feel like calling my ISP to get one. Not "feeling like" calling your ISP to get a static IP, but also wanting to self-host?

I don't think calling the ISP was actually what they didn't feel like doing. It is more the call itself. Being put on queue with wait music, dealing with first line customer support who have no clue what you are asking, waiting to be connected to the right support, being connected to the wrong support, being put on hold again, suddenly being hung up on, rinse, repeat. Which is a whole different type of mental challen…

Although it is a fairly standard ask. It is something which the ISPs I know would have configurable in the web portal.

I tested with 2 ISPs I use and both have it as a prominent add on that you can add for extra cost per month in the UI.

Re: Self-Hosting DNS

#28

this seems like a massively overcomplicated exercise. dns-blocking is evil, no matter who does it. stop lying to yourself and install contentblocker on your devices

DNS is a kind of content. You seem to be quibbling over semantic technicalities.

not really.

it's about the blocking occurring in reach of the user (client) or not (infrastructure quirk that has to be worked around)

Re: Self-Hosting DNS

#29
post #22

this seems like a massively overcomplicated exercise. dns-blocking is evil, no matter who does it. stop lying to yourself and install contentblocker on your devices

> dns-blocking is evil, no matter who does it. You really ought to expand on that line of reasoning in order to get anyone to take this comment seriously.

see my other comment itt

more or less about trustworthy infrastructure

Post reply on HN