- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers - Netservers
- >
- MicroServer Gen 8 Sudden DNS loss 2016
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2017 11:03 AM
10-20-2017 11:03 AM
MicroServer Gen 8 Sudden DNS loss 2016
We recently purchased 35 Microserver Gen 8 computers and installed Server 2016 on them. Each week, around 5 of them suddenly lose the ability to communicate with DNS. I can ping any address (getting replies) and use Internet Explorer to conect to http://x.x.x.x by ip address. But I cannot use NSlookup to find the domain or any address nor ping by FQDN.
Using restart-netadapter restores functionality for a time and so does a restart.
The DNS service is running and restarting it doesn't help.
I recently ran HPSUM to update the network driver on all the servers but it didn't help. Broadcom NetXtreme 17.4.0.0 is the current driver.
These servers run DFS replacation as their primary role as well as SCCM Distribution Points.
Any other suggestions to try?