Use config settings for DNS TTL values across all code

Attending to this old bug will improve our ability to perform zone comparisons between Datastore and the DNS provider. Right now, zone comparison finds some bogus differences, because the TTL we send to the DNS subsystem doesn't match the TTL we use when generating our local dump files.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=164635557
This commit is contained in:
mountford 2017-08-08 13:19:42 -07:00 committed by Ben McIlwain
parent 1ca6c95dc2
commit 2547313ef9
9 changed files with 105 additions and 63 deletions

View file

@ -286,13 +286,35 @@ public final class RegistryConfig {
}
/**
* Returns the default time to live for DNS records.
* Returns the default time to live for DNS A and AAAA records.
*
* @see google.registry.dns.writer.clouddns.CloudDnsWriter
*/
@Provides
@Config("dnsDefaultTtl")
public static Duration provideDnsDefaultTtl() {
@Config("dnsDefaultATtl")
public static Duration provideDnsDefaultATtl() {
return Duration.standardSeconds(180);
}
/**
* Returns the default time to live for DNS NS records.
*
* @see google.registry.dns.writer.clouddns.CloudDnsWriter
*/
@Provides
@Config("dnsDefaultNsTtl")
public static Duration provideDnsDefaultNsTtl() {
return Duration.standardSeconds(180);
}
/**
* Returns the default time to live for DNS DS records.
*
* @see google.registry.dns.writer.clouddns.CloudDnsWriter
*/
@Provides
@Config("dnsDefaultDsTtl")
public static Duration provideDnsDefaultDsTtl() {
return Duration.standardSeconds(180);
}