-----BEGIN PGP SIGNED MESSAGE-----
Florian Weimer wrote:
* Scott Kitterman:
Interesting. One quick comment for you...
enyo.de. 3600 IN TXT ("v=spf1 a:22.214.171.124 "
won't give you what you want. The 'a' mechanism takes a domain name
arguement, not a IP address.
Oops, thanks. These bugs should be fixed.
Why not just activate the new IP, add a second A record for
mail.enyo.de and then delete the first one after you are sure that
TTLs have expired?
Yes, my example misses the point. I need something which actually
requires a change in the published SPF record.
On the contrary, since you have an example of something which
does not require a change in the SPF record it can be converted
into a positive example of how to write a DNS lag tolerant SPF
It is the ip4: mechanism that is intolerant of DNS lag, since
it saves lookups at the cost of re-encoding information.
Daniel Taylor VP Operations Vocal Laboratories, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----