On Tue, May 27, 2008 at 10:36 AM, Dave Crocker <dhc(_at_)dcrocker(_dot_)net>
wrote:
Eliot Lear wrote:
The problem is when there are hundreds or thousands of hosts beneath
example.com. How many commercial DNS management systems can handle that
from a provisioning point of view?
All.
How else did they register those names and populate them with records?
Implementation of SPF and DK faced similar challenges, and there are
still some registrars that provide DNS services that don't support
batch updates or the right kind of record types. I don't know that it
has been that huge of an adoption barrier overall. And it leaves those
services at a competitive disadvantage, if they don't modify their DNS
administration tools. I've seen registrars update their tools to
support these, and I've seen registrars ignore them. I've guided
clients away from the latter and toward the former. I suspect I'm not
the only one.
I guess my overwhelming point here is that I don't think that the
limitation of certain tools is really a stumbling block. And keep in
mind that we're talking about *certain* tools, because there are
others that would handle this kind of thing just fine.
Regards,
Al Iverson
--
Al Iverson on Spam and Deliverability, see http://www.spamresource.com
News, stats, info, and commentary on blacklists: http://www.dnsbl.com
My personal website: http://www.aliverson.com -- Chicago, IL, USA
Remove "lists" from my email address to reach me faster and directly.
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html