Hello,
One of our treasured old machines needs TLS version upgraded particularly to avoid SMTP
handshake failures that have started to crop up.
This machine also runs FRED registry operations that we use for many activities like training,
whois, invoicing, etc.
I would hence really like to find out in advance if upgrading TLS version will break FRED.
Will upgrading openssl break FRED ?
Regards,
Paulos
=============================
Dr Paulos B Nyirenda
NIC.MW & .mw ccTLD
http://www.nic.mw
SDNP: http://www.sdnp.org.mw
Tel: +265-(0)-882 089 166
Cell: +265-(0)-888-824787
WhatsApp: +265-(0)-887386433
--
This email has been checked for viruses by AVG.
https://www.avg.com
Happy new year everyone,
We have been successfully developing FRED 2.40.3 over Ubuntu 16.04 which is the documented deployment libraries’ OS requirement. For our final deployment, we are looking at the possibility of deploying over a higher version of Ubuntu (either 18.04 or 20.04) because Ubuntu 16.04 is scheduled for EOL in April 2021. (https://ubuntu.com/about/release-cycle).
Before we go down the hairy path of testing internally, we would like to know if any issues have been reported about installing FRED over Ubuntu 18.04 or 20.04? Or if anyone can testify that it has worked for them?
Thanks and regards,
Kelvin
Hello,
Hope this finds you well in these troubled times.
We have a persistent request from a registrar asking us to "confirm what our balance was on
the 1st of December 2019" ... about 12 montsh ago.
We have repeatedly told the registrar that by the nature of EPP transactions on a registry
running FRED, we do not keep such balances on the registry on a day to day basis except in
regular backups of the database.
I would like to hear what you think about such a request from a registrar which connects to a
registry running the FRED registry system and how you would respond to it.
Is there an easier way of dealing with such a request other than by remounting a whole
FRED database on a test server from a previous FRED backup of that date ?
Remounting a FRED database backup is a major task and we have told them that if they
insist then we would raise a fee or charge for it.
Any help?
Regards,
Paulos
=============================
Dr Paulos B Nyirenda
NIC.MW & .mw ccTLD
http://www.nic.mw
SDNP: http://www.sdnp.org.mw
Tel: +265-(0)-882 089 166
Cell: +265-(0)-888-824787
WhatsApp: +265-(0)-887386433
--
This email has been checked for viruses by AVG.
https://www.avg.com
Hello FRED team
I've skimmed the FRED docs and AFAICT there's no distribution in form of Docker image(s).
Does anyone have plans "dockerizing" FRED?
(Please don't get me wrong, I'm not trying to make any sort of pressure that anyone has to do
something, I'm just asking and that's it.)
Thank you
Piotr
.mw Registrar,
GDPR compliance test phase on .mw - invitation
========================================
I am pleased to advise that the Malawi .mw ccTLD registry on FRED has started a test phase
for compliance on GDPR compliance for all and we would like to invite you to assist us to
test.
We have now mounted a test server to handle both EPP and WHOIS on ngoli3.sdnp.org.mw
that you can test right away.
A WHOIS query for any of your existing domains will show that we are now hiding details on
the e-mail, phone, fax and other details while showing name, organisation, address, DNS
servers.
The database on the test server is that of 24 July 2020. You can compare the following:
1. Current WHOIS at: http://www.registrar.mw/whois-intro.php
2. Current command line WHOIS: $whois domains.mw -h ngoli.sdnp.org.mw
3. GDPR compliant test : http://ngoli3.sdnp.org.mw/whois
4. GDPR compliant command line test: $whois domains.mw -h ngoli3.sdnp.org.mw
You can also test creating a new contact using EPP and you will find that the default is "hide"
on the above details and it is up to the registrar to toggle this to "disclose" as needed.
Please make sure that your EPP client is capable of handling the .mw GDPR complaint
environment as you continue to conduct your business using the .mw registry.
We will have this test phase running for at least two week from 1 August 2020 after which we
will make a decision to move this test phase to the production environment. All modifications
that you make on the test environment will be deleted and lost from ngoli3 at the end of the
test phase, so, you can test as much as you need to without charge.
Please let me know if you face any problems using the new GDPR compliant test .mw
registry on EPP, WHOIS or any other service. These steps are very important to us.
Regards,
Dr Paulos B Nyirenda
NIC.MW & .mw ccTLD
http://www.nic.mw
Tel: +265-(0)-882 089 166
Cell: +265-(0)-888-824787
WhatsApp: +265-(0)-887386433
--
This email has been checked for viruses by AVG.
https://www.avg.com
Hello,
As our list of registrars has grown, we are regularly getting a request from a registrar to
"Please send me a list of domains under our registrar account with their expiry dates"
As a registry using FRED registry, how do you handle such requests?
We have so far just directed them to use the command list_domains under fred-client BUT
we would like to here if others are handling this in a different or better way.
Many of our new registrars are at the point of learning how to be a good registrar and so
they often ask us for help like this.
Regards,
Paulos
======================
Dr Paulos B Nyirenda
NIC.MW & .mw ccTLD
http://www.registrar.mw
Tel: +265-(0)-882 089 166
Cell: +265-(0)-888-824787
WhatsApp: +265-(0)-887386433
--
This email has been checked for viruses by AVG.
https://www.avg.com
Hi everyone,
Our domains that expired in February and March are stuck in "to be deleted"
state, they never get deleted.
On manual deletion or renewal the output is:
Error: ObjectStatusProhibitsOperation
Manual run of '/usr/sbin/fred-admin --object_regular_procedure' executes but
doesn't give any output. Zones are still being generated with such 'to be
deleted' domains excluded.
The timezone is set to UTC in postregsql.conf
Enum_parameters are as follows:
expiration_notify_period -30
expiration_dns_protection_period 30
expiration_letter_warning_period 34
validation_notify1_period -30
validation_notify2_period -15
regular_day_procedure_period 0
object_registration_protection_period 6
handle_registration_protection_period 0
regular_day_outzone_procedure_period 14
outzone_unguarded_email_warning_period 25
enum_validation_continuation_window 14
regular_day_procedure_zone Africa/Johannesburg
expiration_registration_protection_period 61
What could be the cause of this?
Regards.
Moeketsi
Hi,
We try to install Fred for review features and start to use product. For
installation we use link —
https://fred.nic.cz/documentation/html/AdminManual/Installation/BinsUbuntu.…
(1.2.2). But can't pass step 7.
We got dependencies error (see below). fred-webwhois-apache needs
*1.17.0-1~xenial+1*, but maximal package that I found on archive.nic.cz
is *1.16.1-1~xenial+1*. How to resolve this problem?
Sincerely, Lem
*/root@fred:~# apt install fred-webwhois-apache /*/
/
/Reading package lists... Done/
/Building dependency tree /
/Reading state information... Done/
/Some packages could not be installed. This may mean that you have/
/requested an impossible situation or if you are using the unstable/
/distribution that some required packages have not yet been created/
/or been moved out of Incoming./
/The following information may help to resolve the situation:/
/The following packages have unmet dependencies:/
/ fred-webwhois-apache : Depends: fred-webwhois (=
1.17.0-1~xenial+1) but 1.16.1-1~xenial+1 is to be installed or/
/ fred-webwhois-py3 (=
1.17.0-1~xenial+1) but it is not going to be installed/
/E: Unable to correct problems, you have held broken packages./
*/root@fred:~# lsb_release -a/*
/No LSB modules are available./
/Distributor ID: Ubuntu/
/Description: Ubuntu 16.04.6 LTS/
/Release: 16.04/
/Codename: xenial/