Yes. You can add an MX record for a subdomain directly in the parent domain's DNS zone in mPanel, or using the BinaryLane CLI or API. You do not need to create a separate zone for this.

For example, to receive email at user@alerts.example.com, add an MX record named alerts in the example.com zone. The MX target is the mail server hostname supplied by your email provider.

TABLE OF CONTENTS

Add the record in mPanel

Open the parent domain's DNS records and add an MX record with the subdomain as its hostname. Have your email provider's MX hostname and priority ready.

  1. In mPanel's Domains page, select the parent domain, such as example.com, and open DNS Records.
  2. Select Add Record.
  3. Set Hostname to the subdomain only, such as alerts, and Record Type to MX.
  4. Enter the provider's hostname in Mail Server Host, including its trailing dot, and enter the provider's Priority. For example, mail.example.net. and 10 are illustrative values, not settings for your email service.
  5. Select Add. If your provider specifies multiple MX records, repeat these steps with each supplied hostname and priority.

For email addressed to the parent domain, such as user@example.com, use @ instead of alerts.

Prefer commands? See Manage your DNS records with the BinaryLane CLI or API.

Check the record

Check that the saved record shows the full subdomain, type MX, and the intended mail host and priority. Then query a BinaryLane nameserver directly, as shown in the DNS CLI/API guide's verification steps, using the subdomain name and record type MX.

You can prepare records before changing nameservers. For public queries to use this zone, the domain must be delegated to BinaryLane's nameservers. Saved changes may take time to appear in DNS answers, and other resolvers may retain cached answers. See BinaryLane DNS hosting and nameservers.

Existing subdomain delegation

Already using a separate subdomain zone?
If the parent zone already has NS records delegating the subdomain, manage its MX records in that delegated zone. Adding an MX record to the parent zone does not override the delegation. You do not need to remove a working delegation just to use the direct method described above.

A separate subdomain zone still needs matching NS delegation in the parent zone for public resolvers to find it. Creating the separate zone alone is not enough.