/
operations-dns-designate_initialconfig.xml
165 lines (165 loc) · 6.85 KB
/
operations-dns-designate_initialconfig.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
<?xml version="1.0"?>
<!DOCTYPE section [
<!ENTITY % entities SYSTEM "entity-decl.ent"> %entities;
]>
<section xml:id="designateInitialConfig"
xmlns="http://docbook.org/ns/docbook" version="5.1"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink">
<title>&desig; Initial Configuration</title>
<para>
After the &productname; installation
has been completed, &desig; requires initial configuration to operate.
</para>
<section xml:id="sec-designate-identify">
<title>Identifying Name Server Public IPs</title>
<para>
Depending on the back-end, the method used to identify the name servers'
public IPs will differ.
</para>
<section xml:id="sec-designate-infoblox">
<title>InfoBlox</title>
<para>
InfoBlox will act as your public name servers, consult the InfoBlox
management UI to identify the IPs.
</para>
</section>
<section xml:id="sec-designate-bind">
<title>BIND Back-end</title>
<para>
You can find the name server IPs in <filename>/etc/hosts</filename> by
looking for the <literal>ext-api</literal> addresses, which are the
addresses of the controllers. For example:
</para>
<screen>
192.168.10.1 example-cp1-c1-m1-extapi
192.168.10.2 example-cp1-c1-m2-extapi
192.168.10.3 example-cp1-c1-m3-extapi
</screen>
</section>
<section xml:id="sec-designate-a-record">
<title>Creating Name Server A Records</title>
<para>
Each name server requires a public name, for example
<literal>ns1.example.com.</literal>, to which &desig;-managed domains will
be delegated. There are two common locations where these may be registered,
either within a zone hosted on &desig; itself, or within a zone hosted on a
external DNS service.
</para>
<para>
<emphasis role="bold">If you are using an externally managed zone for these
names:</emphasis>
</para>
<procedure>
<step>
<para>
For each name server public IP, create the necessary A records in the
external system.
</para>
</step>
</procedure>
<para>
<emphasis role="bold">If you are using a &desig;-managed zone for these
names:</emphasis>
</para>
<procedure>
<step>
<para>
Create the zone in &desig; which will contain the records:
</para>
<screen>&prompt.ardana;openstack zone create --email hostmaster@example.com example.com.
+----------------+--------------------------------------+
| Field | Value |
+----------------+--------------------------------------+
| action | CREATE |
| created_at | 2016-03-09T13:16:41.000000 |
| description | None |
| email | hostmaster@example.com |
| id | 23501581-7e34-4b88-94f4-ad8cec1f4387 |
| masters | |
| name | example.com. |
| pool_id | 794ccc2c-d751-44fe-b57f-8894c9f5c842 |
| project_id | a194d740818942a8bea6f3674e0a3d71 |
| serial | 1457529400 |
| status | PENDING |
| transferred_at | None |
| ttl | 3600 |
| type | PRIMARY |
| updated_at | None |
| version | 1 |
+----------------+--------------------------------------+
</screen>
</step>
<step>
<para>
For each name server public IP, create an A record. For example:
</para>
<screen>
<?dbsuse-fo font-size="0.7em"?>
&prompt.ardana;openstack recordset create --records 192.168.10.1 --type A example.com. ns1.example.com.
+-------------+--------------------------------------+
| Field | Value |
+-------------+--------------------------------------+
| action | CREATE |
| created_at | 2016-03-09T13:18:36.000000 |
| description | None |
| id | 09e962ed-6915-441a-a5a1-e8d93c3239b6 |
| name | ns1.example.com. |
| records | 192.168.10.1 |
| status | PENDING |
| ttl | None |
| type | A |
| updated_at | None |
| version | 1 |
| zone_id | 23501581-7e34-4b88-94f4-ad8cec1f4387 |
+-------------+--------------------------------------+
</screen>
</step>
<step>
<para>
When records have been added, list the record sets in the zone to
validate:
</para>
<screen>
<?dbsuse-fo font-size="0.70em"?>
&prompt.ardana;openstack recordset list example.com.
+--------------+------------------+------+---------------------------------------------------+
| id | name | type | records |
+--------------+------------------+------+---------------------------------------------------+
| 2d6cf...655b | example.com. | SOA | ns1.example.com. hostmaster.example.com 145...600 |
| 33466...bd9c | example.com. | NS | ns1.example.com. |
| da98c...bc2f | example.com. | NS | ns2.example.com. |
| 672ee...74dd | example.com. | NS | ns3.example.com. |
| 09e96...39b6 | ns1.example.com. | A | 192.168.10.1 |
| bca4f...a752 | ns2.example.com. | A | 192.168.10.2 |
| 0f123...2117 | ns3.example.com. | A | 192.168.10.3 |
+--------------+------------------+------+---------------------------------------------------+
</screen>
</step>
<step>
<para>
Contact your domain registrar requesting <emphasis>Glue
Records</emphasis> to be registered in the
<literal>com.</literal> zone for the nameserver and public
IP address pairs above. If you are using a sub-zone of an existing
company zone (for example, <literal>ns1.cloud.mycompany.com.</literal>),
the Glue must be placed in the <literal>mycompany.com.</literal> zone.
</para>
</step>
</procedure>
</section>
<section xml:id="sec-designate-more">
<title>For More Information</title>
<para>
For additional DNS integration and configuration information, see the
&ostack; &desig; documentation at
<link xlink:href="https://docs.openstack.org/designate/rocky/"/>.
</para>
<para>
For more information on creating servers, domains and examples, see the
&ostack; REST API documentation at
<link xlink:href="https://developer.openstack.org/api-ref/dns/"/>.
</para>
</section>
</section>
</section>