I think tucows stole my domain

[do...@02.usenet.us.com]

It would seem that my domain has been poached.
http://clearlakeysl.org used to be a Yahoo site, and then we moved to
eteamz in June 2011, and that name would land at
http://www.eteamz.com/clearlakeyouthsoccerleague/

Now it lands at tucows.com.

Using tucows to look up the domain information shows
Domain Name:CLEARLAKEYSL.ORG
Created On:12-Mar-2008 16:23:38 UTC
Last Updated On:16-Mar-2013 03:50:06 UTC
Expiration Date:12-Mar-2014 16:23:38 UTC
Sponsoring Registrar:Tucows Inc. (R11-LROR)
Status:CLIENT TRANSFER PROHIBITED
Status:CLIENT UPDATE PROHIBITED
Status:AUTORENEWPERIOD

The "Last Updated" date might be when it stopped working, although I
thought I had used it as recently as March 27th.

It was supposed to autorenew, but maybe it did expire, and tucows
immediately poached it. They don't offer any obvious way to get it
back.

--
Clarence A Dold - Hidden Valley Lake, CA, USA GPS: 38.8,-122.5

[Keith Keller]

On 2013-04-03, do...@02.usenet.us.com <do...@02.usenet.us.com> wrote:
> It would seem that my domain has been poached.
> http://clearlakeysl.org used to be a Yahoo site, and then we moved to
> eteamz in June 2011, and that name would land at
> http://www.eteamz.com/clearlakeyouthsoccerleague/
>
> Now it lands at tucows.com.
>
> Using tucows to look up the domain information shows
> Domain Name:CLEARLAKEYSL.ORG
> Created On:12-Mar-2008 16:23:38 UTC
> Last Updated On:16-Mar-2013 03:50:06 UTC
> Expiration Date:12-Mar-2014 16:23:38 UTC
> Sponsoring Registrar:Tucows Inc. (R11-LROR)
> Status:CLIENT TRANSFER PROHIBITED
> Status:CLIENT UPDATE PROHIBITED
> Status:AUTORENEWPERIOD
>
> The "Last Updated" date might be when it stopped working, although I
> thought I had used it as recently as March 27th.

You are in the autorenew period, which means that if you can log in to
your registrar you should be able to renew the domain without risking
losing it. The rest of the whois still lists you as the admin (which I
won't post to usenet).

> It was supposed to autorenew, but maybe it did expire, and tucows
> immediately poached it. They don't offer any obvious way to get it
> back.

It hasn't been ''poached'' yet. There is a 30 day period (the
AUTORENEWPERIOD) where the domain may not work but is still not
available for purchase by others. But the ultimate registrar (which may
be tucows; some providers merely resell tucows' registrar service) can
point your domain wherever they want during AUTORENEWPERIOD.

Did you follow the link being displayed? It gives you a way to find out
who your provider is. In your case it says "Active Network, eteamzplussupport
[at] active.com". Since that may be eteams, that's probably your first
stop for help.

--keith

--
kkeller...@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

[David Kaye]

<do...@02.usenet.us.com> wrote

> The "Last Updated" date might be when it stopped working, although I
> thought I had used it as recently as March 27th.
>
> It was supposed to autorenew, but maybe it did expire, and tucows
> immediately poached it. They don't offer any obvious way to get it
> back.

Personally, I don't trust anybody's autorenew, so I keep my renewal dates on
my Outlook, which loads every time I run my main computer. I also keep a
physical calendar to remind me of renewal dates. Also, I set the reminders
2 months ahead of time just to make sure that I renew in plenty of time. I
had a struggle once with Network Solutions to move my domain name and lost
it because I was too late. I hope they were happy with davidkaye.net...

[do...@02.usenet.us.com]

Keith Keller <kkeller...@wombat.san-francisco.ca.us> wrote:
> You are in the autorenew period, which means that if you can log in to

...

> It hasn't been ''poached'' yet. There is a 30 day period (the
> AUTORENEWPERIOD) where the domain may not work but is still not

That all seems so obvious now.
When I noticed, I sent a support request via our normal web page interface
on the non-custom eteamz site that still works. No reply.

Only 30 days "RENEWAL"... for a Fall Soccer League, that could be a
timeframe that would be overlooked. I was just getting ready to open
registration for Fall 2013. If it had failed in February, I might not have
noticed.

Yesterday, I sent email to the "provider" address noted at tucows, and they
replied that it should all be working shortly.

The tucows whois listing has been changed, although I don't see that having
an effect yet.

The whois listing also has a dead email for me, pointing to the old domain,
which was a yahoo email. We don't have the extra cost email on the new
provider.

Our DNS registrar is probably reselling tucows. If I had known that, the
tucows entry would have been less alarming. I had asked about that when we
signed up, because I didn't think they really were registrars, but they
said they were, and I didn't examine it carefully.

[do...@02.usenet.us.com]

David Kaye <sfdavi...@yahoo.com> wrote:
> Personally, I don't trust anybody's autorenew, so I keep my renewal dates

I'll add an annual cron job, like I do with a few other expiring things.

> physical calendar to remind me of renewal dates. Also, I set the reminders

Physical Calendar? What's that?

I think I might do a "wget" in a weekly cron job, to verify that the home
page is returning what it should return. This is a seasonal page, only
used for 6-9 months a year, so a loss of registration might go unnoticed.
No users have complained.

> had a struggle once with Network Solutions to move my domain name and lost

I had a struggle with NSI, just about the time the whole registration
thingie changed, back in the mid 90's. I had one error there that repeats
itself here: a self-referencing email address.
If the domain is no good, you can't send or receive email to an address on
that domain.

[Roy]

On 4/3/2013 11:07 AM, do...@02.usenet.us.com wrote:
> ...

>
> I think I might do a "wget" in a weekly cron job, to verify that the home
> page is returning what it should return. This is a seasonal page, only
> used for 6-9 months a year, so a loss of registration might go unnoticed.
> No users have complained.
>

>...

You don't need to do a wget on the home page. Just put a file out there
called something like "webpagecheck" with some random text in it and
verify that.

The other thing to do is to write a cron job that checks all your domain
names and emails when they have less than "x" days left

Somebody wrote the script for you

http://www.cyberciti.biz/tips/domain-check-script.html

[do...@02.usenet.us.com]

Roy <aa...@aa4re.ampr.org> wrote:
> You don't need to do a wget on the home page. Just put a file out there
> called something like "webpagecheck" with some random text in it and
> verify that.

I did a
wget --quiet clearlakeysl.org --output-document=clearlake.html
diff clearlake.html GOOD-clearlake.html
as a script in cron.

> The other thing to do is to write a cron job that checks all your domain
> names and emails when they have less than "x" days left

I added a cron for that script, too.

[do...@02.usenet.us.com]

do...@02.usenet.us.com wrote:

> Roy <aa...@aa4re.ampr.org> wrote:
> > The other thing to do is to write a cron job that checks all your domain
> > names and emails when they have less than "x" days left

> I added a cron for that script, too.

Bummer. GMail thinks it's spam.
I said "not spam", so it might get straightened out, and I sent it on a
non-GMail path, which does arrive.
I don't actually log in to that GMail account, except for troubleshooting.

[Roy]

On 4/8/2013 7:14 PM, do...@02.usenet.us.com wrote:
> do...@02.usenet.us.com wrote:
>> Roy <aa...@aa4re.ampr.org> wrote:
>>> The other thing to do is to write a cron job that checks all your domain
>>> names and emails when they have less than "x" days left
>
>> I added a cron for that script, too.
>
> Bummer. GMail thinks it's spam.
> I said "not spam", so it might get straightened out, and I sent it on a
> non-GMail path, which does arrive.
> I don't actually log in to that GMail account, except for troubleshooting.
>

Add the sender to your gmail contacts list too :-)

[Roy]

On 4/8/2013 6:53 PM, do...@02.usenet.us.com wrote:
> Roy <aa...@aa4re.ampr.org> wrote:
>> You don't need to do a wget on the home page. Just put a file out there
>> called something like "webpagecheck" with some random text in it and
>> verify that.
>
> I did a
> wget --quiet clearlakeysl.org --output-document=clearlake.html
> diff clearlake.html GOOD-clearlake.html
> as a script in cron.
>

Email yourself the results. This might work

wget --quiet clearlakeysl.org --output-document=clearlake.html
diff clearlake.html GOOD-clearlake.html > /tmp/webpage.diff
if [ $? -ne 0 ] ; then
mail -s "Webpage diff" y...@somehting.net < webpage.diff
fi

[do...@02.usenet.us.com]

Roy <aa...@aa4re.ampr.org> wrote:
> On 4/8/2013 7:14 PM, do...@02.usenet.us.com wrote:
> > Bummer. GMail thinks it's spam.

> Add the sender to your gmail contacts list too :-)

Once I logged into that account, and clicked "not spam" on one of them,
they were all released from spam jail, and were retrieved by my other
account.

[do...@02.usenet.us.com]

Roy <aa...@aa4re.ampr.org> wrote:
> Email yourself the results. This might work

If there is any output from a cron job, it gets mailed.
No output, no mail.

[Roy]

On 4/10/2013 3:49 PM, do...@02.usenet.us.com wrote:
> Roy <aa...@aa4re.ampr.org> wrote:
>> Email yourself the results. This might work
>
> If there is any output from a cron job, it gets mailed.
> No output, no mail.
>

True but the email goes to the user that ran the job. By using the
script I showed, you can email it to anyone.

I have far too many servers to tend. Checking every server for job
output would be very tedious. All my scripts email a common mail
account that I monitor.

You could put something in the mail alias file and have it sent it
remotely but I prefer a common script

[Keith Keller]

On 2013-04-10, Roy <aa...@aa4re.ampr.org> wrote:
>
> True but the email goes to the user that ran the job. By using the
> script I showed, you can email it to anyone.

Vixie cron (and likely some others) support the MAILTO environment
variable in the crontab, so that an alternate email address can be
provided without having to redirect stdout.