About this matter i need to ask one more question:
I told you this before:
When the customer makes a B application, the domain will be created 1 month after the
application is done.
Another thing is (according to our rules), that it should also be possible for other
customers to apply for the same domain name in this period.
So the question is:
Is it possible to create 2 or more of the same domain name, when the first one has got
another object state ?
________________________________________
Fra: fred-users-bounces(a)lists.nic.cz [fred-users-bounces(a)lists.nic.cz] På vegne
af Jaromír Talíř [jaromir.talir(a)nic.cz]
Sendt: 14. november 2008 14:56
Til: fred-users(a)lists.nic.cz
Emne: Re: Disable domain ? (object state description)
Yes, this is possible with Fred because of feature called "object
states". Each object in Fred (domain, contact, nsset, keyset) can have
associated some states. Some of them can be assigned automatically, for
example domain state 'Expired' is set according to current time and
domain.exdate. Some of them can be assigned manually as
serverTransferBlocked. These states usually "trigger" some action (email
notification, registrar epp poll message creation, object
unregistration..) All this activity is done in call fred-admin
--object_regular_procedure. So proper Fred installation needs to put
this call into cron script and call it every day.
I attached one old document describing it in more detail. All is driven
by set of postgresql procedures in fred-db/sql/states.sql.
One of these states is 'serverOutzoneManual'. These state blocks domain
from generation into zone, so it's technically "disabled".
There should be a dialog in web administration to support this feature
but it's not there right now, so you need to issue these two sql
commands (you must now ID of domain):
sql>INSERT INTO object_state_request (object_id,state_id,valid_to)
VALUES (ID,7,CURRENT_TIMESTAMP+INTERVAL '1 month');
sql>SELECT update_object_state(ID);
After month, daily procedure will clean this state and domain will get
into zone.
Regards,
Jaromir
Petur Kirke píše v St 05. 11. 2008 v 14:22 +0000:
In Faroe Islands we have 2 kinds of domain
applications named A applications and B applications.
When the customer makes an A application, the domain is created immediately.
When the customer makes a B application, the domain will be created 1 month after the
application is done.
So my question is:
Is it possible to create one domain (incl. contacts, nameservers) in FRED, and make it
DISABLED until 1 month is gone ?
Or do i have to save all the information outside of FRED until 1 month is gone, and then
create the domain in FRED ?
regards
Petur
This email and its attachments may be confidential and are intended solely for the use of
the individual to whom it is addressed.
If you are not the intended recipient or authorized to receive information for the
intended recipient you are notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this information is strictly prohibited. If the
email contains proposals, they are valid for 30 days following the date of email
transmission. Finally, the recipient should check this email and any attachment for the
presence of viruses. The company accepts no liability for any damage caused by any virus
transmitted by email.
_______________________________________________
Fred-users mailing list
Fred-users(a)lists.nic.cz
https://lists.nic.cz/mailman/listinfo/fred-users
This email and its attachments may be confidential and are intended solely for the use of
the individual to whom it is addressed.
If you are not the intended recipient or authorized to receive information for the
intended recipient you are notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this information is strictly prohibited. If the
email contains proposals, they are valid for 30 days following the date of email
transmission. Finally, the recipient should check this email and any attachment for the
presence of viruses. The company accepts no liability for any damage caused by any virus
transmitted by email.