Solved

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

Posted on 2014-07-29
3
1,261 Views
Last Modified: 2014-11-12
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
Comment
Question by:Dimarc67
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
3 Comments
 
LVL 4

Accepted Solution

by:
Dimarc67 earned 0 total points
ID: 40228940
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
 
LVL 4

Author Closing Comment

by:Dimarc67
ID: 40228947
Issue self-resolved.
0
 
LVL 4

Author Comment

by:Dimarc67
ID: 40307805
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

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
Previously, on our Nano Server Deployment series, we've created a new nano server image and deployed it on a physical server in part 2. Now we will go through configuration.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question