Assigned
Status Update
Comments
mo...@google.com <mo...@google.com> #2
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best Regards,
Josh Moyer
Google Cloud Platform Support
Best Regards,
Josh Moyer
Google Cloud Platform Support
an...@futurefore.com <an...@futurefore.com> #3
[Comment deleted]
[Deleted User] <[Deleted User]> #4
Guys, nothing on this? I have the same request.
rh...@gmail.com <rh...@gmail.com> #5
I have starred this as a WANT. There are many services that would be OK with an ephemeral IP address so long as there is a DNS entry and it's OK if it is unreachable for a few minutes when DNS updates are propagating.
er...@ziiware.com <er...@ziiware.com> #6
This would certainl;y make the ephemeral addresses much more useful, especially in Google Container Engine clusters.
aa...@gmail.com <aa...@gmail.com> #7
Hi
Is there any timeline on this?
THis issue was acknowledged in April 2014, but nothing since.
Why?
I use a virtual server with an ephemeral IP address as an occasionally-on dev server.
It needs https.
It would be good if it has a fixed 'internal DNS' name, e.g.dev-server.my-project.europe-2.google.com
Then I can make a DNS CNAME to it, i.e.dev-server.my-domain.com => ....
It also makes ssh'ing / scp'ing to it easier if it has a fixed name.
Thanks
Andrew
Is there any timeline on this?
THis issue was acknowledged in April 2014, but nothing since.
Why?
I use a virtual server with an ephemeral IP address as an occasionally-on dev server.
It needs https.
It would be good if it has a fixed 'internal DNS' name, e.g.
Then I can make a DNS CNAME to it, i.e.
It also makes ssh'ing / scp'ing to it easier if it has a fixed name.
Thanks
Andrew
yv...@gmail.com <yv...@gmail.com> #8
Totally agree, please implement such a mechanism. Would make life in the cloud much easier.
pa...@google.com <pa...@google.com> #10
This feature is available in alpha, to be considered for early testing please sign up here: https://goo.gl/efG1sK
yv...@gmail.com <yv...@gmail.com> #11
Thanks, I'll check it out.
On Mon, Feb 20, 2017 at 9:04 PM <google-compute-engine@googlecode.com>
wrote:
On Mon, Feb 20, 2017 at 9:04 PM <google-compute-engine@googlecode.com>
wrote:
ma...@gmail.com <ma...@gmail.com> #12
Has there been any update for this?
pa...@google.com <pa...@google.com> #13
Please stay tuned, we're still working on developing the relevant DNS subsystems for production-level reliability so we can move to Beta testing and then GA.
is...@google.com <is...@google.com>
md...@gmail.com <md...@gmail.com> #14
Any notices?
I'm new on GCP and need it!
I'm new on GCP and need it!
er...@ziiware.com <er...@ziiware.com> #15
You can use gcloud commands in a script to do this. The console page where you do it manually has a link at the bottom that shows you the gcloud command line. That is what we did, with ansible.
ma...@maxweisel.com <ma...@maxweisel.com> #16
Any word on this one?
ph...@battelleecology.org <ph...@battelleecology.org> #17
Any news on this?
[Deleted User] <[Deleted User]> #18
Any updates on this is much appreciated? Are there anyone really looking to this as a feature?
ma...@gmail.com <ma...@gmail.com> #19
Really needed feature
di...@siteground.com <di...@siteground.com> #20
This would be very helpful feature.
fi...@embriotech.ch <fi...@embriotech.ch> #21
Comment has been deleted.
me...@gmail.com <me...@gmail.com> #22
Still want this feature. specifically on node startup and shutdown
ke...@umich.edu <ke...@umich.edu> #23
For us, it would be nice if it wasn't just for internal DNS, but even managed DNS (Cloud DNS) that you have permission on
ra...@gmail.com <ra...@gmail.com> #24
this would be very nice indeed...
Description
1. Launch a Google Compute Engine instance
2. Wait for it to launch
3. Create a DNS record manually
What is the expected output? What do you see instead?
Expected: Not doing things manually.
Actual result: Having to do things manually.
What version of the product are you using? On what operating system?
Compute API v1, DNS API v1beta1
Please provide any additional information below.
When using ephemeral IPs for GCE instances, it would be desirable to have DNS A records automatically created in a Google Cloud DNS zone as soon as the ephemeral IP is bound to the instance. Instead, a developer must either poll the GCE API's instances.get method until the natIP field is populated, or add a startup script to the instance's image that performs a change request against the Google Cloud DNS API creating or updating the record(s) as needed.
I believe this is a common use case, wanting DNS records that map from (
Ideally a managed zone and record name would be added as an optional argument to the Compute API's instance.insert parameters.