2017-01-12 04:02:45 +08:00
---
name: TTL
parameters:
- ttl
2023-01-13 05:59:42 +08:00
parameter_types:
ttl: Duration
2017-01-12 04:02:45 +08:00
---
TTL sets the TTL for a single record only. This will take precedence
2023-01-20 20:56:20 +08:00
over the domain's [DefaultTTL ](../domain/DefaultTTL.md ) if supplied.
2017-01-12 04:02:45 +08:00
2017-06-09 01:44:37 +08: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-09 02:14:46 +08: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-09 01:44:37 +08:00
2023-03-14 04:30:21 +08:00
{% code title="dnsconfig.js" %}
2023-01-20 20:56:20 +08:00
```javascript
2017-06-09 02:14:46 +08:00
D('example.com', REGISTRAR, DnsProvider('R53'),
2017-01-12 04:02:45 +08:00
DefaultTTL(2000),
2017-06-09 02:14:46 +08: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-12 04:02:45 +08:00
);
2022-02-18 01:22:31 +08:00
```
2023-03-14 04:30:21 +08:00
{% endcode %}