Opened 6 years ago

Closed 6 years ago

#2272 closed task (fixed)

Change of DNS records for deegree.org and www.deegree.org required

Reported by: Tfr42 Owned by: sac@…
Priority: normal Milestone: Sysadmin Contract 2019-I
Component: SysAdmin/DNS Keywords:
Cc: tmc@…, Tfr42, stephanr

Description (last modified by robe)

Please apply the following changes to the DNS entry for the domain "deegree.org".

We would like to move the deegree.org website to github.pages. From our understanding this requires a DNS update to set a CNAME from deegree.org to deegree.github.io and also a CNAME from www.deegree.org to deegree.github.io:

@                        IN CNAME          

I remove.
www                      IN CNAME          deegree.github.io.

In case of questions please contact: tmc (AT) deegree.org.

Reference:

Change History (13)

comment:1 by Tfr42, 6 years ago

Cc: tmc@… added

Added TMC to cc:

comment:2 by robe, 6 years ago

Description: modified (diff)
Milestone: Sysadmin Contract 2019-I

you had two A records

@ » 136.243.175.5 plaza » 136.243.175.5

I removed those and replaced them with 2 cnames:

@ -> deegree.github.io plaza -> deegree.github.io www -> deegree.github.io

most everything else looks like it points to plaze which just seems to redirect to www.degree.org

so not sure what the purpose of that is.

I tested and seems to go to github now, but ssl cert is not in place, so guess you'll need to do that.

comment:3 by robe, 6 years ago

Resolution: fixed
Status: newclosed

comment:4 by robe, 6 years ago

I put the plaza one back because it seems it is connected to a lot of things not related to website.

Many of these you have moved to github though I think. So let me know if you want to do anything with these. Changed these

@ » deegree.github.io.
www » deegree.github.io. 

Left these alone

plaza » 136.243.175.5 

apidoc » plaza.deegree.org.
artefacts » plaza.deegree.org.
buildserver » plaza.deegree.org.
cite » plaza.deegree.org.
deegree3-demo » plaza.deegree.org.
deegree3-testing » plaza.deegree.org.
demo » plaza.deegree.org.
download » plaza.deegree.org.
drupal » plaza.deegree.org.
drupal-test » plaza.deegree.org.
nexus » plaza.deegree.org.
ogcri » plaza.deegree.org.
repo » plaza.deegree.org.
schemas » plaza.deegree.org.
wiki » plaza.deegree.org.
Last edited 6 years ago by robe (previous) (diff)

comment:5 by stephanr, 6 years ago

Cc: Tfr42 stephanr added
Resolution: fixed
Status: closedreopened

I reopened the ticket because it looks like not only the DNS entries for the website www.deegree.org resp. deegree.org have been changed.

It looks like MX records have been removed too, because no email can currently be received for deegree.org.

Regarding the certificate for deegree.org/www.deegree.org could only be set correctly after the DNS settings were adjusted (because letsencrypt is used by github-pages). Now the page can be displayed without SSL problems.

All DNS entries that are not related to the website, such as the MX-records, plaza.deegree.org and its aliases, should remain unchanged, as these are still needed even if some pages are redirecting to www.deegree.org.

Could you please review the changes ?

comment:6 by robe, 6 years ago

Hmm there weren't any mx records. I saw a lot of email forwards done directly using Pairs system.

I just send an email to psc@… if you got that email then those are still working fine.

comment:7 by robe, 6 years ago

just resent my note to tmc@…

in reply to:  7 comment:8 by stephanr, 6 years ago

Replying to robe:

just resent my note to tmc@…

I have no access to e-mails to psc@…, I am only on the list/forwarder of tmc@….

However, since the weekend no emails have reached me via the list tmc@… (incl. your mail).

Replying to robe:

Hmm there weren't any mx records. I saw a lot of email forwards done directly using Pairs system.

I just send an email to psc@… if you got that email then those are still working fine.

For me it looks like the MX records have been removed or if they were generated automatically before, they are currently not generated any more.

comment:9 by robe, 6 years ago

I see two forwards a psc and a tmc one. I added myself to tmc to see if I would get the email and I didn't. Though it may have gone into my junk mail so verifying.

I'll put in a call to Pair if I can't figure it out. At a glance looks all setup right.

comment:10 by robe, 6 years ago

I figured out the problem. I see what you mean that the MX records disappeared.

The issue was that even though Pair let's me put in a CNAME for degree.org (converts it to @) and it works that evidentally somehow makes it strip out it's own MX records which aren't editable from the interface.

So to fix I had to change the

CNAME @ deegree.github.io

to

A @  185.199.110.153

After I did that I started getting the deegree.org emails to tmc (after adding myself to the list). It's not ideal. Does anyone have a though on how to have an CNAME @ and not screw up the MX.

I guess alternatively I could explicitly add in the MX of pair, but then that would be screwed if they change it.

comment:11 by robe, 6 years ago

Although hmm that seems to have broken the SSL for deegree.org or perhaps that wasn't working?

comment:12 by stephanr, 6 years ago

I have checked the settings of the github-pages, and also started an update, which did not lead to the desired working result.

The SSL settings were running when the CNAME was still present, but it is also documented on the github pages that forwarding (deegree.org and www.deegree.org simultaneously) can cause problems with some providers.

After talking to another TMC member, we decided to redirect only www.deegree.org via CNAME to Github pages and continue to use our own server (plaza.deegree.org/136.243.175.5) for the redirection of deegree.org to www.deegree.org. (Which should also solve our SSL problem)

Can you please adjust the two records in this way?

@                        IN A              136.243.175.5
www                      IN CNAME          deegree.github.io.

comment:13 by robe, 6 years ago

Resolution: fixed
Status: reopenedclosed

Done. Feel free to reopen if you still have issues

Note: See TracTickets for help on using tickets.