adapted from here.
Windows Home Server is Windows Server 2003 at its core. Most of the really cool things 2k3 can do is against the EULA. If you need Domains or load balacing, buy 2K3. But I didn’t see the harm in the small hack. If you are not comfortable with configuring Windows components, using Remote Desktop or configuring the Windows Firewall, stop here.
- RDP into the WHS.
- Click Start, point to Control Panel and choose Add or Remove Programs
- Click Add/Remove Windows Components
- Click on the words Networking Services and then click the Details button.
- Put a check in the box next to DNS and then click Next, Next…Finish.
- Close the Add or Remove Programs windos
- Click Start, point to Control Panel and choose Windows Firewall
- Click on the tab for the Exceptions page
- Click the Add Port button
- In the Name box type DNS, in the Port number box type 53, ensure TCP is selected and click OK.
- Click the Add Port button again
- In the Name box type DNS, in the Port number box type 53, ensure UDP is selected and click OK.
- Click OK to close the Windows Firewall window
- Point the DNS of whatever serves as your DHCP server to your WHS.
- Assuming your DHCP is a hardware firewall or a router provided by your ISP, point your WHS DNS to whatever you use. OPENDNS, GOOGLEDNS, whatever.
CAVEAT: The original author reconfigured the IP Configuration on his WHS so it used its own address for DNS.
Popularity: 36% [?]
