I’ve been using Hetzner for some time, but now I want to host everything myself at home.

DNS was easy with Hetzner, just point the domain to Hetzner’s nameservers, and from there to my server.

How are people doing this for home servers? When there’s not access to something like Hetzner’s nameservers.

Is there a free/cheap nameserver I can use to point at my home server’s IP?

  • thisisawayoflife@lemmy.worldEnglish
    1·
    8 months ago

    I have a pair of DO droplets doing nothing but primary/secondary chroot-bind. I have DDNS setup so my PFSense router updates the zone with the current IP address of my home setup and I handle all the DNS tasks (spf/dkim/dmarc/blah blah blah) there. I wrote a couple of scripts to handle zone signing and all that jazz so I don’t have to log in often, if ever.

    I’ll be replacing those with a modern os shortly, and probably adding recursion to them so I can use them to resolve personal DNS requests for all the machines on my domain (external and internal hosts).

    • SidewaysHighways@lemmy.worldEnglish
      1·
      8 months ago

      Fuck man, I consider myself relatively knowledgeable with this stuff and desperately want to get into self hosting more stuff, especially stuff like DNS. and your comment just shows me how much of an uphill battle I have ahead of me.

      My old gaming PC running truenas core and a few jails make me seem like a wizard to my family and stuff but I’m just a hecking n00b that’s good at following instructions.

      Where’s the guide for establishing a whole alternative Internet presence outside of the current reign of control?

      Lol I’m proud of being the same species as you guys and glad there are people out there willing to share

  • Decronym@lemmy.decronym.xyzBEnglish
    1·
    8 months ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    CF CloudFlare
    DNS Domain Name Service/System
    HTTP Hypertext Transfer Protocol, the Web
    IP Internet Protocol
    RPi Raspberry Pi brand of SBC
    SBC Single-Board Computer
    SSH Secure Shell for remote terminal access
    SSL Secure Sockets Layer, for transparent encryption
    VPN Virtual Private Network
    VPS Virtual Private Server (opposed to shared hosting)

    9 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.

    [Thread #280 for this sub, first seen 13th Nov 2023, 21:05] [FAQ] [Full list] [Contact] [Source code]

  • Oisteink@feddit.nlEnglish
    1·
    8 months ago

    Yes - I like bind9 with views so I can serve external and internal from same instance. As I only have services for my own use 1 ns on my dynamic ip is enough for my home subdomain.

    Bind9 has ok scripting possibilities with rndc and nsupdate.

  • Scrubbles@poptalk.scrubbles.techEnglish
    0·
    8 months ago

    Agree with the two so far, but to clarify how I use them.

    Cloudflare for external/public services. (Like if you run Lemmy). Use the tunnels so random people’s traffic aren’t hitting your actual IP at all, and it remains proxied through them.

    Dynamic DNS if you have an ISP that will change your IP on you randomly. Personally I use namecheap, and they have an API to update when the IP changes. I use pfsense which has a dynamic dns plugin which will update my IP if it changes.

    • PeachMan@lemmy.worldEnglish
      1·
      7 months ago

      I thought CloudFlare tunnels handled the non-static IP part, so DDNS shouldn’t be necessary? I have a tunnel running on an RPi and I THINK it’s going to update the IP that CF has if/when my ISP changes it… I guess I’ll find out! 😆

      • Scrubbles@poptalk.scrubbles.techEnglish
        0·
        8 months ago

        There might be a service in cloudflare that does that - but I’m not aware of it. DNS in cloudflare requires an IP to proxy to, and you would need something (hosted by cloudflare on your rpi theoretically) that then would notify cloudflare that your IP has changed - otherwise cloudflare won’t know where it’s proxying from.

        Cloudflare isn’t DNS, it’s a proxy that sits in the middle. (Okay it also does DNS, but I mean it’s not just routing traffic). Essentiall all cloudflare does is

        • User queries DNS for yourdomain.com
        • DNS returns cloudflare’s IP address
        • Cloudflare sees the request, and then asks your server’s IP address for the data
        • Once cloudflare receives the data from your server, it will pass it up to the user.

        I’m simplifying a lot but that’s the gist. But if your IP changes then cloudflare doesn’t know where to get your data.