Skip to content
English
  • There are no suggestions because the search field is empty.

Why delegate a subdomain?

Our system automatically generates a complete set of DNS records for the appropriate domain. That set includes:

  • Our system automatically generates a complete set of DNS records for the appropriate domain. That set includes:
    • A Records: Address Record points a domain or subdomain to an IP address.
    • MX Records: Mail eXchanger record is a type of certified and verified resource record in the Domain Name System that specifies a mail server responsible for accepting email messages on behalf of a recipient's domain.
    • TXT Records:
      • SPF: Sender Policy Framework record used to indicated to mail exchanges which hosts are authorized to send mail for a domain.
      • DKIM: DomainKeys Identified Mail is a protocol that allows verification through cryptographic authentication.
      • DomainKeys: A deprecated email authentication system designed by Yahoo to verify the domain name of an email sender and the message integrity.
      • DMARC:Domain-based Message Authentication, Reporting & Conformance is an email authentication, policy, and reporting protocol. It builds on SPF and DKIM to align messages with the sender’s “From” domain, define how recipients handle authentication failures, and provide reports that help protect against fraudulent email. 
    • For a delegated sub-domain only, a further sub-domain "img" for hosted assets (e.g., img.news.example.com).
  • URLs in the email content are automation replaced with new URLs that use the sub-domain so that iPost can track views and clicks. Those new URLs redirect to the original URL after recording the action.
  • The SMTP envelope FROM: field uses a tagged address at the sub-domain, so that iPost can handle bounces (via the automatically created MX records) and match them with recipient addresses. 
  • At the customers’ option, the user-visible From: field in the message may use an address at the sub-domain (we call this the IBMF, “in-bound message filter”, address) to automatically process opt-out requests, out-of-office responses, etc. (also via the MX records). This is not required, however, please see our documentation on Sender Guidelines to learn what role the From Address plays in domain alignment and, ultimately, deliverability.

This automation frees you from having to react if we update any of our IP addresses or if a new type of TXT record becomes standard, etc.