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

Light editing knot_authoritative_dns.md #2124

Merged
merged 1 commit into from
Jun 17, 2024
Merged

Light editing knot_authoritative_dns.md #2124

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
17 changes: 8 additions & 9 deletions docs/guides/dns/knot_authoritative_dns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,12 @@
---
title: Knot Authoritative DNS
author: Neel Chauhan
contributors:
contributors: Steven Spencer
tested_with: 9.4
tags:
- dns
---

# Knot Authoritative DNS

An alternative to BIND, [Knot DNS](https://www.knot-dns.cz/) is a modern authoritative-only DNS server maintained by the Czech domain registry [CZ.NIC](https://www.nic.cz/).

## Prerequisites and assumptions
Expand Down Expand Up @@ -45,7 +43,7 @@ mv /etc/knot/knot.conf /etc/knot/knot.conf.orig

That will help in the future if the introduction of errors into the configuration file occurs. It is *always* a good idea to make a backup copy before making changes.

Edit the *knot.conf* file. The author is using *vi*, but you can substitute your favorite command line editor:
Edit the *knot.conf* file. The author uses *vi*, but you can substitute your favorite command line editor:

```bash
vi /etc/knot/knot.conf
Expand All @@ -70,7 +68,7 @@ log:

Replace `example.com` with the domain name you are running a nameserver for.

Next, create the zone files itself:
Next, create the zone files:

```bash
mkdir /var/lib/knot/zones
Expand Down Expand Up @@ -105,15 +103,15 @@ Save your changes.

## Enabling Knot

Now you will allow DNS in `firewall-cmd` and enable Knot DNS:
Next, allow DNS ports in `firewalld` and enable Knot DNS:

```bash
firewall-cmd --add-service=dns --zone=public
firewall-cmd --runtime-to-permanent
systemctl enable --now knot
```

You can check DNS resolution with the `host` command:
Check DNS resolution with the `host` command:

```bash
% host example.com 172.20.0.100
Expand All @@ -126,8 +124,9 @@ example.com has address 172.20.0.100
example.com mail is handled by 10 mail.another.com.
%
```

## Conclusion

While most people use third-party services for DNS there are scenarios where self-hosting DNS is desired. For instance, telecom, hosting and social media companies host a large number of DNS entries where hosted services are undesirable.
While most people use third-party services for DNS, there are scenarios where self-hosting DNS is desired. For instance, telecom, hosting, and social media companies, host a large number of DNS entries where hosted services are undesirable.

Knot is one of many open source tools which make hosting DNS possible, so congratulations, you got your very own DNS server! Cheers!
Knot is one of many open source tools which make hosting DNS possible. Congratulations, you have your very own DNS server! Cheers!
Loading