File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change 3939 - Managing App Processes : applications/managing-app-processes.md
4040 - Managing App Configuration : applications/managing-app-configuration.md
4141 - Managing App Lifecycle : applications/managing-app-lifecycle.md
42+ - Domains and Routing : applications/domains-and-routing.md
4243 - SSL Certificates : applications/ssl-certificates.md
4344 - Managing Workflow :
4445 - Configuring Load Balancers : managing-workflow/configuring-load-balancers.md
Original file line number Diff line number Diff line change 1+ ## Domains and Routing
2+
3+ You can use ` deis domains ` to add or remove custom domains to your application:
4+
5+ $ deis domains:add hello.bacongobbler.com
6+ Adding hello.bacongobbler.com to finest-woodshed... done
7+
8+ Once that's done, you can go into your DNS registrar and set up a CNAME from the new
9+ appname to the old one:
10+
11+ $ dig hello.deisapp.com
12+ [...]
13+ ;; ANSWER SECTION:
14+ hello.bacongobbler.com. 1759 IN CNAME finest-woodshed.deisapp.com.
15+ finest-woodshed.deisapp.com. 270 IN A 172.17.8.100
16+
17+ !!! note
18+ Setting a CNAME for your root domain can cause issues. Setting your @ record
19+ to be a CNAME causes all traffic to go to the other domain, including mail and the SOA
20+ ("start-of-authority") records. It is highly recommended that you bind a subdomain to
21+ an application, however you can work around this by pointing the @ record to the
22+ address of the load balancer (if any).
Original file line number Diff line number Diff line change @@ -51,29 +51,6 @@ the application to an external PostgreSQL database.
5151
5252Detachments can be performed with ` deis config:unset ` .
5353
54- ## Custom Domains
55-
56- You can use ` deis domains ` to add or remove custom domains to your application:
57-
58- $ deis domains:add hello.bacongobbler.com
59- Adding hello.bacongobbler.com to finest-woodshed... done
60-
61- Once that's done, you can go into your DNS registrar and set up a CNAME from the new
62- appname to the old one:
63-
64- $ dig hello.deisapp.com
65- [...]
66- ;; ANSWER SECTION:
67- hello.bacongobbler.com. 1759 IN CNAME finest-woodshed.deisapp.com.
68- finest-woodshed.deisapp.com. 270 IN A 172.17.8.100
69-
70- !!! note
71- Setting a CNAME for your root domain can cause issues. Setting your @ record
72- to be a CNAME causes all traffic to go to the other domain, including mail and the SOA
73- ("start-of-authority") records. It is highly recommended that you bind a subdomain to
74- an application, however you can work around this by pointing the @ record to the
75- address of the load balancer (if any).
76-
7754
7855## Custom Health Checks
7956
You can’t perform that action at this time.
0 commit comments