wiki.getshifting.com

--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools


r53multipletxtrecords

How to add Multiple TXT Records for a Domain in Route 53

Summary: This wiki page explains how to add multiple TXT records for a domain in AWS Route 53.
Date: 6 August 2025

,

Route 53 is the Domain Name System (DNS) service for AWS. It allows you to manage DNS records for your domains, including TXT records. This page will guide you through the process of adding multiple TXT records for a domain in Route 53, as the way to do this is not immediately obvious.

Adding Multiple TXT Records

To add multiple TXT records for a domain in Route 53, follow these steps, which assume you already have at least one TXT record set up:

  • From the AWS Route 53 management console, navigate to the Hosted zones section.
  • Select the hosted zone for your domain.
  • Select the existing TXT record, this will show the record details on the right side.
  • Click on the Edit record button to modify the record.
  • In the Value field, you can add multiple TXT records by separating them with a newline. Each TXT record should be enclosed in double quotes. For example:
    "v=spf1 include:spf.protection.outlook.com -all"
    "google-site-verification=n6Vz0769Rh7FITR9InI3f-FKzEYw4Q4bV6uapIGOIO8"
  • After adding the desired TXT records, click on the Save button.

In the list of records, you'll still see only one TXT record, but it will contain multiple values:

List of DNS records with just 1 TXT record


Route 53 will handle these as separate TXT records when queried:

Queried DNS records with 2 TXT records


r53multipletxtrecords.txt · Last modified: by sjoerd

Exception: Git command failed to perform periodic pull: From https://dev.azure.com/getshiftingcom/Documentation/_git/knowledge * branch main -> FETCH_HEAD fatal

Exception: Git command failed to perform periodic pull: From https://dev.azure.com/getshiftingcom/Documentation/_git/knowledge * branch main -> FETCH_HEAD fatal

An unforeseen error has occured. This is most likely a bug somewhere. It might be a problem in the gitbacked plugin.

More info has been written to the DokuWiki error log.