Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Deletion by nsupdate relies on a kludge to specify the RRSet TTL #4

Open
GoogleCodeExporter opened this issue Nov 13, 2015 · 0 comments
Open

Deletion by nsupdate relies on a kludge to specify the RRSet TTL #4

GoogleCodeExporter opened this issue Nov 13, 2015 · 0 comments
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

Route 53 require the RRSet TTL to be specified in a Change API request but the 
dynamic update protocol means the TTL arrives from the client set to zero. At 
the moment an override TTL is set in the route53d config file.

Need to query the Route 53 API, or do a DNS query, to learn the true TTL and 
remove the config kludge.

Original issue reported on code.google.com by [email protected] on 3 Mar 2012 at 4:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter