Got a website?
Secured with HTTPS and an SSL certificate?
You’d know if someone tried to register their own certificate for your domain and masquerade as you, right?
If you answered Yes, Yes and No, and you’re using Cloudflare, you can fix that at the flick of a switch (well, click of a button!).
Read on to find out how…
A few weeks ago I commented on a request from Jack Tracey for speakers at the Open Mic Night of the August 2019 Sussex Azure User Group - with the idea being to share your stories of mistakes you’ve made that have led to P1 incidents. I flippantly said I had plenty of stories but wouldn’t be able to travel down to Brighton for the meetup - and Jack asked if I could record something or do something remotely on the night.
In my last post, we created a DNS zone and added a record pointing back to the public IP address of my home broadband connection.
That’s all well and good, but since it’s not a static IP, it can of course change - so we want to be able to keep the record up to date with the current IP.
Today I’ll show you one way of doing that, using a very lightweight updater client (windows or linux) that uses an Azure PowerShell function (ok, I might be a bit of a fanboy when it comes to those!) to update the DNS record-set entry.
The more that I use Azure cloud services, the more I think of ways to use them, either to do something new, or to replace some process or service I already use.
Today, I’ll show you how you can use Azure DNS to provide a Dynamic DNS capability at significantly reduced cost compared to services like No-IP and DynDNS. A future post will automate the process of keeping the DNS entry up-to-date.