Using Windows Server 2016 Essentials setup with the standard (Microsoft provided) <server>.remotewebaccess.com domain for remote access - for the past few days DynDNS has been failing.
Are there wider issues with supporting services?
If I try to remove the current domain so that I can setup again or setup a manual domain it prompts for my user name, checks password but then fails.
If I try to simply setup my own domain, then the request certificate process just hangs.
Are we seeing the deprecation of remotewebaccess.com and the related services, or are there just issues around it at present?