On Thu, Oct 16, 2008 at 01:08:09PM -0600, Peter Saint-Andre wrote:
> I did a bit of research on this. I propose the following text
> (specifically the parenthetical clause):
>
> The result of the SRV lookup will be one or more combinations of
> a port and hostname, which hostnames the initiating entity MUST
> resolve according to returned SRV record weight (if the result of
> the SRV lookup is a single RR with a Target of ".", i.e. the root
> domain, the initiating entity MUST abort SRV processing but
> SHOULD attempt a fallback resolution as described below).
IMHO giving up the domain is a better choice. AFAIR SRV target of "."
is supposed to say "no such service at this address".
When a domain has only an A record, that any service may be running there. If
we do not want XMPP servers to poke the XMPP port and we have no XMPP server
for that domain how do we do that? Using SRV record pointing to "." seems
right to me and if I publish it I don't want the servers still try to use the
A record.
And RFC2782 clearly says:
A Target of "." means that the service is decidedly not
available at this domain.
So, if we know the service is "decidely not available" then IMHO means that we
MUST NOT attempt to contact the service anyway.
Greets,
Jacek
