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/
Hi!
We have announced a new release at last:
https://fred.nic.cz/en/news/version-2-40-released/
Please, report if you have any trouble with the installation procedures
using packages for Ubuntu or Fedora.
If you have any questions, I'm sure our guys will be happy to answer them :)
Greetings,
Lena
Guarantor of Docs for FRED
Hello,
I would like to find out if and how we can get a cc of every notification e-mail in FRED to go to
a designated e-mail address for the attention or analysis of someone who adminsiters the
FRED registry.
I am aware that these e-mail notifications are archived in the FRED database but in our case
the persons monitoring the registry do not have access to the database - and they should not
have such sensitive access anyway
The mailer config in FRED in our case is in /etc/fred/pyfred.conf and it does not give an
option for such a cc address.
If you worried about this or have or found a solution to it please let us know.
Regards,
Paulos
======================
Dr Paulos B Nyirenda
NIC.MW & .mw ccTLD
http://www.registrar.mw
---
This email has been checked for viruses by AVG.
https://www.avg.com
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Hi,
I want to install FRED but would like some guidance when it comes to which Linux Distro I should use.
According to the documentation I could use Ubuntu 16.04 LTS (Xenial Xerus), Fedora 24, Fedora 25, RHEL 7 or CentOS 7 but if I don't have any special preferences which one is most fitting for the latest stable version of FRED?
Would be eternally thankful if any helpful soul could point me in the right direction.
Best regards
Johan Olsson
Hi,
after some time we are announcing a new version of FRED. As usually
release notes are published here:
https://fred.nic.cz/documentation/html/ReleaseNotes/
We have intentionally not announced version 2.37 since this version was
changing hardcoded default for WHOIS disclose flags from "everything is
by default public" to "everything is by default hidden" of course
because of GDPR. New default was again hardcoded and immediate upgrade
could cause issue to registrars that relies on default policy. With
version 2.38 this default policy is configuration option so registry
has control when this policy change based on discussion with
registrars. All the information should be seen from documentation.
I'd like to pick one change from release notes to write about little
bit more and this is handling incoming payments. We are trying to make
FRED even more modular and move all about payments and invoices into
separated module. There is background idea that at some point in time,
this module could be replaced with generic accounting software that
will take care of issuing invoices which should not be responsibility
of registry. For now, the only visible change is that tab payments
disappears from web administration interface (Daphne) and also
associated database tables bank_payment and bank_statement are not
required. My assumption is that this change doesn't have effect for any
instance but in case it has, there is a new component called Pain (from
"payments and invoices") that provides the same functionality but needs
to be installed as additional thing. Feel free to ask more about this
if you'd like to try it.
Regards,
Jaromir
--
Jaromir Talir
Technicky partner / Technical Fellow
-------------------------------------------
CZ.NIC, z.s.p.o. -- .cz domain registry
Milesovska 5, 130 00 Praha 3, Czech Republic
mailto:jaromir.talir@nic.cz http://nic.cz/
sip:jaromir.talir@nic.cz tel:+420.222745107
mob:+420.739632712 fax:+420.222745112
-------------------------------------------
Greetings,
I have a fresh install of FRED 2.35.0 on Ubuntu Server 16.04 LTS but the
services can't seem to start, only fred-pyfred is active.
The ExecStart commands like: /usr/sbin/fred-rifd -ORBendPoint giop:tcp::2224
-ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-rifd.conf exit with
failure of Error: CORBA NameService not running.
/usr/sbin/fred-adifd
-ORBendPoint giop:tcp::2222 -ORBnativeCharCodeSet UTF-8 --config
/etc/fred/fred-adifd.conf exit with failure of Error: CORBA NameService not
running.
/usr/sbin/fred-pifd -ORBendPoint giop:tcp::2223 -ORBnativeCharCodeSet UTF-8
--config /etc/fred/fred-pifd.conf exit with failure of Error: CORBA
NameService not running.
/usr/sbin/fred-logd -ORBendPoint giop:tcp::2226 -ORBnativeCharCodeSet UTF-8
--config /etc/fred/fred-logd.conf exit with failure of Error: CORBA
NameService not running.
/usr/sbin/fred-msgd -ORBendPoint giop:tcp::2228 -ORBnativeCharCodeSet UTF-8
--config /etc/fred/fred-msgd.conf exit with failure of Error: CORBA
NameService not running.
/usr/sbin/fred-rsifd -ORBendPoint giop:tcp::2234 -ORBnativeCharCodeSet UTF-8
--config /etc/fred/fred-rsifd.conf exit with failure of Error: CORBA
NameService not running.
The fred-webadmin log when running /usr/bin/fred-webadmin is as follows:
omniORB: (0) 2019-01-16 08:03:11.886060: ERROR! omniORBpy version 4.2
expects stubs version 4.2. Stubs in
/usr/lib/python2.7/dist-packages/CosNaming_idl.pyc are version 3.0 (rev 0).
Traceback (most recent call last):
File "/usr/bin/fred-webadmin", line 8, in <module>
from fred_webadmin.controller import adif
File "/usr/lib/python2.7/dist-packages/fred_webadmin/controller/adif.py",
line 38, in <module>
import fred_webadmin.auth.corba_auth as auth
File "/usr/lib/python2.7/dist-packages/fred_webadmin/auth/corba_auth.py",
line 1, in <module>
import fred_webadmin.corbarecoder as recoder
File "/usr/lib/python2.7/dist-packages/fred_webadmin/corbarecoder.py",
line 5, in <module>
from pyfco.recoder import decode_iso_date, decode_iso_datetime,
encode_iso_date, encode_iso_datetime
File "/usr/lib/python2.7/dist-packages/pyfco/__init__.py", line 3, in
<module>
from .name_service import CorbaNameServiceClient
File "/usr/lib/python2.7/dist-packages/pyfco/name_service.py", line 6, in
<module>
import CosNaming
File "/usr/lib/python2.7/dist-packages/CosNaming/__init__.py", line 9, in
<module>
import CosNaming_idl
File "/usr/lib/python2.7/dist-packages/CosNaming_idl.py", line 7, in
<module>
_omnipy.checkVersion(3,0, __file__)
ImportError: Stubs not compatible with omniORBpy version 4.2.
Is there a way I can solve this compatibility issure?
The process omniorb4-nameserver status output is as follows:
omniorb4-nameserver.service - LSB: Start the omniNames Interoperable Naming
Service
Loaded: loaded (/etc/init.d/omniorb4-nameserver; bad; vendor preset:
enabled)
Active: active (exited) since Wed 2019-01-16 07:39:02 SAST; 11min ago
Docs: man:systemd-sysv-generator(8)
Process: 28050 ExecStop=/etc/init.d/omniorb4-nameserver stop (code=exited,
status=0/SUCCESS)
Process: 28133 ExecStart=/etc/init.d/omniorb4-nameserver start
(code=exited, status=0/SUCCESS)
Tasks: 0
Memory: 0B
CPU: 0
Jan 16 07:39:02 fred-test systemd[1]: Starting LSB: Start the omniNames
Interoperable Naming Service...
Jan 16 07:39:02 fred-test omniorb4-nameserver[28133]: * Starting omniORB
name server omniNames
Jan 16 07:39:02 fred-test omniorb4-nameserver[28133]: ...done.
Jan 16 07:39:02 fred-test systemd[1]: Started LSB: Start the omniNames
Interoperable Naming Service.
In fred-eppd.log I found [sessionID 216968] Could not obtain object
reference for alias 'EPP_alias'. Check mod_corba's configuration, whoever
the module does seem to be enables under apache mods-enabled.
What could be the problem?
Regards,
Moeketsi Maphoi
Greetings
Fedora 29 got officially released on 30 October last year but no
packages have been built for that release [1] as of today hence
installation on the distro fails with....
Failed to synchronize cache for repo 'fred', ignoring this repo.
No match for argument: fred-*
Any particular reason the components have not been built for the 29
release of Fedora?
Regards
Jóhann B.
1. http://archive.nic.cz/yum/fred/fedora/
