It’s always DNS, right? But what would happen in a world where DNS had better management, better reporting, and you had more control over things? How would it look then? What if it’s not always DNS?
In this iteration of Gestalt Networking News:
– Monitoring Network Flows with Plixer
– The best of both worlds with Array Networks’ Flexible NFV
– A deep dive into Aruba’s new 8400 series switch
Plus Network Collective digs into networking history with Fred Baker!
Mark Henderson, a site engineer for Stack Overflow, walks through how the site picked their DNS provider. The site previously bounced between on-premises BIND servers and DNS services offered through Cloudflare. In light of the Dyn DDoS attack, the site wanted more robust protection from a future outage.
John Herbert from Lame Journal comments: Earlier today on Twitter, Tom Hollingsworth (@networkingnerd) raised the subject of naming conventions. He’s right that having something in the device name that clues you in to where it’s located is really helpful when you’re troubleshooting. But wait, that’s a a form of information disclosure, and some evil h4x0r […]