Since we’ll be unable to offer any further domain setup sessions, I thought I’d put up this brief guide for students who have bought domain names via Gandi.net and would like to use them.
Other domain registrars will vary, but carefully following these steps will ensure that your domain is properly set up.
Your Gandi username (called a “handle”) and password will be necessary, so if you haven’t got those, they will have been e-mailed to you from Gandi when you registered the domain.
1. Log in to Gandi

2. Select the domain
When you log in, you should be take straight to your domains list page. If you are not, you can find it in the main navigation under Manage > Domains.

3. Click “Manage DNS Zone File”
You will find this towards the bottom of the page.

4. Update DNS Records
You’ll see a summary of the domain information attached to your domain.
Each row in the table is called a record.
You need to make sure that there is are two “A” type records, one for “www” and one for “@”, both pointing to the IP address 92.243.28.163:

You can modify a record by clicking on the associated pencil, to the right, and delete it by clicking the X.
Initially there will be a CNAME record for “www” which you need to delete. Don’t worry – it’s quite safe. None of your changes will have any affect until the next step and can easily be undone.
Now add a new A record for “www”, and update the one for “@”.
Each record will look like this when you edit or create it:

TTL is not hugely important, but I usually set it to 30 minutes. It’s just to do with how quickly this setting will update next time you change it.
5. Save your changes
Your changes haven’t been saved yet. A notice will appear above the DNS records advising you of this, and asking you what to do:

Click “Submit Changes” to make your changes final.
6. Tell Marcus
Use the contact form on this website to notify Marcus, who will make a change to the server as a final step. This may take a few days as Marcus is very busy and has lots of non-city work as well as things at City.


This post has no comment.
Commenting Guidelines