Note that this is also true of .biz domains, and we're working on a better
solution (without having to force you to run three commands, or even
ourselves to do this on your behalf - I get nervous altering a lock state
without explicit permission)
i.e. having the registry provide a differentiation between "don't allow
transfer" and "lock the domain down from everything including force majeure"
Charles Daminato
OpenSRS Product Manager
Tucows Inc. - chuck@tucows.com
> -----Original Message-----
> From: owner-discuss-list@opensrs.org
> [mailto:owner-discuss-list@opensrs.org]On Behalf Of John Keegan
> Sent: September 13, 2002 9:01 PM
> To: discuss-list@opensrs.org
> Subject: Re: INFO domains and WHOIS
>
>
> Just a follow-up on this issue.
>
> It has recently been discovered that contact changes to locked
> .INFO domains
> will fail. Unlike other tlds which disallow only nameserver changes and
> transfer while locked, .INFO domains will additionally disallow contact
> changes (including email address contact changes).
>
> You can however, unlock, update and re-lock. Thought you all might like to
> know...
>
> --
> John Keegan
> john@RackShare.com
> http://RackShare.com
>
>
> > From: "Charles Daminato" <chuck@tucows.com>
> > Date: Mon, 9 Sep 2002 07:18:21 -0400
> > To: "John Keegan" <john@rackshare.com>, <discuss-list@opensrs.org>
> > Subject: RE: INFO domains and WHOIS
> >
> > John (et al)
> >
> > In discussing with our development group I've uncovered the
> potential cause
> > for this problem. When we do changes (in bulk or singular), a seperate
> > process is split to perform those changes. We send "success"
> messages via
> > the API (manage.opensrs.net as well) to prevent timeouts. This
> process was
> > put into place as we moved to thick registry models (.biz and .info
> > especially) and we found that a bulk change across more than 1 registry
> > (even if it was only a handful of domains) would time out.
> >
> > The process would then attempt the changes (which may or may not be
> > successful when actually talking to the registry). 99% of the time this
> > seems to work fine. It would seem that we've had a lot of failures with
> > .info lately, which we're digging deeper into.
> >
> > To minimize impact on changes, please attempt only one domain
> change at a
> > time (where possible), and I'll let you know.
> >
> > FWIW, the info at .info is authoritative (since they're thick) so our
> > default action is to sync. Perhaps we should be trusting our
> information?
> >
> > Charles Daminato
> > OpenSRS Product Manager
> > Tucows Inc. - chuck@tucows.com
> >
> >> -----Original Message-----
> >> From: owner-discuss-list@opensrs.org
> >> [mailto:owner-discuss-list@opensrs.org]On Behalf Of John Keegan
> >> Sent: September 7, 2002 10:29 AM
> >> To: discuss-list@opensrs.org
> >> Subject: Re: INFO domains and WHOIS
> >>
> >>
> >> I made changes to the Billing and Technical contacts of a .INFO
> >> domain last
> >> night, and while in the manage.cgi, went back and looked at the
> >> Billing and
> >> Technical contacts and the updated email addresses were there.
> >>
> >> This morning, I check in the RWI and the changes have been
> dropped and the
> >> previous email addresses are now there.
> >>
> >> Can anyone confirm this bug? I think there is some problem with OpenSRS
> >> dropping changes for .INFO domains; seems like something triggers
> >> OpenSRS to
> >> re-sync their local database with an out of date version at the INFO
> >> registry.
> >>
> >> --
> >> John Keegan
> >> john@RackShare.com
> >> http://RackShare.com
> >>
> >>
> >>> From: John Keegan <john@rackshare.com>
> >>> Date: Mon, 2 Sep 2002 22:17:58 -0400
> >>> To: <discuss-list@opensrs.org>
> >>> Subject: INFO domains and WHOIS
> >>>
> >>> It seems like the OpnSRS whois does not show the most recent
> >> information for
> >>> INFO domains for which it is authoritative. Is there a
> reason for this?
> >>>
> >>> When I make change to an INFO domain through the management
> >> interface, the
> >>> change is not reflected in the OpenSRS whois as it would be,
> >> say, for COM
> >>> domains. Seems like the whois goes and gets whatever is at the
> >> INFO registry
> >>> and returns that instead of local data. Which is not good,
> >> since it seems
> >>> like the INFO registry does not update the WHOIS ver quickly...
> >>>
> >>> --
> >>> John Keegan
> >>> john@RackShare.com
> >>> http://RackShare.com
> >>>
> >>>
> >>
> >
>
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:27 EDT