BIND DNS Server on Windows

[Michael De Roover]

On Sunday, February 9, 2025 12:07:48 PM CET Richard T.A. Neal wrote:
> That's my site! 😊

That is incredible!
 
> One major drawback with WSL is that there doesn't seem to be a way to assign
> it a static IP - i.e. your WSL BIND server will change IP address every
> time (it's a private routed address that will need a Windows Firewall NAT
> rule to be reached from other machines on your network).
 
Please do note that WSL is merely a subset of Hyper-V networking, regardless 
of your Windows release. It is possible to assign bridge networking in 
Windows' virtualization suite, as well as NAT networking. Whichever one is 
chosen in the end, is an exercise left to the reader.

Either way, I have used massgrave.dev to make my Windows 10 installation 
Enterprise, and used it to create various Hyper-V machines. One of those is a 
gateway machine that connects to Hyper-V's "Default Switch", which then routes 
to another switch I was able to name "internal.switch.ideapad.lan". It goes 
without saying that this switch is internal, and therefore network-agnostic.

Lastly, there is another switch that is named external.switch.ideapad.lan. 
This is what my wired interface is bridged into. I no longer use this 
interface/switch, but it does still exist nonetheless. That allows for direct 
connections into the host network, on a switch level. However, it is only 
available for wired networking. Unfortunately, this appears to be a physical 
limit. Perhaps it's possible to mitigate this with hostapd voodoo, but I have 
yet to master that myself.

-- 
Met vriendelijke groet,
Michael De Roover

Mail: isc at nixmagic.com
Web: michael.de.roover.eu.org