tickets #88520
closedmigrating all remaining OpenSUSE domains
0%
Description
Hi,
Last year we started to move OpenSUSE domains to be hosted and managed by OpenSUSE and moved opensuse.org / .de / .fr domains, but quite few are still hosted in SUSE R53 setup:
opensuse.asia.
opensuse.com.br.
opensuse.com.es.
opensuse.com.mx.
opensuse.com.
opensuse.co.
opensuse.eu.
opensuse.gen.tr.
opensuse.jp.
opensuse.kr.
opensuse.mx.
opensuse.net.
opensuse.org.cn.
and also few extras that I'm not sure should be moved here too ( I think yes, but will need additional confirmation ):
opensuse-project.com.
opensuse-project.de.
opensuse-project.net.
opensuse-project.org.
openslp.org.
I can prepare this on OpenSUSE side, but will need advice and support, as this would be my first change / work in this infra.
Thanks,
Files
Checklist
- preparing current zone dumps
- import new zones in chip
- change zone ns servers from SUSE R53 to nsx.opensuse.org
Updated by mdruvietis about 3 years ago
List of all current records attached. Almost all of them are empty domains pointing to o.o. by default. As by default you cannot have cnames in top level domain, in AWS R53 there is trick with alias. I would have to see o.o. dns setup first to figure out how to make work.
Additional point: all of those redirected pages ssl is currently boken: if you go to http://opensuse.asia it redirects properly to https://opensuse.org, but https://opensuse.asia will fail. Instead of applying fix on SUSE IT setup, we could bring this to HA proxy and do this job there.
In any case I will need to sort my access to vpn and other places before I can do any action myself.
Updated by mdruvietis about 3 years ago
- File o_o_domains_todo o_o_domains_todo added
Updated by mdruvietis about 3 years ago
- Checklist item changed from to [x] preparing current zone dumps
Updated by cboltz about 3 years ago
For the domains that have MX mx2.suse.de, can you please check which mail addresses exist there so that we can handle them on mx*.o.o?
Updated by lrupp almost 3 years ago
- Category set to Core services and virtual infrastructure
Updated by pjessen almost 2 years ago
- Status changed from New to Resolved
- Private changed from Yes to No
As far as I can tell, ignoring openslp.org all of those domains are now served by pdns on chip.