Let's Encrypt Subscriber Agreement Update

2022-08-04 Thread noreply
Dear Let's Encrypt Subscriber:

We've updated our Subscriber Agreement, effective September 21, 2022. This is 
the agreement that governs the relationship between you and ISRG with regards 
to your acquisition and use of SSL/TLS digital certificates issued by ISRG (via 
Let's Encrypt). You don't need to take any action to continue to use the Let's 
Encrypt service but we encourage you to review the new agreement.

The main updates are: we now link to instructions on choosing a revocation 
reason if you revoke a certificate. This is a requirement for Subscriber 
Agreements from all Certificate Authorities as of this year. Also, we've 
removed unneeded capitalization, removed a section that is redundant with our 
Certificate Policy (CP), and tweaked the wording of the requirement to "assure" 
control of your private key so it matches the Baseline Requirements (BRs).

You can find the updated agreement (v1.3), along with a document that shows the 
differences between the previous and current agreement and the full text of the 
previous agreement here:

https://letsencrypt.org/repository/

If you have any questions about the new agreement, please ask on our community 
forums:

https://community.letsencrypt.org/

Let's Encrypt is a free service because we want to make the Web more secure and 
privacy-respecting for everyone. We're able to operate as a nonprofit thanks to 
corporate sponsorships and donations. Please consider joining our sponsorship 
program:

https://www.abetterinternet.org/sponsor/

Or donate now during our summer fundraising campaign to support this service 
(and get neat Let's Encrypt apparel!).

https://letsencrypt.org/donate/

Thank you,

The Let's Encrypt Team


Let's Encrypt - Change for older browsers/devices

2021-05-19 Thread noreply
Hello from the staff at Let's Encrypt.

On September 30, there will be a change in how older browsers and 
devices trust Let's Encrypt certificates, resulting in a minor decrease 
in compatibility. If you run a typical website, you won't notice a 
difference. Devices and browsers running up-to-date software will 
continue working fine, and we've taken steps to make sure the vast 
majority of older devices will too. If you run a large website, or need 
to support less common software (particularly non-browser software), 
you'll want to read about the details at:

https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/

In either case, no action is required from you. We're letting you know 
so you can provide answers to any questions your site visitors may have.

Here is a sample hostname from one of your current Let's Encrypt 
certificates:  *.spamassassin.org 

Since 2015 we've served the world with 1.6 billion free certificates, 
each one providing security and privacy to people on the Web. It's work 
that's 100% funded by charitable donations since we are a nonprofit. If 
your company is interested in sponsorship, please email 
spon...@letsencrypt.org. If you can make a donation, we ask that you 
consider supporting our work today: https://letsencrypt.org/donate/ 
Thank you.

- The Let's Encrypt team

If you are receiving this email in error, unsubscribe at:
  
http://delivery.letsencrypt.org/track/unsub.php?u=30850198=06c17feadf984c20a72a26ed155e6781.bwhb%2FBPfWM93iQ5gciTRITHDm2Y%3D=https%3A%2F%2Fmandrillapp.com%2Funsub%3Fmd_email%3Ds%252A%252A%252A%252A%2540s%252A%252A%252A%252A.%252A%252A%252A
Please note that this would also unsubscribe you from other Let's Encrypt 
service notices, like expiration reminders.


Action required: Let's Encrypt certificate renewals

2019-01-29 Thread noreply
Hello,

Action may be required to prevent your Let's Encrypt certificate renewals
from breaking.

If you already received a similar e-mail, this one contains updated
information.

Your Let's Encrypt client used ACME TLS-SNI-01 domain validation to issue
a certificate in the past 60 days. Below is a list of names and IP
addresses validated (max of one per account):

 ruleqa.spamassassin.org (62.210.60.231) on 2018-11-23

TLS-SNI-01 validation is reaching end-of-life. It will stop working
temporarily on February 13th, 2019, and permanently on March 13th, 2019.
Any certificates issued before then will continue to work for 90 days
after their issuance date.

You need to update your ACME client to use an alternative validation
method (HTTP-01, DNS-01 or TLS-ALPN-01) before this date or your
certificate renewals will break and existing certificates will start to
expire.

Our staging environment already has TLS-SNI-01 disabled, so if you'd like
to test whether your system will work after February 13, you can run
against staging: https://letsencrypt.org/docs/staging-environment/

If you're a Certbot user, you can find more information here:
https://community.letsencrypt.org/t/how-to-stop-using-tls-sni-01-with-certbot/83210

Our forum has many threads on this topic. Please search to see if your
question has been answered, then open a new thread if it has not:
https://community.letsencrypt.org/

For more information about the TLS-SNI-01 end-of-life please see our API
announcement:
https://community.letsencrypt.org/t/february-13-2019-end-of-life-for-all-tls-sni-01-validation-support/74209

Thank you,
Let's Encrypt Staff


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-18 Thread noreply

3.3.3.updates (TXT) -> \"1815645\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-17 Thread noreply

3.3.3.updates (TXT) -> \"1815556\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-16 Thread noreply

3.3.3.updates (TXT) -> \"1815422\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-15 Thread noreply

0.4.3.updates (TXT) -> \"1815297\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-15 Thread noreply

2.3.3.updates (TXT) -> \"1815297\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-15 Thread noreply

3.3.3.updates (TXT) -> \"1815297\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-14 Thread noreply

3.3.3.updates (TXT) -> \"1815188\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-14 Thread noreply

1.3.3.updates (TXT) -> \"1815211\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-14 Thread noreply

0.3.3.updates (TXT) -> \"1815211\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-14 Thread noreply

2.3.3.updates (TXT) -> \"1815211\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-14 Thread noreply

3.3.3.updates (TXT) -> \"1815211\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-13 Thread noreply

0.3.3.updates (TXT) -> \"1815062\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-13 Thread noreply

1.3.3.updates (TXT) -> \"1815062\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-12 Thread noreply

3.3.3.updates (TXT) -> \"1815002\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-10 Thread noreply

3.3.3.updates (TXT) -> \"1814822\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-09 Thread noreply

3.3.3.updates (TXT) -> \"1814708\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-08 Thread noreply

3.3.3.updates (TXT) -> \"1814560\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-06 Thread noreply

3.3.3.updates (TXT) -> \"1814390\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-05 Thread noreply

3.3.3.updates (TXT) -> \"1814340\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-03 Thread noreply

3.3.3.updates (TXT) -> \"1814142\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-11-02 Thread noreply

3.3.3.updates (TXT) -> \"1814048\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-27 Thread noreply

3.3.3.updates (TXT) -> \"1813484\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-26 Thread noreply

3.3.3.updates (TXT) -> \"1813376\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-25 Thread noreply

3.3.3.updates (TXT) -> \"1813258\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-24 Thread noreply

3.3.3.updates (TXT) -> \"1813149\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-22 Thread noreply

3.3.3.updates (TXT) -> \"1812887\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-21 Thread noreply

3.3.3.updates (TXT) -> \"1812812\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-20 Thread noreply

3.3.3.updates (TXT) -> \"1812723\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-19 Thread noreply

3.3.3.updates (TXT) -> \"1812604\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-18 Thread noreply

3.3.3.updates (TXT) -> \"1812474\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-17 Thread noreply

3.3.3.updates (TXT) -> \"1812374\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-16 Thread noreply

3.3.3.updates (TXT) -> \"1812259\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-15 Thread noreply

3.3.3.updates (TXT) -> \"1812214\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-14 Thread noreply

3.3.3.updates (TXT) -> \"1812173\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-13 Thread noreply

3.3.3.updates (TXT) -> \"1812080\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-12 Thread noreply

3.3.3.updates (TXT) -> \"1811919\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-09 Thread noreply

3.3.3.updates (TXT) -> \"1811538\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-08 Thread noreply

3.3.3.updates (TXT) -> \"1811460\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-06 Thread noreply

3.3.3.updates (TXT) -> \"1811305\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-05 Thread noreply

3.3.3.updates (TXT) -> \"1811170\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-04 Thread noreply

3.3.3.updates (TXT) -> \"1811050\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-03 Thread noreply

3.3.3.updates (TXT) -> \"1810669\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-02 Thread noreply

3.3.3.updates (TXT) -> \"1810310\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-10-01 Thread noreply

3.3.3.updates (TXT) -> \"1810251\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-30 Thread noreply

3.3.3.updates (TXT) -> \"1810182\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-29 Thread noreply

3.3.3.updates (TXT) -> \"1810071\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-28 Thread noreply

3.3.3.updates (TXT) -> \"1809961\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-26 Thread noreply

3.3.3.updates (TXT) -> \"1809720\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-25 Thread noreply

3.3.3.updates (TXT) -> \"1809591\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-23 Thread noreply

3.3.3.updates (TXT) -> \"1809377\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-22 Thread noreply

3.3.3.updates (TXT) -> \"1809277\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-21 Thread noreply

3.3.3.updates (TXT) -> \"1809130\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-20 Thread noreply

3.3.3.updates (TXT) -> \"1808973\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-19 Thread noreply

3.3.3.updates (TXT) -> \"1808842\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-18 Thread noreply

3.3.3.updates (TXT) -> \"1808672\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-16 Thread noreply

3.3.3.updates (TXT) -> \"1808524\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-15 Thread noreply

3.3.3.updates (TXT) -> \"1808433\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-11 Thread noreply

3.3.3.updates (TXT) -> \"1807999\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-10 Thread noreply

3.3.3.updates (TXT) -> \"1807940\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-09 Thread noreply

3.3.3.updates (TXT) -> \"1807858\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-08 Thread noreply

3.3.3.updates (TXT) -> \"1807679\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-07 Thread noreply

3.3.3.updates (TXT) -> \"1807571\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-06 Thread noreply

3.3.3.updates (TXT) -> \"1807450\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-05 Thread noreply

3.3.3.updates (TXT) -> \"1807320\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-04 Thread noreply

3.3.3.updates (TXT) -> \"1807196\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-03 Thread noreply

3.3.3.updates (TXT) -> \"1807127\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-02 Thread noreply

3.3.3.updates (TXT) -> \"1807030\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-09-01 Thread noreply

3.3.3.updates (TXT) -> \"1806897\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-31 Thread noreply

3.3.3.updates (TXT) -> \"1806763\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-29 Thread noreply

3.3.3.updates (TXT) -> \"1806536\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-27 Thread noreply

3.3.3.updates (TXT) -> \"1806343\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-26 Thread noreply

3.3.3.updates (TXT) -> \"1806274\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-24 Thread noreply

3.3.3.updates (TXT) -> \"1806003\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-22 Thread noreply

3.3.3.updates (TXT) -> \"1805731\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-20 Thread noreply

3.3.3.updates (TXT) -> \"1805539\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-19 Thread noreply

1.3.3.updates (TXT) -> \"1805491\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-19 Thread noreply

0.4.3.updates (TXT) -> \"1805491\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-19 Thread noreply

3.3.3.updates (TXT) -> \"1805491\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-18 Thread noreply

2.3.3.updates (TXT) -> \"1805375\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-18 Thread noreply

1.3.3.updates (TXT) -> \"1805375\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-18 Thread noreply

3.3.3.updates (TXT) -> \"1805375\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-18 Thread noreply

0.3.3.updates (TXT) -> \"1805375\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-17 Thread noreply

0.3.3.updates (TXT) -> \"1805267\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-17 Thread noreply

2.3.3.updates (TXT) -> \"1805267\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-17 Thread noreply

0.4.3.updates (TXT) -> \"1805267\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-17 Thread noreply

3.3.3.updates (TXT) -> \"1805267\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-17 Thread noreply

1.3.3.updates (TXT) -> \"1805267\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-16 Thread noreply

0.3.3.updates (TXT) -> \"1805150\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-16 Thread noreply

2.3.3.updates (TXT) -> \"1805150\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-16 Thread noreply

1.3.3.updates (TXT) -> \"1805150\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-15 Thread noreply

0.3.3.updates (TXT) -> \"1805059\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-15 Thread noreply

0.4.3.updates (TXT) -> \"1805059\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-14 Thread noreply

1.3.3.updates (TXT) -> \"1804953\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-13 Thread noreply

1.3.3.updates (TXT) -> \"1804883\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-13 Thread noreply

0.3.3.updates (TXT) -> \"1804883\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-12 Thread noreply

1.3.3.updates (TXT) -> \"1804861\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-12 Thread noreply

3.3.3.updates (TXT) -> \"1804861\"

File /usr/local/bin/updateDNS.disabled exists, not updating DNS.


  1   2   3   >