Windows Home Server Dynamic DNS Update

Microsoft just passed along some information that next week on January 11th, there will be an outage of the service that powers *.homeserver.com and *.remotewebaccess.com domain names. If you are a Windows Home Server or Windows Small Business Server user and are using a remote access domain name in one of those two categories, there is a chance that you will be affected.

This outage is taking place to migrate the service from the Windows Live Custom Domains platform to the Azure platform. By moving to Azure, stability and performance will be improved, and will lay the groundwork to support the new Windows Server Solutions products (Vail, Aurora, and SBS2011) being released later this year.

The outage will last approximately 24 hours and during this outage no updates will be able to be performed. What this means is that if your IP address changes during the downtime, your server will be unavailable until the outage is cleared. What this also means is that if you want to change your domain name or release your domain name, you will be unable to do so.

Also, you may see alerts stating that your server was unable to update your domain name, and any 3rd-party add-ins that rely on the remote access services may fail.

Not to worry however, when service is restored your server will automatically update the remote access configuration, alerts will disappear, and remote clients will be able to connect once more.

If after the update, in the rare case that your domain name is not working, follow these steps to correct your configuration.

1. Open the Windows Home Server Console

2. Click on Settings

3. Select the Remote Access item in the Settings page

4. Click Repair and follow the instructions on the screen

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: