Re: The state of DNS support, was Deprecating SPF

"John R Levine" <[email protected]> writes:

> Right, but the web provisioning crudware that people use in front of
> BIND generally can't handle anything other than A, MX, CNAME, and TXT,
> so for anything else you have to get someone with direct access to the
> host to edit the master file.  Like I said, sounds just the same.

There are some GUI tools that don't, there are some that do support SPF
(and other 'new' RR types). Good IETF standards can help customers to
make the right purchase decisions and give incentive to
vendors/programmers to implement support for 'new' RR types.

The current support in GUI tools should not be the guide for a standards
discussion.

As a teacher teaching DNS classes, I found that most of the students
coming to class have never heard of the SPF record (although most of
them deploy SPF with TXT records). The web is full of SPF tutorials
using TXT records that will never be updated.

The new warnings in BIND 9.9 (warns if TXT-SPF is in zone, but no SPF
RR) is a low cost, very effective way to inform DNS admins about the
exsistence of the SPF record, and a warning message in the logs is
incentive for many DNS admins to look up information on SPF records, and
then deploy the SPF record.

Only a few DNS admins have updated to BIND 9.9 by now, I'm curious about
the effect once BIND 9.9 will be in the big Linux server distros
(RedHat, Ubuntu-Server, SLES ...). Maybe the SPF to TXT ration will
change when that happens. 

-- Carsten

_______________________________________________
dnsext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsext