# Update Record

Replaces an existing DNS record with new data. This is a full overwrite — all required fields (host, type, answer, ttl) must be included in the request body. If you omit a field, the existing value will not be preserved and the request may fail. Use GetRecord beforehand to retrieve the current values if you intend to modify just one field. The record ID must belong to a domain you manage.

Endpoint: PUT /core/v1/domains/{domainName}/records/{id}
Version: 1.3.1
Security: BasicAuth

## Path parameters:

  - `domainName` (string, required)
    DomainName is the zone that the record belongs to.

  - `id` (integer, required)
    Unique record id. Value is ignored on Create, and must match the URI on Update.

## Request fields (application/json):

  - `answer` (string, required)
    Answer is either the IP address for A or AAAA records; the target for ANAME, CNAME, MX, or NS records; the text for TXT records.
For SRV records, answer has the following format: "{weight} {port} {target}" e.g. "1 5061 sip.example.org".

  - `fqdn` (string)
    FQDN is the Fully Qualified Domain Name. It is the combination of the host and the domain name. It always ends in a ".". FQDN is ignored in CreateRecord, specify via the Host field instead.

  - `host` (string)
    Host is the hostname relative to the zone: e.g. for a record for blog.example.org, domain would be "example.org" and host would be "blog".
An apex record would be specified by either an empty host "" or "@".
A SRV record would be specified by "_{service}._{protocol}.{host}": e.g. "_sip._tcp.phone" for _sip._tcp.phone.example.org.

  - `priority` (integer)
    Priority is only required for MX and SRV records, it is ignored for all others.

  - `ttl` (integer)
    TTL is the time this record can be cached for in seconds. name.com allows a minimum TTL of 300, or 5 minutes.

  - `type` (string, required)
    Type is one of the following: A, AAAA, ANAME, CNAME, MX, NS, SRV, or TXT.
    Enum: "A", "AAAA", "ANAME", "CNAME", "MX", "NS", "SRV", "TXT"

## Response 200 fields (application/json):

  - `answer` (string)
    Answer is either the IP address for A or AAAA records; the target for ANAME, CNAME, MX, or NS records; the text for TXT records.
For SRV records, answer has the following format: "{weight} {port} {target}" e.g. "1 5061 sip.example.org".

  - `domainName` (string)
    DomainName is the zone that the record belongs to.

  - `fqdn` (string)
    FQDN is the Fully Qualified Domain Name. It is the combination of the host and the domain name. It always ends in a ".". FQDN is ignored in CreateRecord, specify via the Host field instead.

  - `host` (string,null)
    Host is the hostname relative to the zone: e.g. for a record for blog.example.org, domain would be "example.org" and host would be "blog".
An apex record would be specified by either an empty host "" or "@".
A SRV record would be specified by "_{service}._{protocol}.{host}": e.g. "_sip._tcp.phone" for _sip._tcp.phone.example.org.

  - `id` (integer)
    Unique record id. Value is ignored on Create, and must match the URI on Update.

  - `priority` (integer)
    Priority is only required for MX and SRV records, it is ignored for all others.

  - `ttl` (integer, required)
    TTL is the time this record can be cached for in seconds. name.com allows a minimum TTL of 300, or 5 minutes.

  - `type` (string,null, required)
    Type is one of the following: A, AAAA, ANAME, CNAME, MX, NS, SRV, or TXT.

## Response 400 fields (application/json):

  - `message` (string)
    A human-readable message providing more details about the error
    Example: "Bad Request"

  - `details` (string,null)
    Additional context or information about the error
    Example: "'domainName' cannot be null"

## Response 403 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error
    Example: "Permission denied"

  - `details` (string,null)
    Additional context or information about the error
    Example: "Failed authentication"

## Response 404 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error
    Example: "Not Found"

  - `details` (string,null)
    Additional context or information about the error
    Example: "The requested domain does not exist."

## Response 415 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error
    Example: "The 'Content-Type' header must be 'application/json' for this request."

## Response 429 fields (application/json):

  - `message` (string)
    A human-readable message providing more details about the error
    Example: "Rate Limit Exceeded"

## Response 500 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error.
    Example: "Internal Server Error"

  - `details` (string,null)
    Additional context or information about the error.
    Example: "Something went wrong."