Hi there, Now we have delegation of the IN-ADDR.ARPA domains from the root servers, similar to the delegation of the 'ordinary' domains. Before this happened there were only one single registry that handled all the reverse NS delegations, former <hostmaster@nic.ddn.mil>. This was easy to understand. Yesterday I spent some time trying to explain for one of our customers how the registration currently works. Well, you know the story.... Then I come to think of: Why couldn't he send a request to hostmaster@44.193.in-addr.arpa? The information about the hostmaster of each domain is of course already viewable in the zone files, but wouldn't it be more user-fiendly to be able to address the hostmaster of the IN-ADDR domain directly? Maybe this way of using IN-ADDR.ARPA isn't approved in applicable RFC's (I haven't checked)? Regards, Hakan Hansson == Unisource Business Networks Sweden == Unidata IP Services * TIPnet NMC * Gothenburg == phone +46-31-7708072 * fax +46-31-114664 *** Aktiv medlem i '8:e bit:ens vdnner' ***
hh@tip.net (Hakan Hansson) writes: Hi there,
Then I come to think of: Why couldn't he send a request to hostmaster@44.193.in-addr.arpa?
The main problem would be that not even all sevice providers will get their mail systems to recognise hostmaster@44.193.in-addr.arpa as local mail! Daniel
participants (2)
-
Daniel Karrenberg
-
hh@tip.net