DNS resolver, which it is deeply silly to not include in the title.
Self-Hosting DNS
11–20 of 72 posts
Re: Self-Hosting DNS
#12>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 really resent having to pay $120 a year for a static IP :-|
vps with static ip will go for half of that
Re: Self-Hosting DNS
#13>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?
point your ns to CloudFlare and write a powershell script to update your AA records every 5 minutes, boom quasi static IP (from the PoV of the client anyway)
Not 99.9999% uptime obviously but good enough.
Re: Self-Hosting DNS
#14DNS resolver , which it is deeply silly to not include in the title.
technically it's a stub forwarder. so i'll let it pass
Re: Self-Hosting DNS
#15>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?
point your ns to CloudFlare and write a powershell script to update your AA records every 5 minutes, boom quasi static IP (from the PoV of the client anyway) Not 99.9999% uptime obviously but good enough.
dyndns solves some applications of static addressing but not most
Re: Self-Hosting DNS
#16Why 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
Yes but to the root servers, not to someone else's cache.
Re: Self-Hosting DNS
#17Re: Self-Hosting DNS
#18DNS 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).
Re: Self-Hosting DNS
#19this 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
Re: Self-Hosting DNS
#20this 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.