# update_dns_record

> Change the value, TTL or priority of one existing DNS record, addressed by `record_id`.

- Tier: W
- Required scope: write:dns
- Annotations: idempotentHint
- Docs: https://api.inleed.com/tools/update-dns-record

## Description

Change the value, TTL or priority of one existing DNS record, addressed by `record_id`. Only the fields you send change — omit `value`/`ttl`/`priority` to leave them as they are. For MX put the exchange host in `value` and the preference in `priority`. The `record_id` is derived from the record's content, so a successful update changes it — the response returns the new `record.id`; use that for any following `delete_dns_record`, never the pre-update id.

## Input schema

- `input` — string (required). A domain, email address, website URL, numeric service id, or hosting-account username the customer actually owns. Resolved to the owning account automatically; the resolved target is echoed back in the response.
- `record_id` — string (required). The record id from list_dns_records → data[].id (e.g. rec_0a1b2c3d4e5f6a7b).
- `value` — string. New value. For MX this is the exchange host; put the preference in priority.
- `ttl` — integer. New time-to-live in seconds (60–604800). Omit to keep the current TTL. Range 60–604800.
- `priority` — integer. New MX preference (0–65535). Only for MX. Range 0–65535.

## Example call

```json
{
  "name": "update_dns_record",
  "arguments": {
    "input": "example.se",
    "record_id": "rec_01hx8n3k5p7q9r2s4t6v8w0y65"
  }
}
```