Re: [OT] Domain Name Registrars

Troy Settle wrote:

Here's the thing for name servers (at least as far as I understand
it)...

With all due respect, the problem with postings like this is that it
actually slows down the process of people finding out the truth for
themselves by perpetuating misinformation. It's far better to either do the
research and post accurate information, or avoid posting.

the glue records must exist in the root servers for each registry.

A) The only "root servers" are those that serve the root zone. What you're
referring to are Top Level Domain (TLD) name servers. B) Policies on whether
name server IP records are necessary for domain registration vary by
registry. There is no hard and fast rule. C) "Glue" is a DNS term of art
that refers specifically to IP addresses for servers whose hostnames are IN
the zone they serve. For example, if you have the following NS records:

example.org. NS ns1.example.org.
example.org. NS ns2.example.org.

Then glue records are _required_ in the ORG TLD name servers. Otherwise
there is no way for anyone to reach your servers.

However, for those situations where the name server hostnames are all out of
zone, it's generally better to avoid putting IP address records for those
hostnames in the parent zone (regardless of what level we're talking about
here) because it makes the administration of the zones/domains much more
difficult.

If your name servers are under the .ca TLD, and you're
registering a .com domain, then the .com registry must have the glue
records for your .ca name servers.

That's actually exactly the opposite of the truth. If the name servers for
your COM name are in CA, then the IP addresses can be resolved the normal
way (recursively).

As an OpenSRS reseller,

eek,

Doug

--

This .signature sanitized for your protection

_______________________________________________
freebsd-isp@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to "freebsd-isp-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: external DNS
    ... But as for my owmn DNS I will have to get it up and running very soon. ... >> If your domain is no longer on our servers and you have ... >> registered with the central registry. ... > because they do not have a zone for your domain. ...
    (microsoft.public.win2000.dns)
  • Re: Server registration lost after domain password change
    ... Servers in SQL Enterprise Manager. ... the fix in XP service pack 1 only works if the registry key "MasterKeyLegacyNt4Domain" is ...
    (microsoft.public.sqlserver.tools)
  • Re: using PIAS at the time of deployment
    ... PIA's do not contain any code, they are simply .NET metadata representing ... the COM interfaces exposed by the native COM servers. ... > suite and then manually added the files in the global assembly cache ... > and registered them in the registry also. ...
    (microsoft.public.dotnet.framework.interop)
  • Re: [OT] Domain Name Registrars
    ... the root name servers are not authoritative for the TLDs. ... name servers have delegated authority to for those zones. ... that for the .mil zone four of the root servers are authoritative, ... then the .com registry must have the glue ...
    (freebsd-isp)
  • RE: User rights on Terminal Services
    ... For actually using COM servers and ActiveX controls, ... User rights on Terminal Services ... I am not sure if there is any registry tomfoolery in it - what is the best ...
    (Focus-Microsoft)