• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Dynamic DNS

If you use the Dynamic DNS connection for private transfers. I.e. it is not a Site/Server for the public. You might want to secure the propagation of your External IP.

It does not secure your Internet connection per-se just, the transmission of you External IP to the DNS server.

:sun:
 
If you're talking about AD DNS/DHCP, I think you need Windows in order for secure updates to work properly. If you have non-Windows DHCP clients you'd have to enable non-secure updates for them to be able to update the DNS zones. Of course, IMO, it makes more sense to just have the DHCP server update DNS and not let any of the clients touch the DNS zones.
 
Yes it is a windows 2003 enviornment & the DCHP clients are all running windows. I just wanted to make sure, before I switch to "secure only" there was no logical reason to include the "non-secure" option.

Thanks
 
Back
Top