Opened 3 years ago

Closed 3 years ago

#11462 closed Task/To do item (fixed)

set up new AUSM.community domain

Reported by: Tony Nelson Owned by: JaimeV
Priority: High Component: Tech
Keywords: Cc:
Sensitive: no

Description

Please help/let us get working on our new site. We want to apply the WordPress theme we have chosen and start to design and copy from our old site. Our Member Name is: MSN

But we'd also like to create a separate login for the student web team that is helping us with the project.

Change History (14)

comment:1 Changed 3 years ago by JaimeV

Owner: set to JaimeV
Status: newassigned

Great. I see you've already created a hosting order for ausm.community and I see you created an initial user tony. As the default user tony has server access to the area where you can mount your new wordpress site.

You can access the server over sftp with tony's username and password. https://support.mayfirst.org/wiki/faq/files/sftp

Once you have access you can begin installing a new wordpress instance there. https://support.mayfirst.org/wiki/WordPress

If you want to give server access to someone other than tony you can create a new user and add them to the "server access" tab.

However... in practice sharing sftp access to the website files on the server with more than one user doesn't work out so well. For now the web configuration expects the web files to be owned and processed by user tony. This can be changed to another user name by editing your web configuration in the web configurtaion tab but it is best to choose one username to be the owner of your web files and stick with that.

Does that make sense?

Last edited 3 years ago by JaimeV (previous) (diff)

comment:2 Changed 3 years ago by JaimeV

Resolution: fixed
Status: assignedclosed

comment:3 Changed 3 years ago by Tony Nelson

Hi Jamie, sorry to bother you again. The verification with google has failed yet again. When I look at the DNS settings on MayFirst it shows that Distance is different than weight. All the weight column is filled with 0s instead of the 1,5,5,10,10 that Google recommends. Could that be the issue?

comment:4 Changed 3 years ago by Tony Nelson

Resolution: fixed
Status: closedassigned

comment:5 Changed 3 years ago by JaimeV

Hi do you have guide that shows google's recommended DNS settings for directing your domain to their e-mail servers? You can set distance values for some types of DNS records through the control panel.

comment:6 Changed 3 years ago by Tony Nelson

Yes, here they are pasted below:

Changing Mail Exchange (MX) records Mail Exchange (MX) records control how incoming email is routed for your domain. Before Google can host your email, you'll need to change these MX records to point to our servers.

If your domain already has email addresses, please be careful changing MX records. To avoid disruption in email service, be sure to create the same set of user accounts with the control panel before changing your MX records Learn more

Sign in to your domain hosting company's website using the username and password associated with your domain.

Navigate to an MX record maintenance page. MX records are special DNS (Domain Name Service) records, and are often located under sections titled "DNS Management," "Mail Server Configuration," or "Name Server Management." You may need to turn on advanced settings to allow editing of these MX records.

Delete any existing MX records before entering new MX records.

For each MX record, enter information according to the entries in the following table.

You may not be allowed to enter the priority values exactly as they appear in the table below; in that case, simply ensure that the server addresses are prioritized in the same order as they appear in the table. (i.e. The priority ranking [1, 3, 3, 5, 5, 5, 5] should work just as well as [1, 5, 5, 10, 10, 10, 10] so long as you keep the addresses in the right order.)

If you're asked to specify the type of each record you're adding, enter "MX". MX records often require the specific format of DNS records, including a trailing dot (".") at the end of any full-qualified domain names (e.g. "server.example.com.") Set any TTL values to the maximum allowed. MX Server address Priority

ASPMX.L.GOOGLE.COM. 1 ALT1.ASPMX.L.GOOGLE.COM. 5 ALT2.ASPMX.L.GOOGLE.COM. 5 ASPMX2.GOOGLEMAIL.COM. 10 ASPMX3.GOOGLEMAIL.COM. 10

Change the SPF record to fight SPAM (optional) You may define the SPF record to authorize only certain IP addresses to send email for your domain. This will prevent spammers from sending unauthorized email under a forged address from your domain.

comment:7 Changed 3 years ago by Jamie McClelland

Hi Tony,

The priority/distance settings are set up properly.

However, it looks like the domain names are entered incorrectly on two of your records.

You have:

  • 10 alt3.aspmx.l.google.com.
  • 10 alt4.aspmx.l.google.com.

But the directions specify:

  • 10 ASPMX2.GOOGLEMAIL.COM.
  • 10 ASPMX3.GOOGLEMAIL.COM.

I just fixed them for you.

comment:8 Changed 3 years ago by Tony Nelson

Hi. I actually have seen that happen already after I put them in the first time. I'm not sure what would cause it, but I put copied and pasted them correctly both times, then the system for some reason is creating "alternates." Why would that be you think?

comment:9 Changed 3 years ago by Jamie McClelland

Strange - I have no idea why that would happen.

However, it seems that they are properly entered now:

0 jamie@turkey:~$ dig +short @a.ns.mayfirst.org -t mx ausm.community
1 aspmx.l.google.com.
5 alt1.aspmx.l.google.com.
5 alt2.aspmx.l.google.com.
10 aspmx2.googlemail.com.
10 aspmx3.googlemail.com.
0 jamie@turkey:~$ 

comment:10 Changed 3 years ago by Tony Nelson

Thanks. I'll check back tomorrow to see if the validation went through, but it's saying that it failed still. We'll also have to check if it gets changed again - most likely that it will since it already did it once, no?

comment:11 Changed 3 years ago by Jamie McClelland

It looks like the changes I made are sticking - let me know if you notice that they change.

And, if validation still fails (mabye there is another obscure typo or mistake we made).

comment:12 Changed 3 years ago by JaimeV

Resolution: fixed
Status: assignedfeedback

Did this work out for you?

comment:13 Changed 3 years ago by Tony Nelson

Resolution: fixed
Status: feedbackassigned

The changes stuck and it's now verified. Thanks a bunch, Jamie.

comment:14 Changed 3 years ago by Jamie McClelland

Resolution: fixed
Status: assignedclosed

Great!

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.