Yes, but nobody can actually be using example.com, whereas somebody really is using domain.com. We have to use guaranteed-to-be-fake domains in Rackspace doc: example.com & example.org are always fake, always reserved for doc.

A Rackspace guaranteed-to-be-fake domain is kcexample.com but the Knowledge Center folks appreciate using that one themselves.

From: Ruben Orduz <notifications@github.com<mailto:notifications@github.com>>
Reply-To: "rackerlabs/developer.rackspace.com" <reply@reply.github.com<mailto:reply@reply.github.com>>
Date: Monday, June 2, 2014 at 3:57 PM
To: "rackerlabs/developer.rackspace.com" <developer.rackspace.com@noreply.github.com<mailto:developer.rackspace.com@noreply.github.com>>
Cc: Rose Coste <rose.coste@rackspace.com<mailto:rose.coste@rackspace.com>>
Subject: Re: [developer.rackspace.com] incorporate feedback on consistency of SDK Quickstart with API doc (#290)


In src/docs/cloud-dns/getting-started/samples/create_record.rst:

> @@ -5,7 +5,7 @@
>  .. code-block:: javascript
>
>    var recDetails = {
> -    name: 'app.domain.com',
> +    name: 'app.example.com',


Actually neither domain.com or example.com are good placeholders. The way rackspace DNS works, if there is that domain names have to be globally unique (within rackspace). So, if another user already has a example.com/domain.com, the person running this code will receive an exception, which could be a cause of frustration.

—
Reply to this email directly or view it on GitHub<https://github.com/rackerlabs/developer.rackspace.com/pull/290/files#r13306728>.