mirrors/hello-dns
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

$ORIGIN needs dot.

Browse Source 
Your PowerDNS ancestry shows: missing dots. ;-) 
Without the trailing dot, `named-checkzone` says:

```
SOA record not at top of zone (ietf.org.ietf.org)
```
This commit is contained in:
JP Mens 2018-03-29 15:22:19 +02:00 committed by GitHub
parent 2f90d2850d
commit cf2b41c1bd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -205,7 +205,7 @@ trailing 0 which denotes this is the end.
This format is unusual, but has several highly attractive properties. For This format is unusual, but has several highly attractive properties. For
example, it is binary safe and it needs no escaping. When writing DNS example, it is binary safe and it needs no escaping. When writing DNS
software, it may be tempting to pass DNS names around as "ASCII". This then software, it may be tempting to pass DNS names around as "ASCII". This then
leads to escaping and unescaping code in lots of places. It is highly leads to escaping an unescaping code in lots of places. It is highly
recommended to use the native DNS encoding to store DNS names. This will recommended to use the native DNS encoding to store DNS names. This will
save a lot of pain when processing DNS names with spaces or dots in them. save a lot of pain when processing DNS names with spaces or dots in them.
@ -500,7 +500,7 @@ of the zone, at which point there is also a SOA record. So a typical zone
will start like this: will start like this:
``` ```
$ORIGIN ietf.org $ORIGIN ietf.org.
@ IN SOA ns1 admin 2018032802 1800 900 604800 86400 @ IN SOA ns1 admin 2018032802 1800 900 604800 86400
IN NS ns1 IN NS ns1
IN NS ns2 IN NS ns2
@ -519,7 +519,7 @@ Note however that above we learned that the parent zone, 'org' also needs to
list the nameservers for example.org, and it does: list the nameservers for example.org, and it does:
``` ```
$ORIGIN org $ORIGIN org.
... ...
ietf IN NS ns1.ietf ietf IN NS ns1.ietf
ietf IN NS ns2.ietf ietf IN NS ns2.ietf
@ -538,7 +538,7 @@ To solve this problem, the parent zone can provide a free chicken. In the
org zone, we would actually find: org zone, we would actually find:
``` ```
$ORIGIN org $ORIGIN org.
... ...
ietf IN NS ns1.ietf ietf IN NS ns1.ietf
ietf IN NS ns2.ietf ietf IN NS ns2.ietf
@ -574,7 +574,7 @@ www.ietf.org is sent to cloudflare. This simultaneously means that what
everyone wants is impossible: everyone wants is impossible:
``` ```
$origin ietf.org $ORIGIN ietf.org
@ IN CNAME this.does.not.work.int. @ IN CNAME this.does.not.work.int.
``` ```
@ -593,7 +593,7 @@ can loop.
Wildcards allow for the following: Wildcards allow for the following:
``` ```
$origin ietf.org $ORIGIN ietf.org.
* IN A 192.0.2.1 * IN A 192.0.2.1
IN AAAA 2001:db8:85a3::8a2e:0370:7334 IN AAAA 2001:db8:85a3::8a2e:0370:7334
smtp IN A 192.0.2.222 smtp IN A 192.0.2.222