Here's a couple of newbie questions that I couldn't find the answers to in
either your draft RFC or the FAQ, though I'm sure it's in there somewhere.
First question:
Does the SPF record go in the DNS of the domain registrar or the domain
hosting service? For example, my domain is registered at GoDaddy.com and
hosted at Interland. As one of the .com TLD registrars, GoDaddy points to
Interland's nameservers as authoritative for my domain. Where does the SPF
record belong?
Interland has so far refused to even consider SPF, has refused to tell me
the CIDR range that their few dozen outgoing MX's share (besides their
entire /14) and has also refused to create any TXT records to support SPF.
I assume that they will eventually come around, so I would like to come up
with a suitable SPF record.
Hence, my second question:
Though I don't have a reasonable CIDR range for their outgoing MX's, there
is a consistent naming structure that I could take advantage of with the PTR
mechanism. Their outgoing MX's are always named like:
mail[xx].atl.registeredsite.com
where the [xx] represents one or more decimal digits, for example:
mail4.atl.registeredsite.com
Rather than just using:
v=spf1 ptr:registeredsite.com -all
which is a whole /14, or the slightly better:
v=spf1 ptr:atl.registeredsite.com -all
I would like to use a macro in an SPF record to describe the MX names more
precisely. My idea is to use the *DIGIT macro feature, perhaps something
like
v=spf1 ptr:mail%{1}.atl.registeredsite.com -all
However, the draft RFC does not give any examples of expanding a macro
including *DIGIT, though that function is described. Would this SPF record
work with the MX name structure I gave? I can see that *DIGIT was meant for
extracting the parts of a dotted quad, but I hope it is applicable to this
problem, as well. I think an example in the draft RFC of how *DIGIT expands
might be helpful, particularly how it puts the separator back in or doesn't
and if it can be used for something other than a dotted quad.
My local ISP, whom I send some outgoing mail through, also uses a similar
naming scheme for their outgoing MX's, so I suspect that a solution to this
would be useful to others.
--
Seth Goodman
off-list replies to sethg [at] GoodmanAssociates [dot] com
-------
Sender Permitted From: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Latest draft at http://spf.pobox.com/draft-mengwong-spf-02.9.4.txt
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname(_at_)©#«Mo\¯HÝÜîU;±¤Ö¤Íµø?¡