KB ID 0001251
Problem
At a client this week, they were having a LOT of mail flow problems. Looking at the queue viewer, I could see that all their mail was sat in queues waiting to go into their mails stores. There was a queue for each mail store, and the error on each was “451 4.4.0 DNS query failed Exchange Server error in message queue“. Looking in the Application log it was full of Event ID 205, and 16025 Errors Stating;
Source MSExchange Common
No DNS servers could be retrieved from network adapter {GUID} Check that the computer is connected to a network and that the Get-NetworkConnectionInfo cmdlet returns results.
OR
No DNS servers could be retrieved from network adapter {GUID}. Verify that the computer is connected to a network and that the Get-NetworkConnectionInfo cmdlet returns results.
Solution
First you need to get the ‘Identity” of your actual network card with a Get-NetworkConnectionInfo command, (make sure the correct DNS settings are set for this NIC, i.e. it’s not pointing to a PUBLIC DNS server!) Once you have it, change the Transport service to use this new ID, with a Set-TransportServer command.
Then Restart the Microsoft Exchange Transport Service and the Microsoft Exchange Mailbox Transport Service.
Related Articles, References, Credits, or External Links
NA
31/05/2017
Brilliant – you’re a life saver. This affected me after a change of NICs on a VMWare server from E1000 to VMXNET3. Exchange 2016 on Server 2016. Nothing is ever simple in Exchange, that’s for sure…
11/10/2017
You’re really a life saver. I got this problem after a exchange server recovery installation. The nic of the recovered machine got a new guid, but the transport service knows the old one.
The queue was full! After the PS cmd everything’s fine.
Thank you very, very much!
Torsten
30/10/2017
i followed the instructions, but got this error
WARNING: The command completed successfully but no settings of ” have been modified.
it didn’t take, because after reboot, i’m still getting the error.
what are the troubleshooting steps i should do next?
05/06/2018
Lifesaver! Like Rob above I rolled by my vmware tools and vmxnet3 driver to see if it would resolve some Exchange/Outlook latency issues and it killed delivery of my emails to mailboxes – the queues had DNS errors. fixed using your solution in 1 minute.
Lesson learnt: changing the vmtools/vmxnet3 driver results in the old NIC GUID hanging around – use this fix to resolve it 😉
Cheers 😉
15/06/2019
It worked for me but there is a typo. M is written instead of N.
InternalDMSAdapterGUID should be InternalDNSAdapterGUID
Thanks,
18/06/2019
Well Spotted – ThanQ
P
07/08/2019
Thanks Pete!
Same issue, reinstall of vmware tools and different GUIDs after that.
The mail server started delivering again after the procedure.
26/03/2020
This is helped me get mail flowing at the school I work at. Thank you so much!
05/04/2020
Thank you!! 🙂
04/05/2020
Sadly, did not work for me. Even after doing this the server throws the same errors.
18/11/2020
Awesome! Worked like a charm!
21/11/2020
Worked like a charm!
27/12/2020
merci et 10000000 merci
25/11/2022
Thank you, this was a great help!
03/03/2023
You are a godsend! After either a Windows update or a Plex update (they occurred at the same time) my physical host rebooted–but the system picked up an old SYSTEM partition on a backup RAID set and chose that as C: and reset my actual System C: drive to H:–and bricked the whole network. One restore from backup later, the Exchange VM messed up badly and wouldn’t load EMS or EMC! Restored the VHDX files from a backup 1 day hence and recreated the VM successfully, but no mail was flowing: inbound, outbound, internal, nothing – though Outlook and OWA worked perfectly.
You nailed it: the transport services were still linked to the old Virtual NIC (which didn’t exist) and so all mail sat in the queues. Until I found this page. Followed instructions and in less than a minute mail was flowing normally again! HALLELUJIA!
Many, many thanks kind stranger! Have all my gold!
03/03/2023
🙂
18/12/2023
Thanks So much. We were about to failback to the old server and lose about 7 hours of work.
16/10/2024
This helped me after I did a full VM restore of Exchange 2013. Thank you!