-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Florian Weimer wrote:
* Scott Kitterman:
Interesting. One quick comment for you...
enyo.de. 3600 IN TXT ("v=spf1 a:212.9.189.167 "
"a:212.9.189.169 -all")
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
record.
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.
dtaylor(_at_)vocalabs(_dot_)com http://www.vocalabs.com/
(952)941-6580x203
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC+18v8/QSptFdBtURAts5AJwNULgApDav+ef7tZ+IddUQGdRr8gCeLfJN
qWSFzO2kY3A2kNpopuLS3jM=
=22zp
-----END PGP SIGNATURE-----