Dick St.Peters wrote:
wayne writes:
If they were *really* concerned about DNS loads, they would publish
TXT records with a long TTL. Or, better, locate their name servers
somewhere else where the traffic isn't a problem.
This just makes the problem worse. For example, if you're an African
company, you don't want your communication with your African
correspondents to require trans-Atlantic DNS queries.
Perhaps location of DNS servers is still a hot debate.
But publishing records with a long TTL is something that should be done
in the first place where bandwidth is so sensitive, caching is the very
key to bandwidth reduction. Unless we are talking about a domain name
whose DNS records change a lot. But I think not.
Terry Fielder
terry(_at_)greatgulfhomes(_dot_)com
Associate Director Software Development and Deployment
Great Gulf Homes / Ashton Woods Homes
Fax: (416) 441-9085
--
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
-------
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