is NS record pointing to "some other name server" needed in case of classless IN-ADDR.ARPA delegations?

Hi, in case of classless IN-ADDR.ARPA delegations(http://www.ietf.org/rfc/rfc2317.txt) I have usually seen at least one NS record pointing to name server other than the end-customer ones. Example from rfc2317.txt where there are two NS records and the second one is not the end-customer name server

Re: purpose of the RIR(for example RIPE) "domain:" object

2011 19:37 kirjutas Matus UHLAR - fantomas : > On 20.12.11 19:32, Martin T wrote: >> >> Ok, but who will use reverse delegations in RIPE? > > > well, everybody who wants to resolve reverse DNS in Europe (and all IP space > maintained by RIPE). > > Maybe I had to reph

load-balancing in DNS using two A records

I have seen setups where one domain name has two address records. First IP address is in the ISP-A network and the other one is in the ISP-B network. In case I execute "host www..com", I always get two IP addresses as a reply and they always appear by turns. Am I correct, that setup like this provi

Re: purpose of the RIR(for example RIPE) "domain:" object

Ok, but who will use reverse delegations in RIPE? regards, martin 2011/12/19, Matus UHLAR - fantomas : > On 19.12.11 10:32, Martin T wrote: >>what is the purpose of RIPE database "domain:" objects? Are they >>practically used for something? And according to RIPE da

purpose of the RIR(for example RIPE) "domain:" object

Hi, what is the purpose of RIPE database "domain:" objects? Are they practically used for something? And according to RIPE database manual, "nserver" attribute under domain object specifies nameservers of the domain- has this some sort of practical use or is it just informative field(it's not mand