Can't modify an existing SPF record

[Greg Choules]

The SPF record type was deprecated in 2014 and the SPF definition string
*must* now be contained as data in a TXT record.
BIND will still load a zone containing SPF records, but it will check
whether a TXT record also exists that contains the same string and will
generate a log message telling you if it doesn't find one.

>From a quick glance at the webmin manual it *should* allow you to put
anything you like in a TXT record.
@Roberto Carna <robertocarna36 at gmail.com>  your SPF record currently looks
like this:

company.com. 971 IN TXT "v=spf1 mx ip4:[corpIP] include:mktomail.com ~all"


The ip4:[corpIP] will not work. [] are not valid characters in the SPF
specification and in any case ip4: must be followed by a literal dotted
decimal IPv4 address.

On Fri, 8 Jul 2022 at 17:34, Benny Pedersen <me at junc.eu> wrote:

> On 2022-07-08 18:14, Crist Clark wrote:
> > As far as BIND is concerned, this is arbitrary text in a TXT record.
> > It doesn’t know or care about SPF syntax within it.
>
> TXT records is mostly used, and SPF records is in bind supported
> --
> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
> from this list
>
> ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
>
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20220708/53044267/attachment.htm>