PHWinfo - Afficher un message

01/10/2007, 17h46

Hi

I would like to know if I got some things right or not. You are the
experts so that's why I'm asking

Ok, so let's say I've registered a domain: example.com (and let's say
that regestrar's name is ARegistrar).

During the registration, new RRs (of type NS) were created on the
namservers of the com domain and I got access (via my registrars panel)
to change contents of those RRs. Is this right?

Still I need a service called DNS hosting, right?

Fortunately ARegistrar offers free DNS hosting to its clients, so during
the registration process, ARegistrar filled NS RRs on nameservers of com
domain with names of its nameservers - such as ns1.aregistrar.net
(primary) and ns2.aregistrar.net (secondary). Still correct?

So this newly created RRs say that the nameservers for example.com are
ns1.aregistrar.net (primary) and ns1.aregistrar.net (secondary), but
this information is not authoritative. Right?

The authoritative information about example.com resides on ARegistrar's
nameservers (ns1.aregistrar.net, ns2.aregistrar.net) in the form of NS
RRs (so the ns1.aregistrar.net says that it is a nameserver for
example.com). Right?

So it possible for me to change nameservers for my domain any time by
changing the NS RRs that reside on nameservers of com domain, right?
(and then I'll have to wait for the changes to propagate)

And that wouldn't be something that is called 'domain transfer' - I'm
just not using ARegistrar's nameservers but I still pay ARegistrar for
the domain because they are giving me the access to NS RRs of com
nameservers, right?

So basically, registering a domain (example.com) == getting access (via
registrars panel) to NS RRs of nameservers of higher level domain (com).
Right?

So the process of registering a domain as such has nothing to do with
DNS hosting except fot the fact that many (most) registrars offer you
DNS hosting (and configures it properly) when you register a domain. Right?

And last question - just want to be super sure: the SOA RR for
example.com resides on nameserver for that domain (i.e.
ns1.ARegistrar.net) and not on nameserver of com domain, right?

Ok, big thanks for any answers

01/10/2007, 17h46	#1
flawius Messages: n/a Hébergeur:	registering domain, NS and SOA RRs Hi I would like to know if I got some things right or not. You are the experts so that's why I'm asking Ok, so let's say I've registered a domain: example.com (and let's say that regestrar's name is ARegistrar). During the registration, new RRs (of type NS) were created on the namservers of the com domain and I got access (via my registrars panel) to change contents of those RRs. Is this right? Still I need a service called DNS hosting, right? Fortunately ARegistrar offers free DNS hosting to its clients, so during the registration process, ARegistrar filled NS RRs on nameservers of com domain with names of its nameservers - such as ns1.aregistrar.net (primary) and ns2.aregistrar.net (secondary). Still correct? So this newly created RRs say that the nameservers for example.com are ns1.aregistrar.net (primary) and ns1.aregistrar.net (secondary), but this information is not authoritative. Right? The authoritative information about example.com resides on ARegistrar's nameservers (ns1.aregistrar.net, ns2.aregistrar.net) in the form of NS RRs (so the ns1.aregistrar.net says that it is a nameserver for example.com). Right? So it possible for me to change nameservers for my domain any time by changing the NS RRs that reside on nameservers of com domain, right? (and then I'll have to wait for the changes to propagate) And that wouldn't be something that is called 'domain transfer' - I'm just not using ARegistrar's nameservers but I still pay ARegistrar for the domain because they are giving me the access to NS RRs of com nameservers, right? So basically, registering a domain (example.com) == getting access (via registrars panel) to NS RRs of nameservers of higher level domain (com). Right? So the process of registering a domain as such has nothing to do with DNS hosting except fot the fact that many (most) registrars offer you DNS hosting (and configures it properly) when you register a domain. Right? And last question - just want to be super sure: the SOA RR for example.com resides on nameserver for that domain (i.e. ns1.ARegistrar.net) and not on nameserver of com domain, right? Ok, big thanks for any answers