1
0
mirror of https://github.com/StackExchange/dnscontrol.git synced 2024-05-11 05:55:12 +00:00
Tom Limoncelli 533eabedf5 Update docs for the "plan a" change (#1499)
* Update docs
2022-05-08 14:41:33 -04:00

56 lines
1.4 KiB
Markdown

---
name: DNS-over-HTTPS
title: DNS-over-HTTPS Provider
layout: default
jsId: DNSOVERHTTPS
---
# DNS-over-HTTPS Provider
This is a read-only/monitoring "registrar". It does a DNS NS lookup to confirm the nameserver servers are correct. This "registrar" is unable to update/correct the NS servers but will alert you if they are incorrect. A common use of this provider is when the domain is with a registrar that does not have an API.
## Configuration
To use this provider, add an entry to `creds.json` with `TYPE` set to `DNSOVERHTTPS`.
```json
{
"dohdefault": {
"TYPE": "DNSOVERHTTPS"
}
}
```
The DNS-over-HTTPS provider defaults to using Google Public DNS however you may configure an alternative RFC 8484 DoH provider using the `host` parameter.
Example:
```json
{
"dohcloudflare": {
"TYPE": "DNSOVERHTTPS",
"host": "cloudflare-dns.com"
}
}
```
Some common DoH providers are:
* `cloudflare-dns.com` ([Cloudflare](https://developers.cloudflare.com/1.1.1.1/dns-over-https))
* `9.9.9.9` ([Quad9](https://www.quad9.net/about/))
* `dns.google` ([Google Public DNS](https://developers.google.com/speed/public-dns/docs/doh))
## Metadata
This provider does not recognize any special metadata fields unique to DOH.
## Usage
An example `dnsconfig.js` configuration:
```js
var REG_MONITOR = NewRegistrar("dohcloudflare");
D("example.com", REG_MONITOR,
NAMESERVER("ns1.example.com."),
NAMESERVER("ns2.example.com."),
);
```