Tuesday, March 19, 2024

[RESOLVED] No DNS servers could be retrieved from network adapter

Abstract: On a Microsoft Exchange 2013/2016 Server you might see the event ID 205 or 16025 (No DNS servers could be retrieved from network adapter 00000000-0000-0000-0000-000000000000) in the event log and wish to solve them.

The full message from the event log is the following:

Log Name:      Application
Source:        MSExchange Common
Date:          2016-06-02 13:44:16
Event ID:      205
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      exch02.int.contoso.com
Description:
No DNS servers could be retrieved from network adapter 00000000-0000-0000-0000-000000000000. Check if the computer is connected to a network and Get-NetworkConnectionInfo returns any results.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchange Common" />
    <EventID Qualifiers="49156">205</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-06-02T11:44:16.000000000Z" />
    <EventRecordID>467626</EventRecordID>
    <Channel>Application</Channel>
    <Computer>exch02.int.contoso.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>00000000-0000-0000-0000-000000000000</Data>
  </EventData>
</Event>

 or

Log Name:      Application
Source:        MSExchangeFrontEndTransport
Date:          2016-06-02 13:44:10
Event ID:      16025
Task Category: Configuration
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      exch02.int.contoso.com
Description:
No DNS servers could be retrieved from network adapter 00000000-0000-0000-0000-000000000000. Check if the computer is connected to a network and Get-NetworkConnectionInfo returns any results.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeFrontEndTransport" />
    <EventID Qualifiers="49156">16025</EventID>
    <Level>2</Level>
    <Task>16</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-06-02T11:44:10.000000000Z" />
    <EventRecordID>467622</EventRecordID>
    <Channel>Application</Channel>
    <Computer>exch02.int.contoso.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>00000000-0000-0000-0000-000000000000</Data>
  </EventData>
</Event>

The solution according to Microsoft Technet is the following:

Microsoft Exchange 2013/2016 required that the “Register this connection’s addresses in DNS” is checked in the NIC card option (If you use a NIC for the interside replication and another for the access, then only the NIC for the access and not the for the replication should have set that option!).

You can do that as well via Get-NetworkConnectionInfo

Note: If you enable the option this might cause the following errors in the eventlog:

The system failed to register host (A or AAAA) resource records (RRs) for network adapter

So make sure that the exchange server could register his IP on the non replication NIC in the DNS! Additional make sure that the NIC order is set correctly and that the REPLICATION NIC is not the first one!

Related Articles

1 COMMENT

  1. Making “Register this connection’s addresses in DNS” stops this event id but…
    It makes no sense requiring dns updates for this.
    So if the our dns servers do not allow dynamic updates their logs wil be full of denied updates
    on the forward and reverse zones from the Exchange server.
    If “Register this connection’s addresses in DNS” is unchecked the denied update logs stop but the
    the event id 16025 returns.
    Moral of the story.
    What do you prefer? Logs of event id 16025 or logs of denied updates?
    What a mess :-((

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Stay Connected

35FollowersFollow
- Advertisement -

Latest Articles