On 15/03/2012 03:24, Martin T wrote:
> Ok, but still RIPE domain object is just an informational record? I
> mean DNS servers don't use RIPE domain object data, do they? So
> basically nothing happens if I don't create(or update) domain object
> in RIPE database when I delegate a zone file.
Marti
Ok, but still RIPE domain object is just an informational record? I
mean DNS servers don't use RIPE domain object data, do they? So
basically nothing happens if I don't create(or update) domain object
in RIPE database when I delegate a zone file..
Martin
KuupƤeval 20. detsember 2011 19:37 kirjut
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 rephrase: In RIPE, reverze delegations are done through
RIPE database domain: objects.
They
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 database manual,
>>"nserver" attri
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 database manual,
"nserver" attribute under domain object specifies nameservers of the
domain- has this some sort of practical use or is it just
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
6 matches
Mail list logo