Re: SPF = Sender Policy Framework (was: Microsoft spam solution<snip>)
From: Alan Hodgson (ahodgson_at_simkin.ca)
Date: 09/20/04
- Next message: Blane Bramble: "Re: SPF = Sender Policy Framework"
- Previous message: Dave Uhring: "Re: SPF = Sender Policy Framework (was: Microsoft spam solution<snip>)"
- In reply to: Bill Cole: "Re: SPF = Sender Policy Framework (was: Microsoft spam solution<snip>)"
- Next in thread: Murray Watson: "Re: SPF = Sender Policy Framework (was: Microsoft spam solution<snip>)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 20 Sep 2004 11:51:46 -0700
Bill Cole <bill@scconsult.com> wrote in message news:<bill-0B3B04.07041620092004@toaster.scconsult.com>...
> There is a free-standing A record carried by each TLD root for each
> authoritative nameserver used by domains in the TLD. It used to be that
> you had to register those nameservers as a separate process from domain
> registration, but now it seems that the registry records get created
> every time a new authoritative server is referenced by a domain record.
The registrars still have to explicitly register the nameservers.
They probably hide it from the users, though. The only thing that has
changed in regard to .com/.net glue records is that Verisign now
allows the same IP address to be listed many times with different host
names. Previously, a strict 1-1 relationship was preserved.
- Next message: Blane Bramble: "Re: SPF = Sender Policy Framework"
- Previous message: Dave Uhring: "Re: SPF = Sender Policy Framework (was: Microsoft spam solution<snip>)"
- In reply to: Bill Cole: "Re: SPF = Sender Policy Framework (was: Microsoft spam solution<snip>)"
- Next in thread: Murray Watson: "Re: SPF = Sender Policy Framework (was: Microsoft spam solution<snip>)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|