title: Google Compute Engine: Internal DNS server and issues with the resolving
body: <p>Since google Compute engine does not provides internal DNS i created 2 centos bind machines which will do the resolving for the machines on GCE and forward the resolvings over vpn to my private cloud and vice versa.</p>
  
  <p>as the google cloud help docs suggests you can have this kind of scenario. and edit the resolv.conf on each instance to do the resolving.</p>
  
  <p>What i did was edit the ifcg-eth0 to disable the PEERDNS and in /etc/resolv.conf
  i added the search domain and top 2 nameservrs my instances.</p>
  
  <p>now after one instance gets rebooted..it wont start again because its searching for the metadata.google.internal domain </p>
  
  <p><em>Jul  8 10:17:14 instance-1 google: Waiting for metadata server, attempt 412</em></p>
  
  <p>What is the best practice in this kind of scenarios?</p>
  
  <p>ty</p>
  
  <p>Also i need the internal DNS for to do the poor's man round-robin failover, since GCE does not provides internal balancers.</p>