DNS |
Sponsored by |
Consumption of software as a service with a usage-based business model has gained incredible popularity in recent years. On the other hand, other cloud services such as infrastructure and platform as a service are just starting to pick up. While compute and storage are by the far the most commonly used cloud infrastructure services, few consider core network services such as IP Address Management (IPAM) as something that could be utilized over the cloud.
In the first part of this trilogy, I discussed the importance of automatically provisioned second generation DNS in connection with Software Defined Networking (SDN) and Software Defined Data Centre (SDDC). In the second post, I talked about IP addressing, private enterprise networks, and how DHCP does not meet the requirements of multitenant Infrastructure-as-a-Service (IaaS) cloud environments. I will now wrap up this trilogy by putting these two thesis into real-life context.
I could have ignored yesterday's ICANN New gTLD Applicant Update Webinar and just read summaries from the usual respected news and industry sources. However, with three hours slotted and likely questions regarding ICANN CEO Fadi Chehadé's somewhat eyebrow-raising comments at the regional ICANN Registry-Registrar meeting in Amsterdam last week -- led me wanting to hear it all myself.
In part 1, I talked about some of the risks associated with BYOD. But there are actions you can take to greatly reduce this risk. One effective method for limiting the risk of BYOD is to employ DNS-based security intelligence techniques. DNS-based security intelligence makes use of an enterprise's caching DNS server to monitor and block DNS queries to known botnet command and control (C&C) domains.
In my previous post, I talked about the significance of DNS in connection with the Software Defined Data Center (SDDC) and Software Defined Networking. Although the second generation DNS provisioning model I outlined should have seemed straight-forward enough, in real life it is anything but. In my view, the real-world complications of a seemingly trivial issue are largely related to how the network industry approaches IP addressing.
The number of 'things' connected to the internet is already bypassing the number of people on the planet. This Internet of 'things' is changing the way we live and work: from the way food is grown and produced on farms through automated temperature and feeding controls, to the way we check prices and buy through connected terminals, to the vehicles we drive, the security cameras at work, and automated gates at the entrance. Connected 'things' are everywhere. All these 'things' are helping us to be more productive and efficient while also offering more and more convenience.
Ah, BYOD. How I love thee. BYOD, or "Bring Your Own Device", gives me choices. I can use a device at work I actually like and am most effective with. (How did I ever get by without my iPad?) But BYOD comes with challenges. Personal devices can be infected with malware. Once they're connected to an enterprise's network, they can be controlled by a bot master to hijack enterprise resources and wreak havoc as part of a botnet.
During 2012, Software Defined Networking (SDN) seemed to be all the rage. The VMware acquisition of Nicira during the summer doldrums for US $1.26 billion validated the fact that the SDN paradigm is expected to have some serious legs over the coming years. I guess the same applies to virtualized network services in general, although the acquisitions in that space were not quite as high-profile as the ones in SDN.
Here are the top ten most popular news, blogs, and industry updates featured on CircleID during 2012 based on the overall readership of the posts for the past 12 months. Congratulations to all the participants whose posts reached top readership and best wishes to the entire community for 2013.
It is just another phishing case. Why should I care? I happened to receive my own copy of the phishing email message. Most Internet users will just smile bitterly before deleting it. I checked it to see why it had gone through the spam filters. It had no URL in the text but a reply-to address. So it needed a valid domain name, and had one: postfinances.com. PostFinance (without trailing "s") is the payment system of the Swiss Post. It has millions of users.