{"id":1152,"date":"2021-04-07T13:58:07","date_gmt":"2021-04-07T10:58:07","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=1152"},"modified":"2022-10-12T10:54:32","modified_gmt":"2022-10-12T07:54:32","slug":"dns-records-explained","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/dns-records-explained\/","title":{"rendered":"DNS Records Explained"},"content":{"rendered":"

Whenever you want to access a website on the internet, <\/span>the Domain Name System<\/b> (DNS)<\/span><\/i> makes sure you don\u2019t end up with the wrong thing. <\/b><\/p>\n

The DNS keeps a directory that lets it match IP addresses to corresponding domain names stored in its database. This database holds tons of updated DNS records and text files associated with handling a domain request.<\/span><\/p>\n

In this article, we\u2019ll explore <\/span>DNS Servers, DNS Records, and how they operate. <\/b><\/p>\n

What are DNS Records?<\/b><\/h2>\n

Think of DNS records as an archive for domains. <\/span>The archive has authoritative instruction on domain locations<\/span>, type of content hosted on the domain server, how to access it, and when it’ll expire<\/b>.<\/span><\/p>\n

The DNS records effectively command DNS servers on what to do. All domains have essential DNS records hosted on <\/span>DNS nameservers that enable users to access their sites.<\/b><\/p>\n

What are Nameservers?<\/b><\/p>\n

A nameserver is another name for <\/span>a DNS server.<\/b> It houses an enormous archive, albeit decentralized, of domain names and matching IP addresses.<\/span><\/p>\n

The nameserver is the backbone of the modern-day internet and is responsible for telling your computer what to do when you’re sending an email or looking up stuff on the web. <\/span><\/p>\n

When you look up a website, the <\/span>DNS resolver<\/b> (which is also a DNS server) <\/span><\/i>attempts to resolve the query by accessing DNS records at the top-level domains such <\/span>as .com or .org<\/b>, located at the <\/span>DNS root server<\/b>.<\/span><\/p>\n

It requests specific information on a hostname <\/span>(website)<\/span><\/i> query from a higher-level authoritative nameserver. The<\/span> nameserver query process <\/b>ends when the nameserver returns the correct information on the IP address to the DNS client <\/span>(your browser ).<\/span><\/i><\/p>\n

How Does a DNS Server Work? <\/b><\/h2>\n

The idea behind <\/span>DNS is an accessible phone book<\/span> for the internet<\/b>. Computers on the web access the site you\u2019re trying to reach by sending a request to this phone book<\/span>, which receives and answers your query with corresponding feedback. <\/span><\/p>\n

Like how you dial and connect a number from your phone book<\/span>, <\/span>DNS connects with this internet directory through a DNS server<\/b>. The DNS Server keeps information records that resolve domain names to corresponding<\/span> IP addresses<\/b><\/a>.<\/b><\/p>\n

For instance, you’re more likely to remember www.scalahosting.com than you would a string of numeric characters. When you assess ScalaHosting, your browser performs a DNS query via a DNS server to get this<\/span> IP address – 173.237.190.136 <\/b>–<\/span> your browser connects.<\/span><\/i><\/p>\n

A DNS server resolves three types of queries.<\/span><\/p>\n

Recursive Query<\/b><\/h3>\n

In this query, the <\/span>DNS Resolver resolves a hostname request from a DNS client<\/b>.  The resolver starts by accessing records at the DNS root server till it finds <\/span>an Authoritative nameserver<\/b> with relevant records on the IP address and other information on the hostname. <\/span><\/p>\n

If the resolver doesn’t find any relevant information on the hostname, it comes back with an error message.<\/span><\/p>\n

Non-recursive Query<\/b><\/p>\n

For a non-recursive query, the DNS Resolver already has partial or complete information on the hostname query stored in its local cache.<\/span><\/p>\n

At this instance, the resolver returns a relevant DNS record to the DNS client or queries an Authoritative nameserver directly for complete DNS records.<\/span><\/p>\n

In both cases, the DNS resolver has information on<\/span> the hostname’s IP address <\/b>and does not need to run extra queries.<\/span><\/p>\n

Iterative Query<\/b> <\/b><\/h3>\n

The DNS resolver resolves the hostname query via many requests<\/b> to multiple nameservers to return the best answers in the iterative query.<\/span><\/p>\n

This happens when the resolver has no access to relevant records or can’t find it in its cache. <\/span><\/p>\n

To solve this, it refers the DNS client to another Authoritative Nameserver or Domain Root Server at the required DNS zone.<\/span><\/p>\n

Then, the DNS client repeats the entire query process against the new DNS server the resolver referred it to. <\/span><\/p>\n

Types of DNS Records<\/b><\/h2>\n

When you register a domain from ScalaHosting, we host and manage that domain\u2019s DNS records on our servers. The DNS servers edit,<\/span> delete or create records for the<\/b> domain <\/b><\/a>assigned to it.<\/b><\/p>\n

Because of this, we offer a way to manage some of your domain records without the technicalities involved. We\u2019ve listed some of the common and less-common DNS records below.<\/span><\/p>\n

Common Types of DNS Records<\/b><\/h3>\n

These records provide relevant information about a domain or hostname and its corresponding IP address.<\/span><\/p>\n

A Record<\/b><\/h4>\n

The A Record is an Address Mapping Record. It stores the IPv4 address of a domain. <\/span><\/p>\n

The A records also operate a DNS-based Blackhole List (DNSBL). This list helps email servers weed out and block messages from known spammer domains.<\/span><\/p>\n

CNAME Record<\/b><\/h4>\n

The Canonical Name (CNAME) Record forwards one domain to another domain through an alias. <\/span><\/p>\n

Domains use the CNAME records in the absence of an A record<\/b>. Because of this, all CNAME records point to another domain, not an IP address.<\/span><\/p>\n

CERT Resource Record<\/b><\/h4>\n

The Certificate record keeps encryption certificates like:<\/span><\/p>\n

    \n
  • PKIX<\/span><\/li>\n
  • PGP<\/span><\/li>\n
  • SPKI.<\/span><\/li>\n<\/ul>\n

    PTR Record<\/b><\/h4>\n

    This record is <\/span>a DNS Reverse-lookup Pointer. <\/b>It enables a resolver to provide an IP address and get a hostname as feedback.<\/span><\/p>\n

    TXT Record<\/b><\/h4>\n

    The DNS Text record lets a domain administrator store human-readable texts in the DNS.<\/span><\/p>\n

    MX Record<\/b><\/h4>\n

    The Mail Exchanger (MX) Record directs outbound mail via an SMTP server to a mail server.<\/span><\/p>\n

    Less-Common Types of DNS Records<\/b><\/h4>\n

    We’ve listed some DNS records responsible for other functions not directly associated with a <\/span>hostname and IP address.<\/b><\/p>\n

    NSEC Record<\/b><\/h4>\n

    The Next Secure Record proves that a DNSSEC record is unavailable.<\/span><\/p>\n

    DNSKEY Record<\/b><\/h4>\n

    This record verifies <\/span>Domain Name System Security Extension<\/b> (DNSSEC<\/span><\/i>) <\/span>signatures <\/b>through a public key.<\/span><\/p>\n

    DNAME Record<\/b><\/h4>\n

    The Delegation Name Record is similar to the CNAME Record but reroutes subdomains as well.<\/span><\/p>\n

    Final Thoughts<\/b><\/h2>\n

    DNS records have other functions that enable users to view your website on the internet. <\/span><\/p>\n

    While free DNS service providers might host your domain with limited firewall protection, <\/span>ScalaHosting guarantees 100 percent uptime, a robust firewall, and a fully managed website<\/b> that caters to all your business needs.<\/span><\/p>\n\n\n

    How To Point a Domain Name To a Web Hosting Provider<\/p>\n\n\n\n