-
Notifications
You must be signed in to change notification settings - Fork 555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNS replace records by criteria #298
Comments
Definitely have a look at what we did on gcloud-node for this, it was a bit |
@jgeewax is that discussion somewhere we can see it? I didn't find many DNS issues on gcloud-node. But I may be poor at searching for it... |
@stephenplusplus - do you recall where we had the debate about replacing |
There is some discussion here: googleapis/google-cloud-node#706. Specifically, here: googleapis/google-cloud-node#706 (diff) |
@jgeewax Is this likely to be the concern you meant to point us to?
In that case, point taken: Be sure to fetch all matching records before making the call to replace. |
I don't think there was much of a discussion about it. I just did it and you said something like "this is cool, just make sure you mention it's not atomic." Here it is: googleapis/google-cloud-node#706 (comment) |
Thanks @stephenplusplus |
@stephenplusplus @callmehiphop Hey guys, can you give us some background on the use case for |
My only direct experience with records has been pretty simplistic: updating the nameservers for my domains. When I was playing with the API while developing, I wanted to see how easy that would be, which is how I ended up with removing the records by type. Was it a bad idea? |
No, not at all! :) We were just curious where it came from. We are thinking about an option to auto-update the SOA record when changes are made, and we were curious where |
I've spent a fair amount of time looking into managing DNS records and how Google Cloud DNS behaves. My thinking has changed from the time this issue was first created. Google Cloud DNS does not allow multiple records to exist for a zone.replace "example.net.", "A", 18600, ["127.0.0.1"] |
Our intention is to allow multiple replacement calls within a single change request using zone.update do
replace "example.net.", "A", 18600, ["127.0.0.1"]
replace "www.example.net.", "A", 18600, ["127.0.0.1"]
replace "mail.example.net.", "A", 18600, ["127.0.0.1"]
replace "example.net.", "MX", 18600, ["10 mail.example.net",
"20 mail.example.com"]
end |
Replace existing record with the new record provided. [refs googleapis#298]
Instead of specifying the records that need to be deleted, allow users to specify the types of records to be removed and replaced.
Update: The example code should be:
See the discussion below about this.
The text was updated successfully, but these errors were encountered: