diff --git a/.gitbook/assets/routes_list.png b/.gitbook/assets/routes_list.png
new file mode 100644
index 0000000..8a78bac
Binary files /dev/null and b/.gitbook/assets/routes_list.png differ
diff --git a/.gitbook/assets/routes_listenflow.png b/.gitbook/assets/routes_listenflow.png
new file mode 100644
index 0000000..c068ed5
Binary files /dev/null and b/.gitbook/assets/routes_listenflow.png differ
diff --git a/.gitbook/assets/the-matrix-morpheus-dns.png b/.gitbook/assets/the-matrix-morpheus-dns.png
new file mode 100644
index 0000000..7df56c8
Binary files /dev/null and b/.gitbook/assets/the-matrix-morpheus-dns.png differ
diff --git a/index/configurations/domains/discussions-subdomains.md b/index/configurations/domains/discussions-subdomains.md
index fee2505..73c85d6 100644
--- a/index/configurations/domains/discussions-subdomains.md
+++ b/index/configurations/domains/discussions-subdomains.md
@@ -22,3 +22,6 @@ I could now create a subdomain under a Nextcloud is running. First of all, it wo
It's one thing when we present something important, something for the public. I would totally understand Google along the way. But we can't do without it in the future either.
+
+
+
diff --git a/index/configurations/domains/own-dns-server.md b/index/configurations/domains/own-dns-server.md
index a4fb5d2..87a1752 100644
--- a/index/configurations/domains/own-dns-server.md
+++ b/index/configurations/domains/own-dns-server.md
@@ -32,7 +32,7 @@ In the diagram you can see how the flow works:
From now on we can manage all sub domains and example.com ourselves with our own records.
{% endhint %}
-
+
## Practice
diff --git a/index/configurations/routes.md b/index/configurations/routes.md
index ae1c418..14db4ef 100644
--- a/index/configurations/routes.md
+++ b/index/configurations/routes.md
@@ -1,2 +1,29 @@
+---
+description: Setting a route from the listen to the target.
+---
+
# Routes
+A route is a path from the input ([Listen](listen.md)) to the destination. The destination can be of different types, stream, HTTP/HTTPS, SSH, use.
+
+With the help of the [graphic from Listen](listen.md#listen-flow) I would like to show the area controlled by the route again:
+
+
Listen and Routes
+
+## Routes List
+
+
+
+1. The new creation and loading of the configuration of the nginx (all Listen, Routes, etc.) can be triggered again manually at any time.
+
+{% hint style="info" %}
+Existing connections are kept as if running the command: nginx -s reload
+{% endhint %}
+
+2. The first thing to see in the Routes list are the default routes. If no route is specified, the default routes always apply.
+
+{% hint style="info" %}
+The default routes cannot be edited or deleted.
+{% endhint %}
+
+3. Each domain entered in [Domains](domains/) is displayed under Routes. One or more routes from one or more [Listen](listen.md) to a destination can now be entered.
