Reverse DNS: Difference between revisions

(2 intermediate revisions by the same user not shown)

Line 50:

[[File:Reverse-dns-inaddrarpa.png|border]]

==4. Generic Per-IP Block==

Support staff can add a name on a per-IP block basis and we'll automatically create reverse records, e.g., if your block is <code>81.187.81.0/29</code> and we add the name <code>hosts.testing.me.uk</code>, then we'll create reverse records such as:

<code>0.hosts.testing.me.uk</code>

<code>1.hosts.testing.me.uk</code>

<code>2.hosts.testing.me.uk</code>

etc.…

Contact support staff for this.

=b. Delegating reverse DNS to your own nameservers=

Line 66:

Line 57:

We have two main ways of setting up the delegation of reverse DNS to your own nameservers, and you can select which you prefer using the control pages. In both cases the task is to set a reference on our system to the name servers that you manage and that will give the answers for reverse DNS queries. The reverse DNS name server boxes on the control pages let you specify one to six name servers (by name, not by IP address) for your name server(s). Don't put a dot on the end of the name though.

[[File:Reverse-dns-delegation.png|none|frame|Delegating reverse DNS to your own nameservers]]

[[File:Reverse-dns-delegation.png|none|frame|Delegating reverse DNS to your own nameservers. Enter your DNS hostnames in to the boxes, not IP addresses]]

This setting is found on the control pages under the link to your Login. This will apply to IPv4 and [[IPv6]].

Line 72:

Line 63:

===1. Delegation by NS===

Delegation by NS works by putting your name server in our DNS for each of your addresses. e.g. if you had <code>217.169.0.0-3</code> then we would put your name servers for each entry <code>0.0.169.217.in-addr.arpa</code>, <code>1.0.169.217.in-addr.arpa</code>, <code>2.0.169.217.in-addr.arpa</code>, <code>3.0.169.217.in-addr.arpa</code>. This would mean you can create four separate zone files each of which has normal SOA records etc., and a single PTR record with the name for that IP address. This is logically the correct way of doing it as the reverse DNS zone is delegated at each level of control right down to the IP address level. It is rather tedious to set up lots of zone files though, especially if you have, say, 128 addresses.

Delegation by NS works by putting your name server in our DNS for each of your addresses. e.g. if you had <code>217.169.0.0-3</code> then we would put your name servers for each entry <code>0.0.169.217.in-addr.arpa</code>, <code>1.0.169.217.in-addr.arpa</code>, <code>2.0.169.217.in-addr.arpa</code>, <code>3.0.169.217.in-addr.arpa</code>. This would mean you can create four separate zone files each of which has normal SOA records etc., and a single PTR record with the name for that IP address. This is logically the correct way of doing it as the reverse DNS zone is delegated at each level of control right down to the IP address level. It is rather tedious to set up lots of zone files though, especially if you have, say, 128 addresses. - but you could ''cheat'', and on your nameserver add the ''parent'' as a zone (eg: <code>0.169.217.in-addr.arpa</code>, and just add PTRs for the IPs you have.

Remember that you also have a WAN address which may be completely different from your other addresses, and the reverse DNS is also delegated to your name servers for this too.