I wouldn’t want to host anything on Windows unless you have to, or you want to learn more about Active Directory / Exchange / etc to help with a day job (assuming your day job is sysadmin / IT). Even then I’d do that inside Windows VMs on a Linux / ESXi host.

I personally wouldn’t (and don’t) host authoritative servers externally to the internet. I do split-horizon DNS, so that my internal BIND server handles my LAN, but I have outside DNS handled by someone that has an ACME (Let’s Encrypt) module, so that I can do wildcart certs.

One thing to look into as you spin up services at home would be some sort of VPN like Tailscale, WireGuard, or even something like Cloudflare Tunnel so that you’re not exposing services directly to the internet if you don’t absolutely have to. I believe some of these projects/products let you specify DNS servers so that when your phone (for example) is connected to the VPN, it uses your home DNS servers instead of public ones.

Your very own self-hosting legend is about to unfold! A world of dreams and adventures with self-hosting awaits!

Windows is just flat out a bad server OS. The only thing it’s really good for is managing active directory. Every other role it could conceivably fill is done better by Linux.

In my opinion, using windows server is only a disadvantage. Linux is the preferred server OS for almost any application. You will find a larger knowledge base online for both Linux and running all that software in Linux. Windows really only has a place as an exchange server IMO, and even then you can find a better option probably.

That being said, I will also recommend Debian.

Don’t use Windows Server for homelab, I’d recommand using Proxmox and make VM and LXC, this will be way easier to backup and manage.

For DNS You should use something like PiHole, which can be setup in a small Debain LXC and works like a charm!

As others said - use Linux. It’s the defacto server operating system. Windows is clunky and cumbersome. Microsoft even made .NET work across other operating systems, making hosting .NET apps on Linux a breeze.

A super simple (and free) way of exposing your home server to the internet is to use Cloudflare tunnels. That way it doesn’t matter what your IP is, traffic is routed through Cloudflare to your server and your IP is never exposed.

Use Cloudflare for your DNS, and it will offer you additional protection on their free plan.

My opinions:

1. No, there is no advantage to Windows server; yes, you are wasting your time. Most good server stuff out there is Linux-first or Linux-only.
2. Yes. bind is the gold standard of DNS servers but can be kind of annoying and fiddly to configure. dnsmasq or coredns are excellent alternatives.

1. Go Linux. It is far superior.
2. get a domain (third level from here for free for starters) and ssl certs from lets encrypt. IP Addresses and no or self signed ssl will look super shady for any not coputer savy person and is unsafe (at least no ssl is)

The main advantage of using Linux for your homelab is that you will get a lot more support because most folks here run their homelabs on Linux, BSD, or a combination of both. I run my home lab on a combination of both. Windows Server will probably end up really frustrating you and adding additional needless expense.

For DNS, you can look into a couple of different solutions:

• PiHole
• Run just Unbound
• Run BIND

I personally just run Unbound as it works well for me. Currently, I am thinking about moving to a split-brain DNS and do away with fake .lan internal TLD that I am using, especially now that I have gotten Let’s Encrypt’s DNS-01 challenge to work properly.

Besides what everyone already said, I would emphasize docker. Just take the plunge and learn it. It will make hosting and keeping things organised much easier.

If you want to go the extra mile, you could have a look into ansible, to make your build reproducible. But it’s probably overkill for now. You’d probably take so long to get anything done that you might lose interest.

1. I’d advise using Linux instead. I don’t think I’ve seen any selfhosters/homelabs use Windows Server. I know you’ve said you wanted to use Docker but Proxmox is a good hypervisor that is used to run Linux containers and can be setup to run Docker containers as well.

2. Why do you plan to run a DNS server at home? It seems to me like your plan is to access your server from outside. For that you can use your IP address or alternatively you can lease a domain and set its DNS to your IP and use that instead. You can also use a free service like DuckDNS instead.

Definitely wouldn’t use windows server for homelabbing, instead consider some sort of Linux. For DNS I personally use pihole unbound which is pihole with unbound as an upstream dns server allowing for the best of both programs! Conveniently, this GitHub repo will allow you to easily deploy a working instance of pihole+unbound for use within your homelab.

1. Use Linux
2. It’s probably not a static-ip and I wouldn’t rely on it as such. I’d use http://www.duckdns.org/ to handle the dynamic IP issue (or something else, https://freedns.afraid.org/ would be another option)
3. I’d look to pihole to start with for DNS. It blocks ads and you can add manual DNS entries. If you need something more complex, you can always migrate to something like unbound but pihole is a good, easy start.
4. Setup https://letsencrypt.org/ You didn’t mention HTTPS/SSL, but you should really set it up. let’s encrypt makes it easy and free

I’ve been self-hosting a wide variety of things including nextcloud (which is one open source project I advocate everyone look at, especially on a web domain so they can access it from anywhere)

Go linux for hosting your open source projects. Just do it. I’m not saying that because windows is inherently worse than linux, but because everything out there is documented as if you’re hosting off of linux. In fact, you should really consider using Ubuntu-server, because most things have documentation specifically for ubuntu.

Going with windows server as mostly just s hyper-v box with your linux installations inside, that might be worthwhile.

If your IP address appears static, then you can probably just directly configure dns through the web interface of your domain provider. There’s a great script out there for doing dynamic dns using different providers such as godaddy, that could be some insurance to make sure you don’t end up with a non-working social media network.

One thing you should consider is running one virtual host as your reverse proxy that redirects different subdomains to the different individual servers running your services. The reverse proxy server running something like nginx would then deal with all your subdomains, and if you work on say your nextcloud and need to reboot it won’t take all your services down at once because your reverse proxy continues to function for all your other services.

1. As already stated, yes, you’ll make life harder, as most (probably all) instances run on Linux. More help there.
2. Bind is the reference implementation of dns, powerdns is easy as well.

With bind you can setup an internal zone on a 2nd instance so you can test before changing the external zone to point to your instances. It’s a tad extra work, but you can mess around without bothering others.

It’s not easy, but there are loads of examples online. (And once you’ve gotten used to the commandline way of administering, it’s not hard)