Check-Host.cc

The MB (Mailbox) record is a fascinating experimental artifact from the original RFC 1035 DNS specifications. In modern network architecture, the Domain Name System strictly handles the routing of traffic to a physical server or an IP address, while the internal application (like an email server) parses the payload to figure out which specific user the data belongs to. The MB record attempted to blur these lines. Instead of routing organizational mail to a centralized server cluster via MX records, MB records attempted to map individual user mailboxes directly to specific hostnames natively within the DNS zone file.

Direct-to-Host Mail Routing

Under the MB protocol theory, the DNS layer would possess granular knowledge of every employee or user in a network. For example, an administrator could theoretically configure an MB record so that mail addressed to the sysadmin mailbox was explicitly routed to a high-security UNIX mainframe, while mail addressed to sales was routed to an entirely different, less secure server. When a remote server wanted to deliver an email, it would query the DNS specifically for the local-part of the email address (the string before the @ symbol) to find the exact hardware destination of that single user's inbox.

The Unscalable Nightmare

The operational reality of the MB record was an absolute scaling disaster. Managing a mid-sized corporate network of 5,000 employees would require a sysadmin to maintain 5,000 individual, manually typed DNS records just to handle standard email routing. Every time a new employee was hired or fired, the core DNS zone file would have to be edited, the SOA serial incremented, and the changes propagated across the global internet just to provision a mailbox. It bloated zone files to unmanageable sizes and placed extreme processing loads on early DNS resolvers.

Delegation to the Application Layer

Engineers quickly realized that DNS was the wrong protocol for managing user-level identities. The industry completely abandoned the MB concept, establishing a firm architectural boundary. Today, DNS (via MX records) is solely responsible for getting the email packet to the front door of the organization's Mail Transfer Agent (MTA). Once the connection is established, application-layer software like Postfix, Exim, or Microsoft Exchange takes over, using internal databases or Active Directory to parse the local-part of the address and deliver the payload to the correct internal inbox. You will not find MB records resolving on any modern production network.