This article outlines the basic steps for beginners launching an independent website. It covers how to search for and register a domain name through common registrar interfaces and explains the process of configuring nameservers to connect your domain to hosting services.

Assuming You Need to Launch Your First Independent Site

Suppose a first-time independent author has a plain text draft of six short product notes, one image file per note, and no hosting yet. She sketches two candidate site names. The first is “fieldnotebook” in her own notes, pairing “field” with “notebook” because the draft is a working record of small items; the second is “quietledger,” which sounds more like a store. She picks the first for the site title and keeps “quietledger” in a separate list for a future shop, because mixing a shop-sounding phrase into the index page would not match the six notes. These names are examples she wrote down herself, and the spellings are only her own records, not a claim that any registrar search will accept them.

For the launch itself she makes a one-page sitemap as a concrete deliverable:

Page title: Field Notebook Index Field one: note number (N01–N06) Field two: note title (example record: “N03 — Fastener sizes”) Field three: image file name (example record: “n03-fastener.jpg”) Field four: status (draft or ready)

She fills two rows to see how it reads. Row one is N01, “Opening notes,” n01-opening.jpg, ready. Row two is N03, “Fastener sizes,” n03-fastener.jpg, draft. The numbering lets her match a note to its image without guessing, and the status column tells her which pages are worth publishing first. This is her own working sheet, not a form taken from any service.

She also writes a short registrar comparison in the same notebook, with three columns: annual price she expects to pay, renewal price she expects later, and whether the control panel explains DNS records in plain language. She enters two made-up figures for each candidate to practise the choice: one column says eighteen, the renewal column says twenty-two; the other says twelve and twenty-six. She chooses the twelve-and-twenty-six option for the first year and notes the later cost as a reason to revisit before renewal. For DNS she plans three records only: an address record pointing the main name to the host, a second address record for the www prefix, and a mail-related record she will copy from the host’s instructions. She keeps the mail record value blank until the host supplies it, rather than inventing one. When a page is ready she will use a fixed path such as /notes/n01 and /notes/n03 for the two example pages, so the index links stay simple.

These are self-made examples meant to show the shape of the decision, not records of an earlier site or results from a trial. The point is to make the naming, the sheet, and the record plan visible on paper before anything is registered.

Searching for Available Domain Names in Registrar Interfaces

At Porkbun , after the account is set up, the Domains page is where a new domain name is searched for and where pricing for the top-level domains on offer is reviewed. In the search bar under the heading "SEARCH FOR YOUR NEW DOMAIN NAME," enter the domain name you want to register. If there are several names, the bulk search option to the right of the search bar accepts multiple entries, up to 100 domains, and can add all available ones to the cart automatically. Select the magnifying glass icon in the search box and wait while availability is checked. The search page then shows whether the domain is available and recommends other domain extensions.1

You can take your six-note draft and two candidate names and turn them into a short search log before you register anything. Open the registrar’s search field and enter one candidate at a time, using the exact spelling and suffix you wrote in your notebook. For each attempt, record four things in your own words: the candidate as typed, whether the interface shows it as available, unavailable, or offered with an alternative suffix, the first-year price shown, and the price shown for renewal if it appears.

Consider a small worked example. Candidate one is “fieldnote-index” with the suffix “.com.” The search result you record might read: shown as available, first-year price recorded, renewal price recorded separately, note that the display changes when a different suffix is selected. Candidate two is “field-note-index.” If the interface treats the hyphen as a different name, log that too, rather than assuming the two are interchangeable. You might add a fifth column headed “name I would actually say aloud,” with values such as “field note index” for both, then note which spelling you prefer and why.

Keep the log beside your sitemap so the naming decision and the page plan stay in one place. When a candidate looks promising, you can check whether its spelling still matches the titles in your table; if the image file names use a different pattern, you might adjust those names later rather than rewriting the domain choice. If a search offers an alternative suffix, record it as another row with its own prices and your reason for keeping or dropping it.

End this step by choosing one candidate to carry forward, writing a single sentence in your notebook explaining the choice in terms of spelling, suffix, and the prices you recorded. That sentence becomes the reference point for the next step, so you do not have to reconstruct your reasoning from scattered search results.

Completing the Checkout Process for New Registrations

In the cart, review the items before paying. Domain privacy is automatically added for TLDs that allow it unless the domain default privacy settings have been changed; the page says this appears under the domain’s “FREE Add-Ons” section. At this point, Website Builder, Email Hosting, or Logo Builder can also be upgraded to a Pro Plan for the domain by clicking the “Upgrade” link in each row.2

Click “Checkout,” and the system takes the order through the checkout process. According to the Dynadot help page, an “Order Finished” email arrives when the order has completed processing and the domain is registered.2

Before you start the checkout for your chosen candidate, you can prepare a small purchase-check page in the same notebook where your search log and sitemap already live. Give it three columns: item, value you confirm in the cart, and later cost you expect. Fill the first row with the candidate name you carried forward, for example “fieldnote-index.com,” and add the suffix in its own row so the string you checked is the same string you are buying.

A second row can record the registration term and the renewal price you noted during comparison, marked as an expected cost rather than a confirmed one. A third row might capture which contact and address details the form asks for, so you can prepare them instead of stopping midway. Keep these as your own working notes; they are not a checklist of requirements.

You might also write two short sentences under the rows: one saying which name variant you are deliberately not buying, such as the hyphenated form, and one saying what you would do if the cart shows a different total than your log. For practice, the first sentence could read: “Not buying fieldnoteindex.com now; the unhyphenated form reads more cleanly in the sitemap.” The second could read: “If the total includes an add-on I did not plan, remove it and recheck.”

After the order completes, you can write the date and the name as it appears in your account beside the same three rows, then note whether the site setup step follows immediately or later. This keeps the checkout decision tied to your six-note plan without turning it into a promise about what the registrar will display.

Choosing Between Default Settings and Custom Configurations

Once checkout is finished, the reader must decide whether to leave everything as the registrar set it or open the settings and change them before the site is connected to a host.

AspectPorkbunDynadotNamesLink
Privacy protection setting at checkoutDomain privacy is enabled by default for any domain whose TLD supports it, and valid account contact information can be masked with the free WHOIS Privacy service; the guide warns that some TLDs, such as .us, do not allow WHOIS Privacy and that checkout warnings should be reviewed.Domain privacy is automatically added for TLDs that allow privacy unless the user has changed the domain default privacy settings, and this is indicated under the domain's “FREE Add-Ons” section during cart review.The system automatically enables domain privacy protection (Whois Privacy), which can hide personal information to prevent spam and nuisance calls; the guide also notes that ICANN requires registration information to be true and valid.
Information template before purchaseThe guide requires valid contact information for the account, allows masking it with free WHOIS Privacy, and warns that some TLDs such as .us do not support privacy; it does not describe a separate registrant contact template to select during checkout.The guide covers searching, adding to cart, reviewing items, optional plan upgrades, and checkout, and states that an “Order Finished” email is sent when the order completes; it does not describe a registrant contact template selection step.Before purchase, the guide says to confirm the domain holder information template: if no contact template is selected, the default template generated from account information is used, and templates can be added and the default modified; ICANN-required registration details include holder name or organization name, email address, phone number, and full address (country, region, city, street, postal code).

123

Locating the Nameserver Management Section in Your Dashboard

In the Porkbun Knowledge Base guide, the Nameservers field is reached from the Domain Management screen: click the Details drop-down to the far right of the domain name, locate Nameservers, then click the edit icon. A pop-up appears showing the current nameservers, which the guide says specify which DNS servers are queried when a user looks up the domain.4

The guide states that, before a first change, this list is pre-populated with Porkbun nameservers. To save a change, the documented steps are to remove all existing entries, add the desired nameservers one per line, and click Save Nameservers.4

With your domain now registered, you can turn to the nameserver section of your dashboard and prepare a small record of what you find there before you change anything. Start a new block in the same notebook where your search log and sitemap already sit, headed with the date and the registered name exactly as it appears in your account. Under it, write three short lines describing what you see: whether the page lists two or more nameserver entries, whether it offers a preset option labeled as belonging to the registrar, and whether there is a separate place for custom entries. You might mark each line with one word of your own choosing, such as “listed,” “preset,” or “custom,” so the layout is easy to scan later.

Consider a worked example to see how the field set works. The block might read: registered name, fieldnote-index.com, recorded on the order date; nameserver entries, two, both marked as registrar presets; custom entry area, present but empty; change control, labeled as a save or update action. That example is a made-up sketch to show the shape of the note, not a report of a screen you should expect to match. If your own page shows different wording, you can record that wording instead and keep the same three lines.

You might also note, in one sentence, which parts of the page you would need to return to later when you connect hosting. The nameserver entries themselves are the part most likely to change, so a short reminder like “revisit entry list once hosting details are known” keeps your place without committing to a setting now. If the page offers a help link, you can write down where that link sits on the page rather than following it, so the record stays a map of the dashboard rather than a set of instructions.

End this step by leaving the entries unchanged and adding a single line under the block saying when you next intend to look at this section.

Updating Authoritative Nameservers for Hosting Connections

Porkbun 's guide describes changing authoritative nameservers when a hosting company requires its own nameservers or when you run your own DNS server. After logging in and reaching Domain Management, locate the domain, open its Details drop-down, find the Nameservers field, and click the edit icon. A pop-up then shows the current nameservers, pre-populated with Porkbun nameservers if the setting was never changed; the list specifies which DNS servers are queried when someone looks up your domain.4

Remove all existing entries, add the desired nameservers one per line, and click Save Nameservers. An additional confirmation message may appear, and the change is fully submitted only after clicking Submit once more. The guide warns that moving away from Porkbun usually breaks Porkbun -hosted services such as web hosting and email, so the new DNS host should answer requests for those services first. Propagation can take up to 48 hours, though most places see it within a few hours.4

You can take the same notebook record you made when you registered the name and extend it with one new field: “nameserver entries as shown, with the date I looked.” Before changing anything, open the nameserver section of your dashboard and copy what appears there exactly as written, in the order shown, so you have a before picture to compare against later.

Consider a worked example to see the field set in use. The block might read: registered name, fieldnote-index.com, recorded on the order date; nameserver entry one, copied as displayed; nameserver entry two, copied as displayed; and a final line, “hosting not yet connected.” For an archived entry — say a note about an older name you no longer plan to use — use the same four fields but mark the last line “kept for reference only,” so the two kinds of entry stay distinguishable when you read back through the notebook.

If you are preparing rather than acting, you can write one sentence under the block saying which hosting connection this change is meant to serve — for example, “this is for hosting the six-note index page.” That sentence anchors the entry to your sitemap without requiring you to verify anything yet.

You might also note which parts of the page you would return to when you connect hosting, keeping the nameserver lines themselves untouched until you have that connection information in hand. When you do update the entries, you can add a second dated line beneath the original so both versions remain readable side by side.

End this step by leaving the entries unchanged and adding a single line under the block noting when you next intend to revisit this section.

Frequently asked questions

When recording her two candidate domain names, what columns does she use in her registrar comparison?

She also writes a short registrar comparison in the same notebook, with three columns: annual price she expects to pay, renewal price she expects later, and whether the control panel explains DNS records in plain language. She enters two made-up figures for each candidate to practise the choice: one column says eighteen, the renewal column says twenty-two; the other says twelve and twenty-six.

What should she write in her notebook at the end of the step to choose one candidate to carry forward?

End this step by choosing one candidate to carry forward, writing a single sentence in your notebook explaining the choice in terms of spelling, suffix, and the prices you recorded.

What three columns should she give her purchase-check page before starting checkout?

Before you start the checkout for your chosen candidate, you can prepare a small purchase-check page in the same notebook where your search log and sitemap already live. Give it three columns: item, value you confirm in the cart, and later cost you expect.