fred-users

fred-users@lists.nic.cz

408 discussions

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.

9 let

IDN in fred? Howto

by Torkil Zachariassen

We are to try out having a few extra national characters áýúíóæøåð and in uppercase these are ÁÝÚÍÓÆØÅÐ in ccTLD names (.fo) We found the 'allow_idn' in server.conf and have it set as 'true' (allow_idn = true), but this seems not to be enough, and does not really fullfill the requirements. IDN is mentioned an option in fred, but where/how can we turn this on, and what should we be aware of ? ...torkil...

9 let

On Ubuntu 16.04.1 LTS - updating broke fred

by Torkil Zachariassen

Sorry for this lengthy message, but a bugfix is provided with a description of the issue in the latest packages of fred for ubunto Have a nice day On Ubuntu 16.04.1 LTS - just updated and upgraded everything including fred, broke fred # systemctl status fred-logd ● fred-logd.service - FRED logging daemon Loaded: loaded (/lib/systemd/system/fred-logd.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Fri 2016-12-30 16:56:12 WET; 17min ago Process: 3653 ExecStart=/usr/sbin/fred-logd -ORBendPoint giop:tcp::2226 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-logd.conf (code=exited, status=1/FAILURE) Main PID: 3653 (code=exited, status=1/FAILURE) Dec 30 16:56:12 fred-ubunto-16 systemd[1]: fred-logd.service: Failed with result 'exit-code'. Dec 30 16:56:12 fred-ubunto-16 systemd[1]: fred-logd.service: Service hold-off time over, scheduling restart. Dec 30 16:56:12 fred-ubunto-16 systemd[1]: Stopped FRED logging daemon. Dec 30 16:56:12 fred-ubunto-16 systemd[1]: fred-logd.service: Start request repeated too quickly. Dec 30 16:56:12 fred-ubunto-16 systemd[1]: Failed to start FRED logging daemon. Hmm where is fred-logd.conf ? In /etc/init/fred-logd.conf ! BUGFIX # cd /etc/fred # ln -s ../init/fred-logd.conf root@fred-ubunto-16:/etc/fred# systemctl start fred-logd root@fred-ubunto-16:/etc/fred# systemctl status fred-logd ● fred-logd.service - FRED logging daemon Loaded: loaded (/lib/systemd/system/fred-logd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-12-30 17:22:57 WET; 2s ago Main PID: 4600 (fred-logd) Tasks: 3 Memory: 2.5M CPU: 25ms CGroup: /system.slice/fred-logd.service └─4600 /usr/sbin/fred-logd -ORBendPoint giop:tcp::2226 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-logd.conf Dec 30 17:22:57 fred-ubunto-16 systemd[1]: Started FRED logging daemon. So the bugfix worked :-) Next issue: # systemctl status fred-rifd ● fred-rifd.service - FRED registrar interface daemon Loaded: loaded ( ; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Fri 2016-12-30 16:50:26 WET; 35min ago Process: 3321 ExecStart=/usr/sbin/fred-rifd -ORBendPoint giop:tcp::2224 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-rifd.conf (code=exited, status=1/FAILURE) Main PID: 3321 (code=exited, status=1/FAILURE) Dec 30 16:50:25 fred-ubunto-16 systemd[1]: fred-rifd.service: Main process exited, code=exited, status=1/FAILURE Dec 30 16:50:25 fred-ubunto-16 systemd[1]: fred-rifd.service: Unit entered failed state. Dec 30 16:50:25 fred-ubunto-16 systemd[1]: fred-rifd.service: Failed with result 'exit-code'. Dec 30 16:50:26 fred-ubunto-16 systemd[1]: fred-rifd.service: Service hold-off time over, scheduling restart. Dec 30 16:50:26 fred-ubunto-16 systemd[1]: Stopped FRED registrar interface daemon. Dec 30 16:50:26 fred-ubunto-16 systemd[1]: fred-rifd.service: Start request repeated too quickly. Dec 30 16:50:26 fred-ubunto-16 systemd[1]: Failed to start FRED registrar interface daemon. Again /lib/systemd/system/fred-rifd.service specifies fred-rifd.conf to be in /etc/fred, were as it is in /etc/init :-/ BUGFIX # cd /etc/fred # ln -s ../init/fred-rifd.conf # cd # systemctl start fred-rifd # systemctl status fred-rifd ● fred-rifd.service - FRED registrar interface daemon Loaded: loaded (/lib/systemd/system/fred-rifd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-12-30 17:30:01 WET; 6s ago Main PID: 4777 (fred-rifd) Tasks: 3 Memory: 3.3M CPU: 31ms CGroup: /system.slice/fred-rifd.service └─4777 /usr/sbin/fred-rifd -ORBendPoint giop:tcp::2224 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-rifd.conf Dec 30 17:30:01 fred-ubunto-16 systemd[1]: Started FRED registrar interface daemon. So the bugfix worked :-) Next issue: # systemctl status fred-pifd ● fred-pifd.service - FRED public interface daemon Loaded: loaded (/lib/systemd/system/fred-pifd.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Fri 2016-12-30 16:28:07 WET; 1h 7min ago Process: 1334 ExecStart=/usr/sbin/fred-pifd -ORBendPoint giop:tcp::2223 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-pifd.conf (code=exited, status=1/FAILURE) Main PID: 1334 (code=exited, status=1/FAILURE) Tasks: 0 Memory: 0B CPU: 0 CGroup: /system.slice/fred-pifd.service Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-pifd.service: Main process exited, code=exited, status=1/FAILURE Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-pifd.service: Unit entered failed state. Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-pifd.service: Failed with result 'exit-code'. Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-pifd.service: Service hold-off time over, scheduling restart. Dec 30 16:28:07 fred-ubunto-16 systemd[1]: Stopped FRED public interface daemon. Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-pifd.service: Start request repeated too quickly. Dec 30 16:28:07 fred-ubunto-16 systemd[1]: Failed to start FRED public interface daemon. BUGFIX # cd /etc/fred # ln -s ../init/fred-pifd.conf # cd # systemctl start fred-pifd # systemctl status fred-pifd ● fred-pifd.service - FRED public interface daemon Loaded: loaded (/lib/systemd/system/fred-pifd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-12-30 17:36:47 WET; 10ms ago Main PID: 4941 (fred-pifd) Tasks: 1 Memory: 1.1M CPU: 5ms CGroup: /system.slice/fred-pifd.service └─4941 /usr/sbin/fred-pifd -ORBendPoint giop:tcp::2223 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-pifd.conf Dec 30 17:36:47 fred-ubunto-16 systemd[1]: Started FRED public interface daemon. So the bugfix worked :-) Next issue: # systemctl status fred-msgd ● fred-msgd.service - FRED messaging daemon Loaded: loaded (/lib/systemd/system/fred-msgd.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Fri 2016-12-30 16:28:06 WET; 1h 9min ago Process: 1258 ExecStart=/usr/sbin/fred-msgd -ORBendPoint giop:tcp::2228 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-msgd.conf (code=exited, status=1/FAILURE) Main PID: 1258 (code=exited, status=1/FAILURE) Dec 30 16:28:05 fred-ubunto-16 systemd[1]: fred-msgd.service: Unit entered failed state. Dec 30 16:28:05 fred-ubunto-16 systemd[1]: fred-msgd.service: Failed with result 'exit-code'. Dec 30 16:28:06 fred-ubunto-16 systemd[1]: fred-msgd.service: Service hold-off time over, scheduling restart. Dec 30 16:28:06 fred-ubunto-16 systemd[1]: Stopped FRED messaging daemon. Dec 30 16:28:06 fred-ubunto-16 systemd[1]: fred-msgd.service: Start request repeated too quickly. Dec 30 16:28:06 fred-ubunto-16 systemd[1]: Failed to start FRED messaging daemon. Same thing BUGFIX # cd /etc/init # ln -s ../init/fred-msgd.conf # cd # systemctl start fred-msgd # systemctl status fred-msgd ● fred-msgd.service - FRED messaging daemon Loaded: loaded (/lib/systemd/system/fred-msgd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-12-30 17:38:59 WET; 4s ago Main PID: 5016 (fred-msgd) Tasks: 3 Memory: 1.6M CPU: 20ms CGroup: /system.slice/fred-msgd.service └─5016 /usr/sbin/fred-msgd -ORBendPoint giop:tcp::2228 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-msgd.conf Dec 30 17:38:59 fred-ubunto-16 systemd[1]: Started FRED messaging daemon. So the bugfix worked :-) Next issue: # systemctl status fred-adifd ● fred-adifd.service - FRED administration interface daemon Loaded: loaded (/lib/systemd/system/fred-adifd.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Fri 2016-12-30 16:28:08 WET; 1h 12min ago Process: 1352 ExecStart=/usr/sbin/fred-adifd -ORBendPoint giop:tcp::2222 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-adifd.conf (code=exited, status=1/FAILURE) Main PID: 1352 (code=exited, status=1/FAILURE) Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-adifd.service: Unit entered failed state. Dec 30 16:28:07 fred-ubunto-16 systemd[1]: fred-adifd.service: Failed with result 'exit-code'. Dec 30 16:28:08 fred-ubunto-16 systemd[1]: fred-adifd.service: Service hold-off time over, scheduling restart. Dec 30 16:28:08 fred-ubunto-16 systemd[1]: Stopped FRED administration interface daemon. Dec 30 16:28:08 fred-ubunto-16 systemd[1]: fred-adifd.service: Start request repeated too quickly. Dec 30 16:28:08 fred-ubunto-16 systemd[1]: Failed to start FRED administration interface daemon. Again same thing BUGFIX # cd /etc/fred # ln -s ../init/fred-adifd.conf # cd # root@fred-ubunto-16:~# systemctl start fred-adifd # root@fred-ubunto-16:~# systemctl status fred-adifd ● fred-adifd.service - FRED administration interface daemon Loaded: loaded (/lib/systemd/system/fred-adifd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-12-30 17:41:42 WET; 4s ago Main PID: 5128 (fred-adifd) Tasks: 4 Memory: 3.3M CPU: 29ms CGroup: /system.slice/fred-adifd.service └─5128 /usr/sbin/fred-adifd -ORBendPoint giop:tcp::2222 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-adifd.conf Dec 30 17:41:42 fred-ubunto-16 systemd[1]: Started FRED administration interface daemon. Final check # fred-status && echo ok ok DONE :-) NOTE fred-status is a local script which looks like this: ####################################################################### #!/bin/sh # File: fred-status.sh # Purpose: Check that fred runs all the 7 required processes # Author: Torkil Zachariassen # Date: 20161209 CMD="ps -u fred --no-headers" count=`$CMD|wc -l` if [ $count -ne 7 ]; then echo ERROR Wrong number of processes $CMD exit 1 fi # return ok return 0 NOTE $ ps -u fred should return the following processes PID TTY TIME CMD 1096 ? 00:01:32 fred-webadmin 1181 ? 00:00:03 fred-logd 1182 ? 00:00:00 fred-rifd 1217 ? 00:00:00 fred-pifd 1218 ? 00:00:01 fred-adifd 3574 ? 00:00:00 fred-msgd 3685 ? 00:00:05 fred-pyfred ####################################################################### It seems that the problem are the following lines in fred-* in /lib/systemd/system: # grep /fred/fred /lib/systemd/system/fred-* /lib/systemd/system/fred-adifd.service:ExecStart=/usr/sbin/fred-adifd -ORBendPoint giop:tcp::2222 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-adifd.conf /lib/systemd/system/fred-logd.service:ExecStart=/usr/sbin/fred-logd -ORBendPoint giop:tcp::2226 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-logd.conf /lib/systemd/system/fred-msgd.service:ExecStart=/usr/sbin/fred-msgd -ORBendPoint giop:tcp::2228 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-msgd.conf /lib/systemd/system/fred-pifd.service:ExecStart=/usr/sbin/fred-pifd -ORBendPoint giop:tcp::2223 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-pifd.conf /lib/systemd/system/fred-rifd.service:ExecStart=/usr/sbin/fred-rifd -ORBendPoint giop:tcp::2224 -ORBnativeCharCodeSet UTF-8 --config /etc/fred/fred-rifd.conf as these references configuration files in /etc/fred, whereas the actual configuration files are installed in /etc/init As I am unsure of what the correct solution might be I will leave this issue to the packager Have a nice day :-)

9 let, 1 měsíc

Re: PHP API

by Agustin Sacramento

Hi! The better way for us was made a Django ApiRest for our front based in PHP Synfony2. You can import fred-client lib and use it into your ApiRest. Best regards, Agustin Sacramento -----Original Message----- From: fred-users [mailto:fred-users-bounces@lists.nic.cz] On Behalf Of Jaromir Talir Sent: Friday, November 11, 2016 13:34 To: A mailing list for users and developers of FRED registry system Subject: Re: PHP API Hi, there is nothing I'd know about for immediate use. It would be great if somebody from community of users would make it. We don't have PHP programmers in our company. Regards, Jaromir On Sun, 2016-11-06 at 14:12 +0200, Mark Elkins wrote: > Better still - open sourced, readable and commented code of an API > written in PHP. > > On 06/11/2016 13:14, Thiago Farina wrote: >> Is there a PHP API for the Python fred client? >> >> -- >> Thiago Farina > _______________________________________________ > fred-users mailing list > fred-users(a)lists.nic.cz > https://lists.nic.cz/cgi-bin/mailman/listinfo/fred-users -- Jaromir Talir Technicky partner / Technical Fellow ------------------------------------------- CZ.NIC, z.s.p.o. -- .cz domain registry Milesovska 5, 130 00 Praha 3, Czech Republicmailto:jaromir.talir@nic.cz http://nic.cz/ sip:jaromir.talir@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

9 let, 2 měsíce

Quick question on Fred regarding Premium Domain Names

by Mark Elkins

I'm writing some words on my understanding of Premium Domain Names - and am not sure about FRED.... Quick question: Does FRED implement the code to specify that "these names" are premium names and therefore cost more. The Registrar also needs a slight EPP code modification in that they must provide the (expected) cost of the domain to the Registry - in order to confirm its premium status - and I guess - the correct cost. In order for the Registry to implement this, one might need to perhaps provide a file of "regular expressions" which if met - would imply the Domain Name is Premium... could even add a second column as the cost? eg . (to match one character) .. (to match two characters) ... (to match three characters) green ( and other "generic" names) blue sexy travel hotel* (hotel, hotels, hotel-bookings - etc) Perhaps - do people have a different understanding of "What is a Premium Domain Name" ? -- Mark James ELKINS - Posix Systems - (South) Africa mje(a)posix.co.za Tel: +27.128070590 Cell: +27.826010496 For fast, reliable, low cost Internet in ZA: https://ftth.posix.co.za

9 let, 2 měsíce

PHP API

by Thiago Farina

Is there a PHP API for the Python fred client? -- Thiago Farina

9 let, 2 měsíce

Two notes about keysets

by Mario Guerra

1. The update_domain source includes the keyset firld. which is correct: ----- self.epp.update_domain(get_domain.id.id.name, add_admin=None, rem_admin=None, chg={'nsset' : None, 'keyset' : keyset_id, 'registrant' : None, 'auth_info' : None}, val_ex_date=None, cltrid=None) ----- But the documentation does not. Checking https://fred.nic.cz/files/fred/fred.txt, we have this fragment ----- update_domain(self, name, add_admin=None, rem_admin=None, chg=None, val_ex_date=None, cltrid=None) DESCRIPTION: The EPP 'update_domain' command is used to update values in the domain. SYNTAX: update_domain name [other_options] OPTIONS: name (required) Domain name add_admin Administrative contact ID (unbounded list) rem_admin Administrative contact ID (unbounded list) chg Change values nsset NSSET ID registrant Registrant ID auth_info Password required by server to authorize the transfer val_ex_date Validation expires at cltrid Client transaction ID ----- 2. The DS generated from the DNSKEY included in keysets, only includes the algorithm 1 (SHA1) but not 2 (SHA256). Best. Mario

9 let, 3 měsíce

auth info database query - best practice for sending auth info to a registrar

by Dr Paulos B Nyirenda

We are now prepapring to transfer multiple domains from our 2R registry to registrars now on the 3R FRED registry for .mw domains. Could you please tell me the best database command for collecting the auth info for a domain Since there appears to be no bulk domain transfer facility in FRED my guess is that we need to run the database query repeatedly to collect domain & auth-info pairs that we can then pass on to the registrar. What is the current best practice for passing auth info details to a registrar? Regards, PC ====================== Dr Paulos B Nyirenda NIC.MW & .mw ccTLD http://www.registrar.mw

9 let, 4 měsíce

auth info database query - best practice for sending auth info to a registrar

by Dr Paulos Nyirenda

9 let, 4 měsíce

domain transfers in FRED - how to charge the transaction

by Dr Paulos B Nyirenda

Jaromir, all, Our FRED registry 3R operation is going well enough that we can now move on to tackle issues on domain transfers and I have one or two questions with the following understanding that I have:. 1. My understanding is that: Once auth_info has been sent from current owner A to new owner B for domain dA.mw then B can do the transfer, such as using fred-client command: transfer_domain dA.mw auth_info_A [other_options] Is this correct? what are the other options? 2. A WHOIS query for dA.mw will then list new registrar: B 3. System then generates new auth_info_B and assigns it under registrar B ... right ? 4. How can the registry charge for the transfer of the domain dA.mw? 5. What needs to be configured in FRED to charge for domain transfers like this one? 6. If this FRED config can be done using fred-admin then please show syntax for trhe fred-admin command to configure charging for domain transfers. 7. If there a similar arrangement for transfering other objects like contacts and/or nssets? Regards, Paulos ====================== Dr Paulos B Nyirenda NIC.MW & .mw ccTLD http://www.registrar.mw ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2016.0.7752 / Virus Database: 4649/12929 - Release Date: 09/01/16 ------- End of forwarded message -------

9 let, 4 měsíce

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

fred-users