title: Run `git clone` with custom DNS?
body: <p><strong>TLDR:</strong> Is there a way to run a <code>git clone [url]</code> with the URL being temporarily hard coded for the git command only?</p>
  
  <p>I am running into a scenario where a hosted environment in the cloud (Azure, AWS, etc) can be burned down and then recreated using same name in short window of time (say within 10 minutes). This results in re-use of the DNS name (ie mycoolwebsite.azurewebsites.com).</p>
  
  <p>Inevitably a command to do a git clone/git push pointed at that DNS name results in failure since the DNS entry that is cached on the machine is now stale since the recreated environment may likely live behind a different external IP.</p>
  
  <p>Through the cloud hosting providers tooling I can query the external IP and do a injection/ejection into <code>/etc/hosts</code>. This has been a functioning workaround but its a "bad idea" for many reasons. I cannot easily point to the IP as the endpoint as the server won't respond to naked IPs, only hostnames (from what I can gather).</p>
  
  <p>I imagine this has been encountered by numerous folks turning up and burning down dev instances in the cloud - is there a better way to handle what is basically a DNS caching issue?</p>