2017-01-11 13:02:45 -07:00
---
name: TTL
parameters:
- ttl
2023-01-12 16:59:42 -05:00
parameter_types:
ttl: Duration
2017-01-11 13:02:45 -07:00
---
TTL sets the TTL for a single record only. This will take precedence
2023-01-20 13:56:20 +01:00
over the domain's [DefaultTTL ](../domain/DefaultTTL.md ) if supplied.
2017-01-11 13:02:45 -07:00
2017-06-08 13:44:37 -04:00
The value can be:
* An integer (number of seconds). Example: `600`
* A string: Integer with single-letter unit: Example: `5m`
* The unit denotes:
* s (seconds)
* m (minutes)
* h (hours)
* d (days)
* w (weeks)
* n (nonths) (30 days in a nonth)
* y (years) (If you set a TTL to a year, we assume you also do crossword puzzles in pen. Show off!)
* If no unit is specified, the default is seconds.
2017-06-08 14:14:46 -04:00
* We highly recommend using units instead of the number of seconds. Would your coworkers understand your intention better if you wrote `14400` or `'4h'` ?
2017-06-08 13:44:37 -04:00
2023-03-13 21:30:21 +01:00
{% code title="dnsconfig.js" %}
2023-01-20 13:56:20 +01:00
```javascript
2023-06-18 05:35:13 +02:00
D("example.com", REG_MY_PROVIDER, DnsProvider(DSP_MY_PROVIDER),
2017-01-11 13:02:45 -07:00
DefaultTTL(2000),
2023-05-24 22:09:22 +02:00
A("@","1.2.3.4"), // uses default
A("foo", "2.3.4.5", TTL(500)), // overrides default
A("demo1", "3.4.5.11", TTL("5d")), // 5 days
A("demo2", "3.4.5.12", TTL("5w")), // 5 weeks
2017-01-11 13:02:45 -07:00
);
2022-02-17 18:22:31 +01:00
```
2023-03-13 21:30:21 +01:00
{% endcode %}