Google Compute Engine: Internal DNS server and issues with the resolving -


since google compute engine not provides internal dns created 2 centos bind machines resolving machines on gce , forward resolvings on vpn private cloud , vice versa.

as google cloud docs suggests can have kind of scenario. , edit resolv.conf on each instance resolving.

what did edit ifcg-eth0 disable peerdns , in /etc/resolv.conf added search domain , top 2 nameservrs instances.

now after 1 instance gets rebooted..it wont start again because searching metadata.google.internal domain

jul 8 10:17:14 instance-1 google: waiting metadata server, attempt 412

what best practice in kind of scenarios?

ty

also need internal dns poor's man round-robin failover, since gce not provides internal balancers.

as mentioned @ https://cloud.google.com/compute/docs/networking:

each instance's metadata server acts dns server. stores dns entries network ip addresses in local network , calls google's public dns server entries outside network. cannot configure dns server, can set own dns server if , configure instances use server instead editing /etc/resolv.conf file.

so should able use 169.254.169.254 dns server. if need define external dns entries, might cloud dns. if set domain cloud dns, or other dns provider, 169.254.169.254 resolver should find it.

if need more complex, such customer internal dns names, own bind server might best solution. make sure metadata.google.internal. resolves 169.254.169.254.


Comments

Popular posts from this blog

toolbar - How to add link to user registration inside toobar in admin joomla 3 custom component -

linux - disk space limitation when creating war file -

How to provide Authorization & Authentication using Asp.net, C#? -