Solved using a footer in genzone_client
Added
footer = /etc/fred/genzone.footer
to genzone.conf and added
_nicname._tcp.fo. IN SRV 0 0 43 whois.nic.fo.
to genzone.footer
Then "genzone_client fo" included the SRV at next update,
and everything worked fine. :-)
vh ...torkil...
On frí, 2011-06-10 at 21:11 +0100, Petur Kirke wrote:
>
> --------------------------------------------------
> From: "Mario Guerra" <mguerra(a)nic.cr>
> Sent: Friday, June 10, 2011 5:03 PM
> To: <fred-users(a)lists.nic.cz>
> Subject: Re: SRV record
>
> > On Fri, 10 Jun 2011 13:31:16 +0100
> > "Petur Kirke" <peturkirke(a)hotmail.com> wrote:
> >
> >> We want to put a SRV record into our zone, something like this:
> >>
> >> _nicname._tcp.fo 86400 IN SRV 0 5 43 whois.nic.fo.
> >>
> >> How can this be done in Fred ?
> >>
> >
> > I wouldn't use FRED for that. Rather, I would use shell statements or
> > similar after running genzone_client. Like:
> >
> > genzone_client fo
> > cat >> db.fo << EOF
> > _nicname._tcp.fo 86400 IN SRV 0 5 43 whois.nic.fo.
> > EOF
> >
named should be reloaded after this.
An alternative is to use the footer feature in genzone_client. See
above.
Hi!
I am installing FRED for the first time here. Got so far as to install the latest database fred-db-2.3.2 into pgsql 8.4. Here's the errors I get. Anybody who has seen this before?
...
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "request_property_value_pkey" for table "request_property_value"
setval
--------
1406
(1 row)
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: function tr_request(integer, timestamp without time zone, timestamp without time zone, inet, integer, integer, integer, character varying, boolean) does not exist
LINE 1: ...unction AS ON INSERT TO request DO INSTEAD SELECT tr_request...
^
HINT: No function matches the given name and argument types. You might need to add explicit type casts.
ERROR: function tr_request_data(timestamp without time zone, integer, boolean, integer, text, boolean) does not exist
LINE 1: ...on AS ON INSERT TO request_data DO INSTEAD SELECT tr_request...
^
HINT: No function matches the given name and argument types. You might need to add explicit type casts.
ERROR: function tr_request_property_value(timestamp without time zone, integer, boolean, integer, integer, integer, text, boolean, integer) does not exist
LINE 1: ...NSERT TO request_property_value DO INSTEAD SELECT tr_request...
^
HINT: No function matches the given name and argument types. You might need to add explicit type casts.
ERROR: function tr_session(integer, character varying, timestamp without time zone, timestamp without time zone, character varying) does not exist
LINE 2: DO INSTEAD SELECT tr_session ( NEW.id, NEW.name, NEW.login_d...
^
HINT: No function matches the given name and argument types. You might need to add explicit type casts.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
ERROR: language "plpgsql" does not exist
HINT: Use CREATE LANGUAGE to load the language into the database.
How to change the 30 and 15 days protection periods for expired domains? Perhaps the validation_notify1_period and validation_notify2_period fields?.
Best regards.
P.S: my documentation for FRED 2.2.0 is almost ready. I think I'm including there interesting values in enum_parameters. Where should I upload it?.
--
Mario Guerra <mguerra(a)nic.cr>
We are about to fully migrate to FRED from our home-made system.
Now, what we want to do is to create domains in FRED according with our expiration date information. But there is one problem: create_domain takes the date from the system, so if I use create_domain today for say, a year, it would create the domain with an expiration date of 6th. June, 2012, which is what I don't want (suppose that that domain was created, say, 6 months ago using our home-made system, the expiration date would be 6th. January 2012).
One solution would be to modify the ex_date field in the domain_registry table according to our original information.
Does this make sense?. Is there any cleaner way of doing this?
Best regards.
--
Mario Guerra <mguerra(a)nic.cr>
