A customer portal moves to a new supplier, but staff still type the same familiar name. How can the name stay the same while the service moves? Because the name and its destination are separate. The Domain Name System, or DNS, supplies information that helps computers find the destination associated with a name. Updating that information can change where a connection goes without changing what the user types. 1

To read that information, it helps to recognize three labels: A, AAAA and CNAME. They are not grades. They identify different kinds of DNS record. Two contain network addresses; the third points to another name. We will follow a single example, portal.bakery.example, rather than try to learn every DNS record at once. 1 2 3

Start with the moment a colleague opens portal.bakery.example. The browser is the program displaying the portal; it does not already know every service’s network address. The device asks a lookup helper for address information about this name. The helper consults DNS, or a usable answer it has saved. A DNS record is one piece of published information with a label identifying its kind. Asking for an address is different from asking who receives email for the same domain. 1 2

After an address has been found, the browser can connect to the web service and request a page. The service, running on computers that answer such requests, supplies the portal’s content. The address record does not contain the login screen, a colleague’s password or a list of invoices. It is a direction needed before those application interactions can begin. 1

Two kinds of network address

Computers use network addresses to reach services. An address used on the internet is called an IP address. There are two address families here: the older IPv4 and the newer IPv6. IPv4 addresses have the familiar form of numbers separated by dots; IPv6 uses a longer form with groups separated by colons. DNS has a separate record type for each. 2 3

An A record supplies an IPv4 address. An AAAA record supplies an IPv6 address. A name may have information for one family or both, and it can have more than one address. Looking up A records does not also check AAAA records. These are different questions to the naming system, even though both concern the same portal name. 2 3

Read a simple illustrative entry as “for this name, the A answer is this IPv4 address.” A separate AAAA answer, if published, supplies an IPv6 address. The letters describe the format of the answer, not different website owners. They also do not indicate that one version of the website is more secure. Whether a visitor can use an address depends on the visitor’s connection and on a working service being available at the destination. 2 3

A business does not need to memorize numerical addresses to understand a move. It needs to know that old and new directions can exist in two separate sets. For example, one colleague may reach the new portal using IPv4 while another reaches the old portal using IPv6. That is a possible configuration problem, not proof that the colleagues typed different names. An administrator investigating the difference should not stop after checking only the first set. 2 3

A CNAME sends the lookup to another name

Sometimes the bakery’s DNS information does not hold the final address at all. Instead, it says that portal.bakery.example is another name for a name supplied by the application provider. This is an alias, recorded with CNAME. Think of an address-book entry that says “see this other entry.” The lookup service follows that name to obtain the needed information. 1 2

Follow the actual steps. The helper asks for the address of portal.bakery.example. The domain’s DNS service replies that it is an alias for customer.provider.example. The helper still has a name, not the final network address. It continues the lookup for that other name and obtains the address information published there. Only then does it return a usable destination to the device. Both names in this example are invented; the sequence shows how the instructions relate. 1 2

There are now two places to consider if the destination stops working: the bakery’s reference and the provider’s information behind the referenced name. A correct alias pointing to a name that no longer supplies a usable address cannot finish the job. Conversely, a working provider name does not help if the bakery’s alias was typed incorrectly. “We use CNAME” identifies a method, not a guarantee that every link in the lookup works. 1

That can be useful when a provider manages the destination. The bakery keeps its customer-facing name while depending on the provider’s named service. If the provider changes addresses behind that name, the bakery need not necessarily publish each address itself. There is still a dependency: the other name must continue to lead to the intended service. 1

A DNS alias is not a web redirect. It helps find a destination before the website answers. It does not contain a page path such as /invoices, and it does not itself tell the browser to replace the address shown to the user. A website can separately send a redirect after receiving a request. If the address bar changes, CNAME alone is not the explanation. 1 2

What the destination cannot tell you

An address is a place to start a connection, not a complete description of the computers and people behind it. A and AAAA records contain address information; they do not list where invoices are stored, who may read them or who owns the application. A familiar provider name in an alias is equally unable to answer all those questions. 2 3

For example, learning where visitors first arrive does not establish where all customer data is retained. Nor does a correct address guarantee that the portal will accept a login or complete an order. Finding the service and using it successfully are separate steps. DNS can succeed while the application has another problem. 1

Two visitors may also use different answers for a while after a change. A lookup service can temporarily reuse an answer it saved earlier. Updating the source does not instantly replace those saved copies. This is one possible reason for different destinations, not automatic evidence of tampering. 1 2

In an outside report, ask which name and which record types were examined. An address found for the public homepage is not automatically the destination of the customer portal. A portal’s record is not a map of the whole invoice-processing system. It is still useful information: it identifies a public dependency that needs someone responsible for maintaining it. The next question is how that dependency fits into the particular service you use, rather than guessing the entire architecture from one address.

When discussing a move with your supplier, you can now ask a much clearer question: “Does our name contain the destination addresses, or does it refer to a name that you manage?” The answer tells you which instructions must be maintained. It also keeps a conversation about reaching the portal separate from a conversation about what happens to your information once you get there.

Sources

1 — RFC 1034 — Domain names: concepts and facilities

2 — RFC 1035 — Domain names: implementation and specification

3 — RFC 3596 — DNS Extensions to Support IP Version 6