You cannot update the name server records for a domain that has a ".no" top-level country code to use Windows Server 2008 R2-based DNS name servers

Article translations Article translations
Article ID: 2586946 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You add a domain that has a ".no" top-level country code in Microsoft Office 365.
  • You sign in to the domain management user interface of the Norid website and create the verification DNS record.

    Note Norid is the domain name registry for Norwegian top-level country codes. This includes ".no."
  • After the domain is verified, you try to update the name server records to use Office 365 DNS name servers.

    Note Office 365 DNS name servers run Windows Server 2008 R2.
In this scenario, you cannot update the name server records to use Office 365 DNS name servers.

CAUSE

This issue occurs because the Office 365 DNS name servers send Norid an authoritative response that does not include an "Authority" section. This behavior occurs when the Office 365 DNS name servers check the Start of Authority (SOA) resource record. When the WriteAuthorityNs parameter is set, the DNS server does not write name server records to the "Authority" section of a response that is returned by a plug-in.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2 or Windows Server 2008 R2 Service Pack 1 (SP1).

Additionally, you must have DNS server role installed on the computer.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.1.760 0.21xxxWindows Server 2008 R2RTMLDR
    6.1.760 1.21xxxWindows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Dns.exe6.1.7600.21062697,34401-Oct-201105:28x64
Dns.exe6.1.7601.21829697,85630-Sep-201107:52x64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_036f449bc4da0325ea4e71aed7a8b1ba_31bf3856ad364e35_6.1.7601.21829_none_c791d532d3e3640b.manifest
File versionNot Applicable
File size710
Date (UTC)01-Oct-2011
Time (UTC)12:55
File nameAmd64_4054b0647878083532b105d9e812bfed_31bf3856ad364e35_6.1.7600.21062_none_dfa944062dfea67e.manifest
File versionNot Applicable
File size710
Date (UTC)01-Oct-2011
Time (UTC)12:55
File nameAmd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.1.7600.21062_none_aa96f4820955e09a.manifest
File versionNot Applicable
File size158,131
Date (UTC)01-Oct-2011
Time (UTC)06:09
File nameAmd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.1.7601.21829_none_acafbd0206555808.manifest
File versionNot Applicable
File size158,131
Date (UTC)30-Sep-2011
Time (UTC)09:06

Properties

Article ID: 2586946 - Last Review: November 9, 2011 - Revision: 1.0
APPLIES TO
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Standard
  • Windows Web Server 2008 R2
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB2586946

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com