252
edits
Reverse DNS: Difference between revisions
m
typo
m (typo) |
|||
|
Because of the way DNS works, control is delegated at each level, so <code>my.firebrick.co.uk</code> is delegated so that the name servers for <code>co.uk</code> tell the name servers for <code>firebrick.co.uk</code> and so on. This is normally only at a couple of levels but it could be that at each level control of the domains below that level (i.e. with anything added to the start of the domain) is delegated to a new name server.
With IP addresses the control is delegated the other way, e.g. <code>217.''x.x.x''</code> is delegated to RIPE, and <code>217.169.0.''x''</code> is delegated to AAISP. To allow DNS to be used to turn IP addresses
To delegate your IP addresses to you we have to find a way to delegate within the block of 256 addresses we have received from RIPE. Few customers have a complete block of 256 addresses. Those that do can simply be set up so that their own name servers are used in the delegation from RIPE. For anyone with less than 256 addresses we have to find a way to give you some of the addresses within a block - which DNS does not allow.
| |||