Launching a new website requires ensuring that domain names correctly point to web servers. This article outlines the basic steps for configuring DNS records, helping you understand what information is needed and how to manage these settings effectively.

Preparing for Your First DNS Configuration

As a hypothetical example, imagine an author planning a simple setup worksheet for a fictional site called “lantern-journal” under the example suffix “.test.” The worksheet is meant to be filled in before the site launch, so the fields are deliberately concrete: record type, host, target, and purpose. Two fictitious rows might look like this. For the main site, type A, host “@”, target “192.0.2.10”, purpose “web server address.” For the short public address, type CNAME, host “www”, target “lantern-journal.test”, purpose “alternate host name.” A third row could be type MX, host “@”, target “mail.example.test”, purpose “incoming mail,” with a separate numeric priority note.

The author also needs a few naming candidates for the worksheet itself. One could be “Lantern Journal DNS Launch Sheet,” another “Site Address Record Checklist,” and a third “New Website DNS Worksheet.” In this example, the author picks the first because it names the project and the task without implying that the DNS settings are already active. That is a judgment about clarity, not evidence that anyone has used the form.

For the worksheet’s heading row, the author writes “Record type,” “Host or name,” “Value or target,” “TTL,” and “Notes.” A sample entry for the mail row might put “3600” in the TTL column and “confirm with mail host” in Notes. The author also adds a small legend explaining that “@” means the root of the chosen name and that “www” is a separate host label. These are self-invented explanatory examples, not a report of a past setup or a verified service.

When the author chooses between an A row and a CNAME row for the site’s main address, the example keeps the A row at the root and reserves the CNAME for the alternate host. The stated reason is that the worksheet separates the server address from the alias, making the two rows easier to review later. No success or outside confirmation is assumed.

Understanding Core Record Fields: Name, Type, and Value

In Amazon Route 53 , each record in a hosted zone carries a name, a type, and a value. The name corresponds to the domain name (example.com) or subdomain name (www.example.com or retail.example.com) that traffic should be routed for, and every record name in a hosted zone must end with the hosted zone's name. The type usually determines the resource traffic is routed to: MX routes traffic to an email server, and A routes traffic to a web server with an IPv4 address. Value is closely tied to type—MX takes the names of one or more email servers, while A takes an IPv4 address such as 192.0.2.136.1

For the next step, the author can take the worksheet’s three core columns — name, type, and value — and test each example row against the actual question it answers. Consider the mail row already drafted: the author might ask whether the name field really identifies only the part before the suffix, whether the type says which kind of record is being described, and whether the value reads as a destination rather than a label. If the value cell holds a note like “points to the hosting server,” it could be rewritten as a concrete target such as the server address the page itself provides, so the row distinguishes a description from an entry.

The author can then try the same three-field review on the root row and the alternative-name row, writing a short candidate comparison beside each. One candidate might read: name “blank or root,” type “A,” value “server address from the setup page”; a second might read: name “www,” type “CNAME,” value “the root name.” The author could mark which candidate they would keep for a first pass and add one sentence of reasoning, such as “keeps the root direct and the alternate pointed at it.” This remains a hypothetical editorial exercise, not a claim about how any resolver behaves.

Before finalizing the sheet, the author might add a small self-check column headed “What question does this row answer?” and fill it with plain questions, then decide whether each row still earns its place. If a row cannot be tied to a concrete choice the author is preparing to make, it can be moved to a separate notes area rather than presented as part of the launch sheet.

Selecting the Right Routing Policy for Simple Records

For simple records in Amazon Route 53 , the documentation lists values specific to simple records and, separately, values specific for simple alias records. These are distinct topics in the same guide. The page states that the values you specify when creating or editing records depend on the routing policy you want to use and on whether the records are alias records. Alias records route traffic to specified AWS resources such as Elastic Load Balancing, a CloudFront distribution, or an Amazon S3 bucket. You can optionally associate health checks and configure target health evaluation. The guide directs readers to the relevant topic for the values required by each routing policy and record type.2

You can treat the routing-policy question as a note to add beside each simple row on your own worksheet, not as a setting you need to resolve before you begin. For the fictional lantern-journal sheet, the author might write “routing policy” in a spare column and fill it with plain questions rather than technical verdicts: “Does this row send visitors to one address, or does it hand off to another name?” and “If two addresses are listed, how would the site owner choose between them?”

The author can then sort the existing sample rows by those questions. The root A row and the alternative-name CNAME row each answer a different question, so the author might mark them as separate cases and leave a blank cell where no simple answer applies. Working from the same entries as before, consider adding a second sample line only when the worksheet already has a genuine need for it, such as a row whose purpose is staying flexible rather than fixed.

Before adding any such row, you might read the note aloud and ask whether it describes a choice the site owner can actually make with the information already on the sheet. If the answer stays hypothetical, the author can keep the cell empty and record the open question in the notes column instead. This keeps the routing column a place for your own deciding, not a finished answer.

Step-by-Step Guide to Creating a New DNS Record

In the Cloudflare dashboard, the documented flow for a new record is to open the DNS Records page, select Add record, and choose a record Type. The required fields vary by record type; the source highlights Proxy status for A, AAAA, and CNAME records, the TTL field controlling record validity and propagation time, and Comment and Tag as reference attributes. After completing the fields, select Save.3

For API-based creation, the source specifies a POST request, with field definitions available under the request body specification for each record type.3

For the next addition to your worksheet, you can take one simple row you have already drafted—say the root A entry for a hypothetical site—and copy it without touching its type, host, or value. Then write a single new field beside it headed “Works with existing draft?” and fill it with a plain answer, such as “Yes—same root name and same target.” The example value matters less than the fact that you are comparing a proposed change against a named row rather than starting over. You might also try a second candidate field headed “What stays fixed?” and note “root host and type” for that row, then “nothing yet” for a mail row you haven’t checked.

You can repeat this for one archived entry if your worksheet includes one, using the same two field names and writing “reference only” under the fixed field. Keeping the field headings identical lets you read current and archived rows side by side without treating them as equivalent. Consider pausing after two rows; the purpose is to make your own comparison visible, not to complete the sheet in one sitting.

Editing and Deleting Existing DNS Entries Safely

In the Cloudflare dashboard, go to the DNS Records page, then Records. To edit a record, select Edit on that specific record, make the necessary changes, and select Save. To delete a record, select Edit on it, then Delete, and select Delete again to confirm. For API changes, a PATCH request updates part of a record, a PUT request overwrites the entire existing record, and a DELETE request deletes records.3

If your domain was added to Cloudflare by a hosting partner, the page states that you manage DNS records through that hosting partner.3

For the existing row you already drafted on your worksheet, you can add a before-and-after pair to make the edit visible. Suppose the sample root row reads “www, A, old-server-value, 3600, points to first host.” You might write a revised line beneath it as “www, A, new-server-value, 3600, repointed for launch,” then note which single field changed and which fields you deliberately left alone. That keeps the edit traceable without turning the sheet into a log.

A deletion example can sit beside it. For an outdated test row, you could mark “staging, A, retired-value, 3600, superseded” and add a short line saying what you checked before removing it: whether another row already covers that name, and whether the row appears in your archived notes. If you keep an archived entry for comparison, use the same two field labels — name and value — and write “reference only” under the fixed field, so current and retired entries remain distinguishable on the page.

You might also try a three-question review for each planned change: which name, which type, and what proves the replacement is correct. Your answers can stay in your own words. When a row fails that review, leaving it in place until you can answer may be the safer choice for your worksheet.

Verifying Traffic Flow After Configuration

After you configure Amazon Route 53 to route traffic to resources such as web servers or Amazon S3 buckets, the documentation describes what happens when someone requests www.example.com. The browser request goes to a DNS resolver, typically managed by the user's ISP. The resolver forwards it to a DNS root name server, then to a TLD name server for .com domains, which responds with the names of the four Route 53 name servers associated with the example.com domain. The resolver caches those name servers, typically for two days, so later browses to example.com skip those steps. The resolver then chooses a Route 53 name server, which looks in the example.com hosted zone for the www.example.com record and returns the associated value, such as the IP address 192.0.2.44. The resolver returns that value to the browser, which sends its request to that IP address; the web server or other resource there returns the page. The resolver also caches the IP address for a time you specify as TTL.1

After you finish a configuration worksheet, you can add a verification column that records what you plan to observe once the site is live. For a fictional root entry such as “www, A, planned-value, 3600, main address,” you might write “page loads at the main address” as the expected result, then note where you would look: the address bar, the page body, or a saved note about which path you requested. This keeps the row about your own material rather than a promise about outside systems.

You can also prepare a small comparison between the main address and an alternative name. If your sheet lists “www” beside a root entry, write one line for each describing which address you would type and what you expect to see, such as the same page title but a different host portion. Mark any entry you cannot yet explain as “unresolved” rather than guessing.

For a row you later revise, keep a short before-and-after note. Suppose the value changes from “old-target” to “new-target”; beside it you might write “replaced because the earlier target belonged to a retired draft.” If you include an archived row, label it “reference only” and leave its value unchanged.

Frequently asked questions

What could I name my own worksheet for planning a site launch?

The author also needs a few naming candidates for the worksheet itself. One could be “Lantern Journal DNS Launch Sheet,” another “Site Address Record Checklist,” and a third “New Website DNS Worksheet.”

How can I review each drafted example row using my worksheet's name, type, and value columns?

For the next step, the author can take the worksheet’s three core columns — name, type, and value — and test each example row against the actual question it answers. Consider the mail row already drafted: the author might ask whether the name field really identifies only the part before the suffix, whether the type says which kind of record is being described, and whether the value reads as a destination rather than a label.

What column can I add to a drafted simple row and what heading should it have?

For the next addition to your worksheet, you can take one simple row you have already drafted—say the root A entry for a hypothetical site—and copy it without touching its type, host, or value. Then write a single new field beside it headed “Works with existing draft?”