Jump to content

This is the support site for Andrews & Arnold Ltd, a UK Internet provider. Information on these pages is generally for our customers but may be useful to others, enjoy!

Reverse DNS: Difference between revisions

m
→‎1. Delegation by NS: accessibility- <code> markup
m (→‎4. Generic Per IP Block: accessibility- code markup)
m (→‎1. Delegation by NS: accessibility- <code> markup)
==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 4four separate zone files each of which has to 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.
 
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.
252

edits