Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1349
  • Last Modified:

How to force Microsoft Azure Cloud Service public IP to change...

I'm exploring the abilities of Microsoft Azure for hosting a web scraper.  To work-around site blocking, I'd like to be able to force the public IP address of the Azure Cloud Service to change on command.  Ideally, a script would be used to force the IP change on a regular schedule.

Azure's documentation indicates that the Cloud Service Public IP address will be re-provisioned if all of the VMs using the service are shut down.  However, when shutting down and restarting my one VM using PowerShell, I'm getting mixed results--sometimes the Cloud Service IP changes, sometimes it doesn't.  One test took 15+ minutes after the VM shutdown/restart for the IP change to register, while other identical tests showed the change within a minute, or no change at all.

Not certain if there is a time factor involved--maybe X number of seconds/minutes are needed after the VM shutdown, before the VM is restarted (along with the Cloud Service by default) for the Azure backend to register the changes?

Any insights or knowledge regarding this would be greatly appreciated.
0
Dimarc67
Asked:
Dimarc67
  • 3
1 Solution
 
Dimarc67Author Commented:
Looks like the delay inconsistency is actually caused (simply) by the Azure DNS record TTL for the cloudapp.net name of the proxy server.  If we shutdown/restart the Cloud Service, it's IP changes, but the DNS record for the name has a TTL of 1 hour, so it won't update in the DNS servers until we clear the cache.

With this information, it seems to work as designed.
0
 
Dimarc67Author Commented:
Issue self-resolved.
0
 
Dimarc67Author Commented:
By the way, our final solution was to write a PowerShell script to create a new cloud service and VM before deleting the previous service.  This forces a new IP address (since the previous IP is still in use).  Working well.
0

Featured Post

When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot has fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now