If the domain already has a Sender ID record, the existing record will need updating to include Airship’s servers. If the domain does not have a Sender ID record in place, a record will need to be added. 

  1. Log into the administrative console for your Domain name (ie. 123-reg, 1&1, Easily, GoDaddy).
  2. Locate the page which allows the domain's DNS records to be updated. In some cases this is hidden behind an “advanced settings” section.

    If a Sender ID record already exists for the domain:
  3. Edit the existing TXT record and add the include statement, marked red in the example below. Do not change anything else, simply add the include:_sid.airship.co.uk as indicated in the example below:

    spf2.0/pra include:_sid.airship.co.uk include:_spf.google.com ip4:195.1.2.3 -all

    If a Sender ID record needs to be added for the domain:
  4. Below is the minimal Sender ID record needed to allow the Console to deliver email on behalf of the domain. If the Console is the only platform sending email on behalf of the domain, simply create a new TXT record containing the text below:
    spf2.0/pra include:_sid.airship.co.uk -all

    The “include:_sid.airship.co.uk” MUST be present in the final TXT record. This tells the recipient’s email platform to allow Airship's Console as a sender for the domain, and to block any other servers.
  5. If the Console is not the only platform sending email on behalf of the domain, all other platforms need to be identified and added upon addition of the new TXT record. Failing to do so may result in bounced email sent by those platforms not being identified within the new TXT record. If only one other IP address is sending on behalf of the domain the IP address can be listed using ip4 or less common ip6 tags. An ip4 example is shown below:

    spf2.0/pra include:_sid.airship.co.uk ip4:195.1.2.3 -all  

    Several IP addresses can be listed using the ip4 or ip6 tag, as indicated below:

    spf2.0/pra include:_sid.airship.co.uk ip4:195.1.2.3 ip4:195.1.2.4 ip4:195.1.2.5 ip4:195.1.2.6 -all  

    For other platforms, such as Google Apps, specific include statements may be needed, the details of which should be available from each platform provider. Google Apps would look like below:

    spf2.0/pra include:_sid.airship.co.uk include:_spf.google.com ip4:195.1.2.3 ip4:195.1.2.4 -all  


Did this answer your question?