Self-Hosting DNS
ghostdev.xyz
Self-Hosting DNS
1–10 of 72 posts
Re: Self-Hosting DNS
#2My journey of DNS, including self-hosting with Pi-hole and AdGuard Home, using paid services like NextDNS and AdGuard DNS, and public privacy-respecting resolvers.
Re: Self-Hosting DNS
#3I also want to selfhost variosu servers like dns, email(just to send email to myself).....ldap, dhcp etc. Where do I get started with? I know linux command line.
Re: Self-Hosting DNS
#4I also want to selfhost variosu servers like dns, email(just to send email to myself).....ldap, dhcp etc. Where do I get started with? I know linux command line.
r/selfhosted on reddit has a very helpful community.
DNS is very easy. Email is tough. Usually one would add a media server such as Plex and Nextcloud which is very useful.
Re: Self-Hosting DNS
#5Why 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.
Re: Self-Hosting DNS
#6>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?
Re: Self-Hosting DNS
#7>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 :-|
Re: Self-Hosting DNS
#8Why 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
Re: Self-Hosting DNS
#9Why 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
Use the root servers to find the dns entries yourself, just like the upstream provider does
Re: Self-Hosting DNS
#10Why 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's called a dns-resolver (iterator). essentially starting from the top (.) and asking for authorative nameservers that can answer the next level down until it reaches the hostname you are looking for. this usually takes multiple rtt's and is hence slower than asking some big cache.