So that you are able to provide Direct addresses in the form doctor@practice.direct.software-vendor.com, you need to delegate the DNS for sub-domain direct.software-vendor.com to the HISPDirect service. The following details how to delegate the DNS for the sub-domain.
For your domain of choice e.g. software-vendor.com, create a sub-domain named direct under software-vendor.com i.e. direct.software-vendor.com. The following table details the two DNS records required to create your sub-domain and delegate the DNS for the sub-domain.
| Record Type | Sub Domain | Points To |
| NS | direct | ns1.direct.hispdirect.com |
| NS | direct | ns2.direct.hispdirect.com |
Please note:
- The only record type possible to use to delegate a sub-domain is NS, no other record type can be used to delegate the DNS of a sub-domain to other name servers. If you are not able to determine how to create NS records with your DNS provider, we suggest contacting support provided by your DNS host. If your DNS provider can not create the required NS records, your next step is to either register a new domain and have the DNS hosting performed by a company that does support sub-domain delegation (eg. GoDaddy) or move your existing DNS hosting to a company that supports sub-domain delegation. The value of registering a new domain over changing the DNS hosting of an existing domain is that you avoid breaking any of the existing domains DNS configuration.
- Do not create a Start of Authority (SOA) record. The SOA record will be created within our name servers. The existence of a SOA record for your direct subdomain in your name servers will prevent the subdomain delegation from working.
If you have a firewall requiring configuration to permit access to the HISP, the following table details all the access points to the HISP.
| Port | Protocol | IP Address | Provides |
| 25 | TCP (SMTP with STARTTLS available) | 52.0.118.85 & 34.201.226.167 | SMTP - send Direct message |
| 53 | UDP & TCP (DNS) | 52.205.6.204 & 34.203.62.211 | DNS - resolve host names and discover Direct certificates |
| 80 | TCP (HTTP) | 52.0.118.85 & 34.201.226.167 | Redirect to HTTPS |
| 143 | TCP (IMAP with STARTTLS available) | 52.0.118.85 & 34.201.226.167 | IMAP - retrieve Direct message |
| 443 | TCP (HTTPS) | 52.0.118.85 & 34.201.226.167 | Web applications & HISPDirect REST API |
| 465 | TCP (SMTPS) | 52.0.118.85 & 34.201.226.167 | SMTPS - send Direct message |
| 587 | TCP (SMTP with STARTTLS available) | 52.0.118.85 & 34.201.226.167 | SMTP - send Direct message |
| 993 | TCP (IMAPS) | 52.0.118.85 & 34.201.226.167 | IMAPS - retrieve Direct message |
| 995 | TCP (POP3S) | 52.0.118.85 & 34.201.226.167 | POP3S - retrieve Direct message |
| 1222 | TCP (SFTP) | 52.0.118.85 & 34.201.226.167 | SFTP - eg. HL7 messaging - key based authentication |
| 5443 | TCP (HTTPS with mutual SSL) | XD interface | |
| 5445 | TCP (HTTPS) | 52.0.118.85 & 34.201.226.167 | XD interface |
| 5446 | TCP (HTTPS) | 52.0.118.85 & 34.201.226.167 | XD interface |
The following host names are provided in production
| Hostname | IP Address | Services |
| mail.direct.hispdirect.com | 52.0.118.85 & 34.201.226.167 | SMTP, IMAP & POP |
| sftp.rosettahealth.net | 52.0.118.85 & 34.201.226.167 | SFTP (FTP using SSH2) |
| api.direct.hispdirect.com | 52.0.118.85 & 34.201.226.167 | HISPDirect REST API |
| xd.direct.hispdirect.com | 68.69.2.75 | XD interface |
| ns1.direct.hispdirect.com | 52.205.6.204 | DNS |
| ns2.direct.hispdirect.com | 34.203.62.211 | DNS |
| portals.rosettahealth.net | 52.0.118.85 & 34.201.226.167 | web applications such as the admin portal |
RosettaHealth's SFTP public key for hostname sftp.rosettahealth.net is
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCS63s4YffQdOQUb9EysBW9Jj11/6qbj/UukYWLm80vawQ05uEyX6mRkE7qJzFjofs0LHsJ1ojyNAvKk46aJjL9xjYN6d5Y/GxMCxjFsOeif1xOurmJDdfQXEot9YFV2uT6w1mRwcFq6L1SWUPrfeDds/ufSIFnipT18WZsb2mmIJDAdjN2t1Q5wJFT1qVLBQbqaEcA2gEpwW+nEbmltVLxesHUiXIdZL3zTzyLhaC5KEAuh0wsAaLDrFL7FUJbjoQRICgpoU3UK1+9/Q9O+JdhmdB5xIcTMDr5PWTInfFREvFD5QEtpJQFnG5BhrP+nYwVNbar27T9a8kEqnliKewV