-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Scott Kitterman wrote:
Is this record broken?
godaddy.com text "v=spf1 a:69.64.33.132 a:66.98.160.100 a:64.202.160.108
ip4:64.202.167.0/24 ip4:64.202.166.0/24 ip4:64.202.165.0/24
ip4:64.202.163.0/24 ip4:64.202.189.0/24 ~all"
a: with an IP address is a syntax error isn't it?
Syntactically, 69.64.33.132 is a valid domain name. The record as a whole
is syntactically and semantically correct, although it probably doesn't
mean what the publisher meant. Since there is no "132" top-level domain,
"a:69.64.33.132" will yield a lookup result of RCODE 3, thus such an "a"
mechanism will simply not match, as per the last paragraph of the
introduction of section 5 in the specification.
What apparently happened here is that the publisher erroneously assumed the
"a" mechanism to be for single IP addresses, and the "ip4" mechanism for
whole blocks of IP addresses.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFCgTaGwL7PKlBZWjsRAkOuAKC3HOFDvKoU2aoJTVEIJl+35kQ/6ACfUPh8
S5KKYaflyGzGu88el62SJSw=
=0SjF
-----END PGP SIGNATURE-----