Re: SPF = Sender Policy Framework (was: Microsoft spam solution<snip>)

From: Randolf Richardson (rr_at_8x.ca)
Date: 09/20/04


Date: Mon, 20 Sep 2004 05:02:55 GMT


"Dave Uhring <daveuhring@yahoo.com>" wrote in news.admin.net-abuse.email:

[sNip]
> That does not answer the question about what a "registered name server"
> is. When I register a domain the technical information I provide is the
> domain name and the IP addresses or hostnames of the two name servers
> which are authoritative for that domain.
>
> What is a "registered name server" which you want removed?

            A "registered name server" is, essentially, a host record as
maintained by Network Solutions (I'm not sure if other Registrars do/can
participate in this, but I've heard that Network Solutions manages this
aspect of DNS and they provide management of host records as a free
service) and used by the root servers for DNS resolution more reliably.

            The "host" can be looked up in Network Solutions' WHOIS server, for
example one of my host records is as follows:

                        telnet whois.networksolutions.com 43
                        host netware.inter-corporate.com
[sNip]
                        Hostname: NETWARE.INTER-CORPORATE.COM
                        Address: 24.87.56.253
                        System: ? running ?
[sNip]
                        <Connection terminated by remote.>

            Regardless of how I configure my DNS zone to return a different IP
address for "netware.inter-corporate.com," the root servers will override
this by providing the information specified in the host record. This also
seems to speed up DNS resolutiona little bit, by the way, because the root
servers don't have to take addition steps to look up external NS records.

            Since it would be impossible for DNS to function if we relied entirely
on DNS servers by name, the "host" record is needed to set up a "registered
name server."

            One of my criteria for picking a Registrar is that they understand
this concept and can support it. So far only Network Solutions has
satisfied me in this regard, which is one of the many reasons I use them as
my Registrar.

-- 
Randolf Richardson, pro-active spam fighter - rr@8x.ca
Vancouver, British Columbia, Canada
Please do not eMail me directly when responding to my
postings in the newsgroups.
Sending eMail to other SMTP servers is a privilege.


Relevant Pages

  • Re: SPF = Sender Policy Framework (was: Microsoft spam solution<snip>)
    ... When I register a domain the technical information I provide is the ... aspect of DNS and they provide management of host records as a free ... service) and used by the root servers for DNS resolution more reliably. ...
    (comp.os.linux.misc)
  • Re: A server with two IP addresses only register the first IP to D
    ... Windows 2003 and Windows 2008 servers. ... Secondary IP Address will not register with DNS while Windows 2008 ...
    (microsoft.public.windows.server.dns)
  • RE: The Common System Interface: Intels Future Interconnect
    ... keep in mind that there is now a massive trend to consolidating ... (latency and bandwidth are restrictions that might require some servers left distributed), ... Kerry Main ...
    (comp.os.vms)
  • Re: Internet Sharing on Domain
    ... > The register which I went through has my public IP information. ... > use this to update the Root servers with the current information. ... > forwarding the requests solved the connectionsharing/DNS dilema. ...
    (microsoft.public.win2000.dns)
  • Re: Dynamic DNS not updating on 2003 servers
    ... registration then it will register. ... > I checked the box to register DNS and the event log> reports an error trying to update the DNS server, which> by our setup it cannot, but should get registered by the> domain controllers which can update our DNS. ... We have not> had this issue with our W2K servers, ... >>Microsoft Windows MVP - Active Directory ...
    (microsoft.public.win2000.dns)