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.
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 serve up a webpage blob from my container whilst keeping the Container Access Policy set to Private.
The function proxy in the previous post enabled that, but I also then needed the webpage to be able to retrieve the video/image blobs uploaded to display them.
Today I explore using a PowerShell function in Azure Functions to automate parts of my webapp deploment.