Forum Discussion

devConram's avatar
devConram
Copper Contributor
Apr 25, 2022

DNS for local SOHO, ip ranges and suffixes

Setting up a local DNS on 2019 to eventually become a small AD.   IP range used is 192.168.1.1/24 and the number of devices are about 40, including phones and infrastructure and such.   I have be...
DNS
Server
suffix
devConram's avatar
devConram
Copper Contributor
Apr 25, 2022

Harm_Veenstra 

 

Thanks, well it was more or less as I thought in regards to DHCP and IP range. 

I cant really risk connectivity since I work a lot from this location and was puzzled about hardly anyone actually bothering to explain if you can use your current DHCP range, even with static addresses, for DNS. My attempts so far made me loss connection. Probably not setting right IP in forward zone.

 

The thing about .local is from here:

Do not use single-label DNS names. For more information, see Information about configuring Windows for domains with single-label DNS names (https://go.microsoft.com/fwlink/?LinkId=106631). Also, we do not recommend using unregistered suffixes, such as .local.

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc726016(v=ws.10)

 

 

Harm_Veenstra's avatar
Harm_Veenstra
MVP
Apr 25, 2022
Your DNS server (Or service if running on an appliance/router/firewall) should always be static and should be provided to clients using DHCP. You can leave it in the DHCP range if you make a reservation to prevent that the address will be assigned to a client.

And ok.. I have seen companies with a .local and it works just fine.. Not sure why you should register it, it's only used inside..

Resources