Opened 5 years ago
Closed 4 years ago
#2356 closed task (fixed)
2020.foss4g.org A record
| Reported by: | pramsey | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | SysAdmin | Keywords: | |
| Cc: |
Description
Can we have an 'A' record pointing to 184.168.131.241 please?
Change History (6)
comment:1 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 5 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Not working, I think something is wrong with the redirect on your side. Looks like maybe you're using Cloudflare or AWS, and something might need to be changed on that end.
comment:3 by , 5 years ago
The IP given was to some sort of URL shortener/redirector and didn't work. After getting the IP for the true site: $ dig +short 2020foss4g.ca 52.60.138.213 35.183.196.77 I pointed to the first IP returned. Depending on the hosting service this may not be reliable (if IPs can shift). So let me know if this should be different. Otherwise the DNS works now.
comment:4 by , 5 years ago
Can we try a CNAME to 2020foss4g.ca? Maybe that will be better? 2020foss4g.com is a HTTP redirect, but 2020foss4g.ca appears to be an actual server. Unfortunately the hosting co seems to migrate it around to different IPs on their own schedule.
comment:5 by , 5 years ago
Ok swapped to CNAME, should be working in an hour. Let us know if it's not.
PS: After it's working please make sure to get an https cert working.
comment:6 by , 4 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Removed the CNAME to www.foss4g2020.com and add A record as requested. Why are we not pointing directly at 2020foss4g.ca servers? The redirect service being used seems fragile, at least on my browser.