Adding a Netblock for Reverse DNS
Adding your netblock
Reverse DNS is separate from the standard DNS for a domain name, and as such is a different service. Our rate for the service is 24.95/yr per netblock (range of IP Addresses). It requires that your ISP be willing to delegate control over the netblock they have assigned you to easyDNS. Before setting up a netblock with easyDNS, please contact your ISP and ask them if they can provide you with a PTR record for your IP addresses, or, if not, if they will be able to delegate to easyDNS.
Once you have this confirmed, you will need them to provide you with the netblock itself.
We require that this be this in what is called [CIDR notation.]
This will be a numeric representation of the range with consists of the starting IP, and then the class of block-sizes, to determine theending IP of the range.
For example, if your ISP has provided you with a range of 32 IP addresses that begin at 22.214.171.124, then this is called a /27 range, and the CIDR notation for it would be 192.168.2.0/27
Once you have this in hand, log into your easyDNS account, and then go to our reverse DNS page.
Select the Reverse DNS service level, and then click to generate the invoice. Click to accept our terms and conditions, then select the method of payment you prefer. Once paid, the zone will become active on our system, and once you configure it, your ISP can then delegate the block to us.
Delegation Methods (Info for your ISP)
When the reverse block is added, our system will automatically detect the current relegation method your ISP has selected, and advise you as to that you need them to do. This information is available in the Domain Administration section of your users page, in the DNS Settings tab on the Reverse Information line, behind the behind the Get Info and Change links.
If your ISP is at all uncertain about how to do this, please ask them to see [the documentation here.]
Setting up your PTR Records
Once the netblock has been added and the invoice paid, you can configure PTR records by clicking into the DNS Information line for the netblock and clicking PTR. In general, the only IPs that require PTR records are those which are the location of a sending mail server.
The first time you open this, you will see that no PTR records have been defined.
In this example, we imagine a sending mail server named mail.easydnstest.ca, which is located at the IP address 126.96.36.199. An A record exists in the DNS for the host mail.easydnstest.ca that points to 188.8.131.52, now we enter a PTR record for the IP address that resolves the same name. This way, when a mail server receives a message delivered by that host, it will be able to check the IP DNS and see that it agrees that this is the proper host for that address.
On the left hand side, enter the final octet of the address you want the record for. On the right, the host record you wish it to show as valid for that IP.
After that, when you enter the PTR records for the block, you will see something like this :
What Does it all Look Like
In short, when you send mail outbound from a server, the receiving mail server may wish to check that this connecting mail server is coming from somewhere that has some sort of verification as to its identity.
So it will do lookups first on the name of the host connecting to see what the DNS for that host resolves to, and then for the PTR record to confirm they match, like so:
inboundmailserver$ dig +short mailout.easydns.com 184.108.40.206 inboundmailserver$ dig +short -x 220.127.116.11 mailout.easydns.com.
It sees they match, and allows the mail to pass.