Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid blank lines in zone files #47

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Avoid blank lines in zone files #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions basic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -468,13 +468,13 @@ will start like this:
```
$ORIGIN ietf.org.
@ IN SOA ns1 admin 2018032802 1800 900 604800 86400
IN NS ns1
IN NS ns2
@ IN NS ns1
@ IN NS ns2
```

Note how in this zone file example names not ending on a '.' are interpreted
as being part of ietf.org. The '@' is a way to specify the name of the
apex. Lines two and three omit a name, so they default to '@' too.
apex, so lines two and three indicate that the apex of this zone has two NS records.

This zone lists ns1.ietf.org and ns2.ietf.org as its nameservers.
Being part of the zone, this data is *authoritative*. Any queries sent to
Expand Down Expand Up @@ -562,7 +562,7 @@ Wildcards allow for the following:
```
$ORIGIN ietf.org.
* 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
```

Expand Down