The details on KDE.ru can be found in T9661 - looks like @aspotashev knows how to contact the domain owner.

For QtCon.org, i've searched my records and can't find any details as to which registrar this one is registered with.
Whois says it is owned by the KDE e.V. though, but eNom isn't a registrar i'm aware of us using.

Lydia, Eike, Aleix, any ideas as to if there is a another registrar account somewhere? (by the looks of it, solely used for QtCon.org)

In T12262#211569, @bcooksley wrote:

The details on KDE.ru can be found in T9661 - looks like @aspotashev knows how to contact the domain owner.

Domain registrar for kde.ru is RU-CENTER ( https://www.nic.ru/ ).

I don't know how to contact the owner directly, but

1. I know their full name. However it would be incorrect to make it public without their permission.
2. Grigory Mokhin (Russian KDE team coordinator in 2000-2010) does the renewal payments and he presumably knows how to contact the owner.

To answer "if we have control about thes domains": we don't have control over kde.ru because

• The owner might decide to use kde.ru for something else.
• Bus factor for renewal payments is 1 (that is Grigory Mokhin). If neither him nor the domain owner does the payment in a certain year, the domain would expire.

In T12262#211569, @bcooksley wrote:

For QtCon.org, i've searched my records and can't find any details as to which registrar this one is registered with.
Whois says it is owned by the KDE e.V. though, but eNom isn't a registrar i'm aware of us using.

Lydia, Eike, Aleix, any ideas as to if there is a another registrar account somewhere? (by the looks of it, solely used for QtCon.org)

I am not sure how that was handled back then anymore but maybe @kcoyle remembers or knows more?

@aspotashev

Hi,

can you ask either one to change the namservers to the following set:

pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

I guess both can make that change. If you ever want to reduce the chance of non-payment, it might be an idea to provide the sysadmin team with the credentials. But let's first complete the nameserver change.

@aspotashev any luck reaching out to them?
@kcoyle any idea about qtcon.org?

In T12262#211657, @toma wrote:

@aspotashev

Hi,

can you ask either one to change the namservers to the following set:

pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

I guess both can make that change. If you ever want to reduce the chance of non-payment, it might be an idea to provide the sysadmin team with the credentials. But let's first complete the nameserver change.

You meant dns31.cloudns.net and so on through dns34.cloudns.net ?

No, it's literally pns: https://www.cloudns.net/wiki/article/355/

In T12262#212105, @nalvarez wrote:

No, it's literally pns: https://www.cloudns.net/wiki/article/355/

How come kde.org returns dns31?

[aspotashev@candy ~]$ nslookup -query=any kde.org 
...
kde.org nameserver = dns31.cloudns.net.
kde.org nameserver = dns32.cloudns.net.
kde.org nameserver = dns33.cloudns.net.
kde.org nameserver = dns34.cloudns.net.

because kde.org are on a different setup.

In T12262#211657, @toma wrote:

can you ask either one to change the namservers to the following set:

pns31.cloudns.net
pns32.cloudns.net
pns33.cloudns.net
pns34.cloudns.net

Done. Nameservers changed.

Thanks @aspotashev for sorting that out.

That just leaves QtCon.org. Would it be possible that Digia/The Qt Company registered the domain rather than us?

@filipesaraiva / @sandroandrade Do you happen to know who owns the qtcon.org domain name registration?

It was originally registered by TQtC, and we then had it point its dns servers to us so we could manage it

old sysadmin Ticket ID #WHQ-9986 (10/2/16) discussed setting name servers and Registrant but i haven't found if anything happened beyond that. my guess would be not

this was requested by me and dealt with by Ben in conjunction with Tero from TQtC (and their sysadmins)

Ok, then we will have to contact them.

Thanks for the search Kenny.

speak to fregl probably as a good way in