Re: Secondary DNS Changes - update needed on your end.

[Sidney Markowitz <si...@sidney.com>]

[This email is Bcc'd to earlier recipients as I am now moving the discussion
to the public dev@ mailing list]

This thread got started on the private SpamAssassin PMC mailing list when we
were notified there of a required infrastucture update for our DNS. In keeping
with Apache Software Foundation policy that all project business  that does
not require confidentiality be on a public mailing list, I am posting this
here on dev@.

On looking into it I have found that committers have the ability to do the
required update to our DNS configuration by following the procedures in the
README file

https://svn.apache.org/repos/asf/spamassassin/dns/README

I'll take care of it, and will also update the information that is on
https://wiki.apache.org/spamassassin/InfraNotes
to include a section on maintaining our DNS configuration.

 Sidney

> Dear Sonic Customer, You are receiving this notice because you have been
> using Sonic's Secondary DN
>
> Dear Sonic Customer,
>
> You are receiving this notice because you have been using Sonic's Secondary
> DNS Service for your domain or domains:
>
> spamassassin.org
>
> Sonic is in the process of updating our DNS server infrastructure. To
> continue using Sonic Secondary DNS Service, you will need to update your
> DNS master server as follows:
>
> * Remove references to the retired secondary master server at 64.142.8.20
> and notify server at 64.142.100.92
> * Add the new secondary master and notify server IP address with the new
> address 184.23.168.134
>
> You will need to complete your changes by no later than midnight, August 15,
> 2016.
>
> For more information including an example BIND zone configuration, please
> view the following page:
> Sonic Wiki: Secondary DNS Service
>
> Please do not hesitate to contact us with any questions by replying to this
> email or by telephone at (707) 237-6211 during normal business hours.
>
> Regards,
> Sonic Operations Department
>