Julian Mehnle writes:
I recognize that SPF is not strictly backwards-compatible in this case.
However, their behavior is really brain-dead, and the consequences ought
to be expected. The correct solution would be to respond with a "zero
answers" DNS packet and _NOT_ be charged for such DNS responses.
Keep in mind that in some cases the reason for the DNS query charge is
that there are per-packet or per-byte charges for traffic to/from some
places, mostly relatively remote places involving expensive
trans-oceanic or satellite links.
I think New Zealand traffic is charged on a usage basis, although I
suspect the usage charge is absorbed by local NZ ISPs as a cost of
doing business and is not passed on to NZ end-users as a bandwidth
usage charge. In some places in Africa, the traffic charge is passed
on to end-users.
I'd be curious to know where Stuart's client being charged for DNS
queries is located.
--
Dick St.Peters, stpeters(_at_)NetHeaven(_dot_)com
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com