Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Common scenarios #13

Merged
merged 13 commits into from
May 9, 2016
Merged

Common scenarios #13

merged 13 commits into from
May 9, 2016

Conversation

edwardloveall
Copy link
Contributor

These are the rest of the common scenarios. The list now includes:

  • Creating a subdomain
  • Transferring a domain
  • Connecting your domain to an external service
  • Remove www from your domain
  • Create a CNAME records on the Apex domain
  • My old website data is showing up
  • Redirect one domain to another

Some are new, some have been edited a bit. I obviously can't cover every possible permutation of even these few scenarios, but I'm hoping that this covers a wide range of common questions and situations.


Getting a new domain is fun and all, but it can take some time to setup. A common problem is the website will show up as either nothing, or some kind of placeholder page.

Let's say you get a domain from Donkey Domains. With no setup what-so-ever, it will likely point to a placeholder page with a "website coming soon" message. There are two likely problems.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"whatsoever" is a real word, unless you just like the hyphens

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

likely is not needed. Can also be possible.

@joshuaogle
Copy link

I found a few grammatical things, but the technical stuff all sounded right from what I know. Switching between you in the earlier parts to we in the later parts seemed like it may have been unintentional, but it was pretty well split up so it may not be an issue. The humorous examples really help keep things engaging 🐴 .

👍

@tute
Copy link

tute commented Apr 29, 2016

The humorous examples really help keep things engaging 🐴

👍


These services are great, but they often give you a relatively non-personal URL, something like `your-name.service.com`. That works fine enough for testing, but running a serious business (such as renting donkeys) needs a professional and trustable domain name.

Sometimes, services will offer to sell you a domain up front. Obviously, domain experts like us don't need that kind of handholding. We want to be in control of our domains! What if we decide to switch services? Or have subdomains that point to other services? For me personally, this "solution" isn't flexible enough.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: change "solution" by alternative (no quotes).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I went with offering. I'm trying to guide people away from the pre-configured solution since this whole book is about learning how things work under the hood.

@edwardloveall edwardloveall merged commit 777e0d5 into master May 9, 2016
@edwardloveall edwardloveall deleted the common-scenarios branch May 9, 2016 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants