Query name minimization
One new thing you need to add your DNS security policies is "query name minimizations" (RFC 7816). I thought I'd mention it since many haven't heard about it.Right now, when DNS resolvers lookup a name like "www.example.com.", they send the entire name to the root server (like a.root-servers.net.). When it gets back the answer to the .com DNS server a.gtld-servers.net), it then resends the full "www.example.com" query to that server.
This is obviously unnecessary. The first query should be just .com. to the root server, then example.com. to the next server -- the minimal amount needed for each query, not the full query.
The reason this is important is that everyone is listening in on root name server queries. Universities and independent researchers do this to maintain the DNS system, and to track malware. Security companies do this also to track malware, bots, command-and-control channels, and so forth. The world's biggest spy agencies do this in order just to spy on people. Minimizing your queries prevents them from spying on you.
An example where this is important is that story of lookups from AlfaBank in Continue reading


The goal is to make Kubernetes more accessible to developers.
Windstream sources its SD-WAN technology from VeloCloud.
Humans will be the ‘digital conductors.’
New Relic expects to see integrations with cloud services from Azure, Google, IBM, and Pivotal.
This app-based approach could make private LTE networks more affordable.
Pulse Secure completes acquisition of Brocade assets; Riverbed releases Xirrus access point.
Legal expenses, including Cisco patent dispute, cost Arista $12 million.