On Sat, 8 May 2004, DJ Coster wrote:
So when I type something like www.cnn.com in my browser it really first
tries www.cnn.com.mydomian.com. That fails so it tries to find
www.cnn.com.com which also fails. And lastly tries www.cnn.com which it
finds.
Actually, web browsers very rarely apply the search domain first, if at
all. A resolver stack itself might, but the web browser, when you type in
"www.cnn.com", will assume you really mean www.cnn.com, and look up
"www.cnn.com." using the resolver. It then might apply other
permutations, such as adding www to the front and com/net/org to the end,
if that lookup fails.
Your point still potentially applies, but it is very much implementation
dependent. The spec should probably say one way or the other about how
SPF implementations should handle unqualified domains in that particular
context.
Tim Wilde
--
Tim Wilde
twilde(_at_)dyndns(_dot_)org
Systems Administrator
Dynamic Network Services, Inc.
http://www.dyndns.org/