fred-users

fred-users@lists.nic.cz

407 discussions

Prices for creating and renewing domains

by Mario Guerra

Hello. We've tested applying credits to registrars using FRED. Now, I want to make a question of how the deductions are made. Say, I decide to have 40 monetary units for domain creation and 10 for domain update for renewing my domain, this way. /fred-admin --price_add --operation_price 40.00 --zone_fqdn dom --operation CreateDomain/ /fred-admin --price_add --operation_price 10.00 --zone_fqdn dom --operation RenewDomain/ and assign 140 monetary units to their credit, this way /fred-admin --invoice_credit --zone_id 1 --registrar_id 6 --price 140/ The zone numbered 1 is "dom" . When I create a domain like this: /create_domain testmg6.dom mf02 NULL NULL NULL (1 y) / What is deducted from the credit is 80 monetary units, not 70, so what is left is 60. Is that correct?. If it is, how to apply ONLY the renewal price when you renew the domain, not when you create it?. Best regards. Mario Guerra NIC-CR

8 let, 1 měsíc

Re: payments - invoices and statements on FRED registry system

by Dr P Nyirenda

On 27 Jun 2017 at 9:18, Ghislain wrote: > Good Morning all, > > We (i.e. .RW registry – RICTA Ltd.) are not using FRED but I think the prepayment model is more > or less the same. > > #1. We don’t pre-invoice the registrars based on a “pre-established” list of domain names. > This is a lot of work, and it won’t scale if you have 100 of registrars, unless the registry does that > for them. > But even if it is possible from the registry, it is a lot of work for “them” (i.e. manual work). > > Therefore, they (registrars) just send money/amount, let say $500 or 30,000 RWF, and that is > what we issue the invoice for. > With a simple description, i.e. “Advance payment”. BTW, the amount can vary depending on > what they want to register, renew, etc. Thank you for the input, most of this is already the same on .mw registry. > The law in Rwanda don’t allow to receive money without an invoice. (it being advance or actual > payment). It appears there is no such law in Malawi and this is part of the reason I raised the question - to learn what is the case with other ccTLD registries. > #2. Once received, we credit their accounts in the Registry system. (still a manual process). > Then they can do whatever they want with it (i.e. do registration, renewal, pay for transfer fees, > etc.). Same. So, does your registry system have facilities for generating invoices such as these for pre-payments? Does it produce statements form registrars? Regards, Paulos ====================== Dr Paulos B Nyirenda NIC.MW & .mw ccTLD http://www.registrar.mw > > I think this approach (above) is more flexible. > > A little additional info: > > The money received from registrars, is a liability until it is consumed. > Until it is consumed, it cannot yet be called revenues from your side (registry). > From financial “documents” perspective, an un-consumed advance payment is a liability that > needs to seat in the balance sheet. > Once the revenue is realized (end of month), the money can be recognized in you Income > statement. (you debit the liability and credit your income accounts). > > Sorry if this is perhaps more than what you asked for. > > Thank you, > > Ghislain > .RW registry > > From: fred-users <fred-users-bounces(a)lists.nic.cz> on behalf of Jaromir Talir > <jaromir.talir(a)nic.cz> > Reply-To: A mailing list for users and developers of FRED registry system > <fred-users(a)lists.nic.cz> > Date: Friday, 23 June 2017 at 17:18 > To: <paulos(a)sdnp.org.mw>, <fred-users(a)lists.nic.cz> > Subject: Re: payments - invoices and statements on FRED registry system > > Hi Paulos, > > I guess this is more question for some Malawi lawyer. In Czech Republic > we have a law that we should issue invoice when we receive advanced > payment. However, this may be something specific for our legislation. > Also every legislation specifies what should be the content of the > invoice in that case (issuer, recipient, day of payment, effective day > of service, etc..). This may differ country to country as well. FRED > contains PDF templates for invoices according Czech legislation. I > cannot say if they may be used for you as well. > > If you will be in Joburg, we can have a talk about it there. > > Regards, > Jaromir > > On Fri, 2017-06-16 at 05:15 +0200, Dr P Nyirenda wrote: > Hello, > I would like to find out how your registry responds to a request like > the one here below > for invoices and statements on registrar payments to a registry that > uses the FRED > registry system. > On our registry for the Malawi .mw ccTLD, registrar payments are > credited to the > registrar zone by zone according to what the registrar has paid for. > Once the registrar > has consumed the credit, then they need to make a new payment in > advance which is then > credited to the zones that they need. > We do not need to issue them an invoice in advance, they make the > payments based on what > transactions they need to do on each zone. > When we receive a request for their data payments, we have used > Invoice on Daphne to > generate the data and we have sent this to the registrar. > However, as you can see here below, this registrar seems to be asking > for more. > I would therefore like to request information on how your registry > using FRED handles > requests for data, invoices and statements like these. > Regards, > Paulos > ====================== > Dr Paulos B Nyirenda > NIC.MW & .mw ccTLD > http://www.registrar.mw > ------- Forwarded message follows ------- > From: Jamil Kamaly <Jamil.Kamaly(a)NetNames.com > > To: "paulos(a)sdnp.org.mw" <paulos(a)sdnp.org.mw> > Copies to: Michal Czyz <Michal.Czyz(a)NetNames.com>, domains mw > <domains(a)registrar.mw>, > PB Nyirenda <pb.nyirenda(a)gmail.com> > Subject: RE: Malawi payments. > Date sent: Wed, 14 Jun 2017 11:56:39 +0000 > Hi Dr Paulos, > I think you might have misunderstood, I wasn’t complaining. The > details you provided me > in April was excel spreadsheet with payment details and the zones > that were topped. We > need proper invoices and statements and therefore I was following up > on our last > conversation where you was saying that you are developing a system to > make this possible. > I was just checking if this is now possible and would we be getting > proper statements > and invoices. > Thank you. > Kind regards, > Jamil > ---------------------------------------------------------- > Malawi SDNP Webmail: http://www.sdnp.org.mw > Access your Malawi SDNP e-mail from anywhere in the world. > ---------------------------------------------------------- > -- > 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(a)nic.cz tel:+420.222745107 > mob:+420.739632712 fax:+420.222745112 > ------------------------------------------- > _______________________________________________ > fred-users mailing list > fred-users(a)lists.nic.cz > https://lists.nic.cz/cgi-bin/mailman/listinfo/fred-users > ---------------------------------------------------------- Malawi SDNP Webmail: http://www.sdnp.org.mw Access your Malawi SDNP e-mail from anywhere in the world. ----------------------------------------------------------

8 let, 2 měsíce

RE: payments - invoices and statements on FRED registry system

by Dr P Nyirenda

Hello, I would like to find out how your registry responds to a request like the one here below for invoices and statements on registrar payments to a registry that uses the FRED registry system. On our registry for the Malawi .mw ccTLD, registrar payments are credited to the registrar zone by zone according to what the registrar has paid for. Once the registrar has consumed the credit, then they need to make a new payment in advance which is then credited to the zones that they need. We do not need to issue them an invoice in advance, they make the payments based on what transactions they need to do on each zone. When we receive a request for their data payments, we have used Invoice on Daphne to generate the data and we have sent this to the registrar. However, as you can see here below, this registrar seems to be asking for more. I would therefore like to request information on how your registry using FRED handles requests for data, invoices and statements like these. Regards, Paulos ====================== Dr Paulos B Nyirenda NIC.MW & .mw ccTLD http://www.registrar.mw ------- Forwarded message follows ------- From: Jamil Kamaly <Jamil.Kamaly(a)NetNames.com> To: "paulos(a)sdnp.org.mw" <paulos(a)sdnp.org.mw> Copies to: Michal Czyz <Michal.Czyz(a)NetNames.com>, domains mw <domains(a)registrar.mw>, PB Nyirenda <pb.nyirenda(a)gmail.com> Subject: RE: Malawi payments. Date sent: Wed, 14 Jun 2017 11:56:39 +0000 Hi Dr Paulos, I think you might have misunderstood, I wasn’t complaining. The details you provided me in April was excel spreadsheet with payment details and the zones that were topped. We need proper invoices and statements and therefore I was following up on our last conversation where you was saying that you are developing a system to make this possible. I was just checking if this is now possible and would we be getting proper statements and invoices. Thank you. Kind regards, Jamil ---------------------------------------------------------- Malawi SDNP Webmail: http://www.sdnp.org.mw Access your Malawi SDNP e-mail from anywhere in the world. ----------------------------------------------------------

8 let, 2 měsíce

Maximum renewal period in FRED

by Dr Paulos B Nyirenda

Jaromir, Just one or two more clarifications on FRED: 1. Is there a default maximum number of years (or months) for renewing a domain ? I see that in .cz this is required to be 10 years - is this burned into FRED or can it be modified? See: https://www.nic.cz/files/nic/doc/Registration_rules_CZ.pdf Regards, Paulos ====================== Dr Paulos B Nyirenda NIC.MW & .mw ccTLD http://www.registrar.mw

8 let, 4 měsíce

Invitation à participer à Meetup#2 Présentation et Workshop Openstack

by Ousmane Sanogo

Vous avez reçu une invitation ! -------------------------------------- Rejoignez Ousmane Sanogo à Meetup#2 Présentation et Workshop Openstack Quand : samedi 29 avril 2017, 09:00 Où : Ecole Agitel-Formation 132, Abidjan, Côte d'Ivoire, Abidjan Ce Meetup est organisé par Openstack Côte d'Ivoire. Après une première rencontre pour fêter les 6 ans de Openstack et le lancement du groupe d'utilisateur de Côte d'ivoire, nous organisons un second Meetup qui va vous permettre de mieux connaitre Open... https://secure.meetup.com/n/?s=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkZXN… -------------------------------------- ------- Message envoyé par Meetup de la part de Ousmane Sanogo (https://www.meetup.com/fr-FR/Openstack-Cote-divoire/members/212092234/) depuis Openstack Côte d'Ivoire. Une question? Vous pouvez contacter le support Meetup via support(a)meetup.com Je ne souhaite plus recevoir ce type d'e-mail (https://secure.meetup.com/n/?s=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJob29…) Meetup Inc. (https://www.meetup.com/fr-FR/), POB 4668 #37895 New York NY USA 10163

8 let, 5 měsíců

new documentation for FRED (available on github)

by Jaromir Talir

Hi, in addition to new FRED release, we have also released a new website at https://fred.nic.cz and completely new documentation system. Documentation url is https://fred.nic.cz/documentation. I feel importance of this deserves to use separate email for announcement. New documentation is searchable and it contains many new graphical schemas important to understand FRED architecture and processes. Source code of this documentation in reStructuredText format is available on github https://github.com/CZ-NIC/fred-docs. This means that you are more then welcomed to submit comments or preferably pull requests for things that you think they are missing in documentation. Please, check documentation and let us know what you think about this. Regards, Jaromir

8 let, 5 měsíců

new version FRED-2.29

by Jaromir Talir

Hi, we have published FRED version 2.29. During several previous releases we have rewritten almost all code responsible for EPP communication with registrars. This refactoring was necessery for implementation of new features in the future. Here is a compilation of some significant changes. - support for more operating systems. For the first time we provide also packages for latest RHEL/Centos version 7. Since Ubuntu 12.04 will lost its long term support in April, we will not provide packages for this version anymore. Preffered version of Ubuntu is 16.04. We use Ubuntu 16.04 in production for some time without any issues. This also means that Ubuntu 16.04 is most tested platform. In other platforms we only run limited set of automated tests so registries are required to do more indepth tests themselves. - configurable domain name format checking. Checking of validity of domain name is configurable per zone via linking to set of preconfigured checkers in database table zone_domain_name_validation_checker_map. - new idn support configuration. There used to be allow_idn option in server configuration file that meant that regular registrars are able to register domains in xn-- format (idn domains) in all zones. In current version it is possible to configure idn support per zone via mechanism mentioned earlier. Support for idn is just another preconfigured checker. - configurable dnssec algorithm checking. Until now, there was no checking of dnssec algorithm number used in EPP create_keyset or update_keyset EPP commands. If registries would like to limit this check only for some algorithms, they can do that via modification of database tables dnssec_algorithm and dnssec_algorithm_blacklist. - configurable limit of minimal number of nameservers in nsset. Until now, there was hardcoded requirement to have at least 2 nameservers and maximum 10 nameservers in nsset. Since this was limitation for some registries that wanted to use FRED, we moved this limit into configuration option nsset_min_hosts and nsset_max_hosts in server configuration file - asynchronous notification about EPP events. Notifications for domain state change has always been generated asynchronously via fred-admin commands, but notifications about EPP events done by registrars were created as part of EPP operation. To speed up system a little bit and to be able to continue EPP operation even when notification system is down, we made also notification about EPP events asynchronnous. So don't forget to add into cron system command 'fred-admin -- notify_email_objects_events' in intervals of your preference if you want to keep sending notifications. Regards, Jaromir

8 let, 5 měsíců

FRED and Apache 2.4 on Ubuntu 14.04

by Mario Guerra

People: A nagging problem we had when we migrated FRED to Ubuntu 14.04 (until a couple of weeks ago we ran 2.22 on Ubuntu 12.04) was that, suddenly, Apache connections gave us a CLOSE_WAIT, not a clean closing of the connection. This gave us a real headache with both our whois server and our EPP server. The solution?. Well, simply uninstall the mpm_event Apache module and install the mem_prefork one: a2dismod mpm_event a2enmod mem_prefork service apache2 restart I hope this helps the people using FRED under Ubuntu 14.04 experiencing a similar problem. ------------ Mario Guerra NIC-CR

8 let, 7 měsíců

ERROR HEADER: unpack requires a string argument of length 4

by Jakub Andrys

Hi, I have clean install of Ubuntu 16.04 server and I use script install: https://fred.nic.cz/page/2906/installation-on-ubuntu/ everything looks OK, but when I wan use fred-client, got this error: # fred-client FredClient upstream/2.7.0-97-g21a67 Type "help", "license" or "credits" for more information. Using configuration from /root/.fred-client.conf Used socket type: IPv6. Socket timeout: 10.0 sec. Connecting to localhost, port 700 ... Connection established. Try to open SSL layer... SSL layer opened. ERROR: ERROR HEADER: unpack requires a string argument of length 4 Server didn't return Greeting message. Contact server administrator. in /var/log/fred-eppd.log [19/Jan/2017:10:02:56 +0100] ::1 (process:2354) [sessionID 352216] Could not obtain object reference for alias 'EPP_alias'. Check mod_corba's configuration. [19/Jan/2017:10:02:56 +0100] ::1 (process:2354) [sessionID 352216] Could not obtain object reference for alias 'EPP_alias'. Connection on port 700 looks OK. Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 192.168.120.153:53 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN tcp6 0 0 :::43 :::* LISTEN tcp6 0 0 :::80 :::* LISTEN tcp6 0 0 :::53 :::* LISTEN tcp6 0 0 :::22 :::* LISTEN tcp6 0 0 :::25 :::* LISTEN tcp6 0 0 :::2809 :::* LISTEN tcp6 0 0 ::1:953 :::* LISTEN tcp6 0 0 :::443 :::* LISTEN tcp6 0 0 :::700 :::* LISTEN udp 0 0 192.168.120.153:53 0.0.0.0:* udp 0 0 127.0.0.1:53 0.0.0.0:* udp 0 0 0.0.0.0:68 0.0.0.0:* udp6 0 0 :::53 :::* Any idea whats wrong? Regards, Jakub

8 let, 7 měsíců

Weak digest algorithm @ archive.nic.cz

by Torkil Zachariassen

While running # apt-get update on Ubunto-16 as warning is issued: W: http://archive.nic.cz/ubuntu/dists/xenial/Release.gpg: Signature by key 55360425D50EB41DB9A21E67F20C079E020ADBB4 uses weak digest algorithm (SHA1) It seems that Debian and friends do not like SHA1 any longer. They provide more info on the removal of sha1 and how to fix a half-broken repositories https://wiki.debian.org/Teams/Apt/Sha1Removal I suppose the fred repository for ubunto at archive.nic.cz could be updated along those lines.

8 let, 7 měsíců

← Newer
1
...
8
9
10
11
12
13
14
...
41
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

fred-users