-
Notifications
You must be signed in to change notification settings - Fork 35
/
support.xml
308 lines (299 loc) · 8.29 KB
/
support.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
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
<caa:page xmlns="http://www.w3.org/1999/xhtml" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:caa="http://xmlns.sslmate.com/caa" id="support">
<!--
Copyright (C) 2016-2017 Opsmate, Inc.
This Source Code Form is subject to the terms of the Mozilla
Public License, v. 2.0. If a copy of the MPL was not distributed
with this file, You can obtain one at http://mozilla.org/MPL/2.0/.
This software is distributed WITHOUT A WARRANTY OF ANY KIND.
See the Mozilla Public License for details.
-->
<caa:title>Who Supports CAA Records?</caa:title>
<caa:head>
</caa:head>
<caa:body>
<div class="support">
<h2>Who Supports CAA?</h2>
<div class="overview">
<p>
If you want to publish a CAA record, your domain's DNS software (or provider) needs to support CAA.
This page tells you which DNS software and providers support CAA.
</p>
<p>
If you don't want to publish a CAA record, it shouldn't matter whether or not your
domain's DNS software supports CAA, since the DNS protocol provides a way to add
new record types in a backwards compatible way. Unfortunately, some DNS software
is broken and mishandles unsupported record types such as CAA. If your domain
uses such DNS software, you may have trouble getting certificates for your domain.
</p>
<p>
Please <a href="https://github.com/SSLMate/caa_helper/issues">open an issue</a> if you have
an addition to this page.
</p>
</div>
<div class="section">
<h3>Software</h3>
<support xmlns="http://xmlns.sslmate.com/caa">
<software>
<name>BIND</name>
<comments>Prior to version 9.9.6 use <xhtml:a href="https://tools.ietf.org/html/rfc3597">RFC 3597 syntax</xhtml:a></comments>
</software>
<software>
<name>NSD</name>
<comments>Prior to version 4.0.1 use <xhtml:a href="https://tools.ietf.org/html/rfc3597">RFC 3597 syntax</xhtml:a></comments>
</software>
<software>
<name>PowerDNS</name>
<version>4.0.0</version>
<comments>Versions 4.0.3 and below are <xhtml:a href="https://github.com/PowerDNS/pdns/issues/5546">buggy when DNSSEC is enabled</xhtml:a>.</comments>
</software>
<software>
<name>Knot DNS</name>
<version>2.2.0</version>
</software>
<software>
<name>Simple DNS Plus</name>
<version>6.0</version>
</software>
<software>
<name>Windows Server 2016</name>
<comments>Use <xhtml:a href="https://tools.ietf.org/html/rfc3597">RFC 3597 syntax</xhtml:a></comments>
</software>
<software>
<name>tinydns</name>
<comments>Use generic record syntax</comments>
</software>
<software>
<name>dnsmasq</name>
<comments>Use --dns-rr option with hex data</comments>
</software>
<software>
<name>ldns</name>
<version>1.6.17</version>
</software>
<software>
<name>OpenDNSSEC</name>
<comments>With ldns ≥1.6.17</comments>
</software>
</support>
</div>
<div class="section">
<h3>Providers</h3>
<support xmlns="http://xmlns.sslmate.com/caa">
<provider>
<name>Google Cloud DNS</name>
</provider>
<provider>
<name>Google Domains DNS</name>
</provider>
<provider>
<name>Route 53</name>
</provider>
<provider>
<name>DNSimple</name>
</provider>
<provider>
<name>DNS Made Easy</name>
</provider>
<provider>
<name>Constellix DNS</name>
</provider>
<provider>
<name>Cloudflare</name>
<comments>Cloudflare will add additional CAA records unless you disable Universal SSL.</comments>
</provider>
<provider>
<name>Dyn Managed DNS</name>
</provider>
<provider>
<name>ClouDNS</name>
</provider>
<provider>
<name>Afraid.org Free DNS</name>
</provider>
<provider>
<name>Neustar UltraDNS</name>
</provider>
<provider>
<name>Gandi</name>
</provider>
<provider>
<name>Domeneshop (Domainnameshop)</name>
</provider>
<provider>
<name>Hurricane Electric Free DNS</name>
</provider>
<provider>
<name>BuddyNS</name>
</provider>
<provider>
<name>NS1</name>
</provider>
<provider>
<name>Zilore</name>
</provider>
<provider>
<name>Nucleus NV</name>
</provider>
<provider>
<name>Mythic Beasts</name>
</provider>
<provider support="no">
<name>NameBright</name>
</provider>
<provider support="broken">
<name>ezyreg.com (Netregistry)</name>
<comments><xhtml:a href="https://community.letsencrypt.org/t/dns-problem-query-timed-out-looking-up-caa-using-netregistry/32817/28">Does not respond to CAA queries over UDP</xhtml:a></comments>
</provider>
<provider support="broken">
<name>LM Data</name>
<comments>Responds to CAA queries with a NOTIMP error</comments>
</provider>
<provider>
<name>core-networks.de</name>
</provider>
<provider>
<name>CloudXNS</name>
</provider>
<provider>
<name>Namecheap</name>
</provider>
<provider>
<name>Hetzner</name>
</provider>
<provider>
<name>hosting.de</name>
</provider>
<provider support="no">
<name>STRATO</name>
</provider>
<provider>
<name>http.net</name>
</provider>
<provider support="broken">
<name>Internap</name>
<comments>Responds to CAA queries with a SERVFAIL error</comments>
</provider>
<provider>
<name>Vultr</name>
</provider>
<provider>
<name>Digital Ocean</name>
</provider>
<provider>
<name>INWX</name>
</provider>
<provider>
<name>schokokeks.org</name>
</provider>
<provider>
<name>easyDNS</name>
</provider>
<provider>
<name>Linode</name>
</provider>
<provider>
<name>GratisDNS</name>
</provider>
<provider support="no">
<name>Rackspace Cloud DNS</name>
</provider>
<provider>
<name>Azure</name>
</provider>
<provider>
<name>Dreamhost</name>
</provider>
<provider>
<name>UD Media</name>
</provider>
<provider support="no">
<name>name.com</name>
</provider>
<provider>
<name>OVH</name>
</provider>
<provider>
<name>1&1</name>
</provider>
<provider support="no">
<name>Enom/Tucows</name>
</provider>
<provider>
<name>Netcup</name>
</provider>
<provider>
<name>34SP.com</name>
</provider>
<provider>
<name>iwantmyname</name>
<comments><xhtml:a href="https://help.iwantmyname.com/hc/en-gb/articles/360014762117-Do-you-support-CAA-records-">Requires opening a support ticket</xhtml:a></comments>
</provider>
<provider>
<name>GoDaddy</name>
</provider>
<provider support="no">
<name>SoftLayer</name>
</provider>
<provider>
<name>CloudfloorDNS</name>
</provider>
<provider>
<name>Hostwinds</name>
</provider>
<provider support="no">
<name>Hover</name>
</provider>
<provider support="no">
<name>123 Reg</name>
</provider>
<provider>
<name>Futureweb</name>
</provider>
<provider support="no">
<name>Lightsail DNS</name>
<comments><xhtml:a href="https://forums.aws.amazon.com/thread.jspa?threadID=284063">Relevant forum thread</xhtml:a></comments>
</provider>
<provider>
<name>Crazy Domains</name>
</provider>
<provider>
<name>Alibaba Cloud DNS</name>
</provider>
<provider>
<name>No-IP Dynamic DNS</name>
</provider>
<provider>
<name>UKFast</name>
</provider>
<provider>
<name>NameSilo</name>
</provider>
<provider>
<name>Metaname</name>
</provider>
<provider>
<name>Glauca HexDNS</name>
</provider>
<provider>
<name>DNSPod</name>
</provider>
<provider>
<name>WebHostOne</name>
</provider>
<provider>
<name>Opalstack</name>
</provider>
<provider>
<name>domaindiscount24</name>
</provider>
<provider>
<name>Pair Domains</name>
</provider>
<provider>
<name>deSEC</name>
</provider>
</support>
</div>
</div>
</caa:body>
</caa:page>