Primary Name Server (MNAME)

The Primary Name Server (MNAME), also known as the Master Name Server, is a crucial component of the Start of Authority (SOA) record in the Domain Name System (DNS). The MNAME field specifies the fully qualified domain name (FQDN) of the primary DNS server responsible for the DNS zone.

Here’s what you need to know about the MNAME field:

  1. FQDN: The MNAME field should contain the FQDN of the primary DNS server, which typically includes both the hostname and the domain name. For example, if the primary DNS server for the “example.com” domain is “ns1.example.com,” then “ns1.example.com” would be specified in the MNAME field.
  2. Responsibility: The primary DNS server listed in the MNAME field is considered authoritative for the DNS zone. It’s responsible for maintaining and serving DNS records for that particular zone. Other DNS servers, such as secondary or slave servers, may synchronize their data with the primary server.
  3. Updates: When changes are made to DNS records within the zone, they are typically made on the primary DNS server first. Secondary DNS servers then synchronize their data from the primary server to ensure consistency across the DNS infrastructure.
  4. Contact Point: The MNAME field, along with the RNAME (Responsible Person’s Email Address) field in the SOA record, serves as a contact point for administrative purposes. If there are issues or questions related to the DNS zone, individuals can refer to the MNAME and RNAME for contacting the responsible parties.

Here’s an example of what an SOA record with the MNAME field might look like:

example.com. IN SOA ns1.example.com. admin.example.com. (
    2023090401 ; Serial number
    3600       ; Refresh interval
    900        ; Retry interval
    1209600    ; Expire interval
    86400      ; Minimum TTL
)

In this example, “ns1.example.com” is the Primary Name Server (MNAME), and it is responsible for the “example.com” DNS zone. The MNAME field is a critical component of DNS zone management, as it designates the primary point of authority for the domain.

Key terms in plain language

Open a term for a concise explanation of language used on this page.

Colocation

Placing customer-owned servers and network equipment in a professionally operated data center that provides power, cooling, physical security, and connectivity.

Content Delivery Network (CDN)

A distributed system that serves website or application content from locations closer to users, improving speed, resilience, and capacity.

Cloud Computing

Computing resources—such as applications, servers, storage, or databases—delivered from remote infrastructure and scaled as requirements change.

Infrastructure as a Service (IaaS)

Cloud-based servers, storage, and networking that customers configure and manage without owning the underlying data-center hardware.

Bandwidth

The amount of data a connection can carry in a given time, usually measured in Mbps or Gbps. More bandwidth supports more users, devices, and simultaneous applications.

Disaster Recovery (DRaaS)

A plan and service for restoring applications, data, and operations after an outage or disruption. DRaaS provides recovery infrastructure through a managed cloud service.