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.
You may recall in my post Azure: Trigger a WebJob with Logic Apps and Kudu - Part 2 a couple of months ago, I provided a guide on how to run a webjob when a Kudu deployment completes in an App Service WebApp - pulling secrets/credentials out of KeyVault...
In my last post, Azure Functions - Securing resources with a function proxy, I talked about my work to develop a more Azure-centric solution to replace my current home security camera automation workflow.
Another link in the chain for me was to be able to ser...
In my last post, Azure: Trigger a WebJob with Logic Apps and Kudu - Part 2, I used a Logic App run a WebJob using the Kudu REST API on a schedule, retrieving the necessary credentials from the KeyVault
The main idea of a Logic App is that you don’t need...