> For the complete documentation index, see [llms.txt](https://utm-1.gitbook.io/utm-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://utm-1.gitbook.io/utm-docs/dokumentaciya/utm-it/programmnoe-obespechenie/linux-servera/sistemnoe-po/bind-dns1-master-rezhim.md). # BIND (DNS1 - master режим) ## Установка **Установка BIND в Ubuntu:** ```bash sudo apt update sudo apt install bind9 sudo systemctl enable bind9 sudo systemctl start bind9 ``` **Проверка:** ```bash sudo systemctl status bind9 ``` ## Настройка ### Настройка зон в *named.conf.local* файле *named.conf.local* определяем локальные зоны. ```bash sudo nano /etc/bind/named.conf.local ```
Содержание файла /etc/bind/named.conf.local [Ссылка на файл в GitHub](https://github.com/utenkov-maxim/all-configs/blob/main/Servers/utm-server3/etc/bind/named.conf.local) ``` // // Do any local configuration here // // sudo nano /etc/bind/named.conf.local // sudo systemctl restart bind9 // Consider adding the 1918 zones here, if they are not used in your // organization //include "/etc/bind/zones.rfc1918"; # Forward zone zone "utmhome.ru" { type master; file "/etc/bind/zones/db.utmhome.ru"; allow-transfer { 192.168.1.4; }; also-notify { 192.168.1.4; }; }; # Reverse zone 192.168.1.0/24 - сервера, сетевое оборудование zone "1.168.192.in-addr.arpa" { type master; file "/etc/bind/zones/db.1.168.192"; allow-transfer { 192.168.1.4; }; also-notify { 192.168.1.4; }; }; # Reverse zone 192.168.2.0/24 - рабочие станции zone "2.168.192.in-addr.arpa" { type master; file "/etc/bind/zones/db.2.168.192"; allow-transfer { 192.168.1.4; }; also-notify { 192.168.1.4; }; }; # Reverse zone 192.168.3.0/24 - виртуалки на сервере 192.168.1.3 zone "3.168.192.in-addr.arpa" { type master; file "/etc/bind/zones/db.3.168.192"; allow-transfer { 192.168.1.4; }; also-notify { 192.168.1.4; }; }; # Reverse zone 192.168.4.0/24 - виртуалки на сервере 192.168.1.4 zone "4.168.192.in-addr.arpa" { type master; file "/etc/bind/zones/db.4.168.192"; allow-transfer { 192.168.1.4; }; also-notify { 192.168.1.4; }; }; # Reverse zone 192.168.5.0/24 - виртуалки на сервере 192.168.1.5 zone "5.168.192.in-addr.arpa" { type master; file "/etc/bind/zones/db.5.168.192"; allow-transfer { 192.168.1.4; }; also-notify { 192.168.1.4; }; }; # Reverse zone 192.168.10.0/24 - DHCP zone "10.168.192.in-addr.arpa" { type master; file "/etc/bind/zones/db.10.168.192"; allow-transfer { 192.168.1.4; }; also-notify { 192.168.1.4; }; }; # Reverse zone 192.168.20.0/24 - перефирия zone "20.168.192.in-addr.arpa" { type master; file "/etc/bind/zones/db.20.168.192"; allow-transfer { 192.168.1.4; }; also-notify { 192.168.1.4; }; }; ```
### Создание файлов прямой и обратной зоны #### Создайте каталог Zones ```bash sudo mkdir /etc/bind/zones ``` #### Создание файла прямой зоны ```bash sudo nano /etc/bind/zones/db.utmhome.ru ```
Содержание файла /etc/bind/zones/db.utmhome.ru [Ссылка на файл в GitHub](https://github.com/utenkov-maxim/all-configs/blob/main/Servers/utm-server3/etc/bind/zones/db.utmhome.ru) ``` ; ; BIND data file for local loopback interface ; ; sudo nano /etc/bind/zones/db.utmhome.ru ; $TTL 604800 @ IN SOA ns1.utmhome.ru. admin.utmhome.ru. ( 2025111801 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS ns1.utmhome.ru. ns1 IN A 192.168.1.3 ; ; ######################################### ; 192.168.1.0/24 ; ######################################### ; utm-router1 IN A 192.168.1.1 utm-server3 IN A 192.168.1.3 utm-server4 IN A 192.168.1.4 utm-server5 IN A 192.168.1.5 utm-desktop6 IN A 192.168.1.6 ; utm-router50 IN A 192.168.1.50 ; utm-k8s-haproxy IN A 192.168.1.100 ; ; ; ######################################### ; 192.168.2.0/24 ; ######################################### ; WORK-PC IN A 192.168.2.1 HOME-PC IN A 192.168.2.2 GPBNB28791 IN A 192.168.2.3 MAXIM-PC IN A 192.168.2.4 NOTE-PC IN A 192.168.2.5 ANDREY-PC IN A 192.168.2.6 ; ; ; ######################################### ; 192.168.3.0/24 ; ######################################### ; utm-proxy3-0 IN A 192.168.3.0 utm-k8s-master3-1 IN A 192.168.3.1 utm-k8s-node3-5 IN A 192.168.3.5 utm-k8s-node3-6 IN A 192.168.3.6 ; utm-test3-11 IN A 192.168.3.11 ; ; ; ######################################### ; 192.168.4.0/24 ; ######################################### ; utm-k8s-master4-1 IN A 192.168.4.1 utm-k8s-node4-5 IN A 192.168.4.5 utm-k8s-node4-6 IN A 192.168.4.6 ; ; utm-db4-9 IN A 192.168.4.9 utm-minecraft4-10 IN A 192.168.4.10 ; utm-test4-31 IN A 192.168.4.31 ; ; ; ######################################### ; 192.168.5.0/24 ; ######################################### ; utm-k8s-master5-1 IN A 192.168.5.1 utm-k8s-node5-5 IN A 192.168.5.5 utm-k8s-node5-6 IN A 192.168.5.6 ; ; ; ######################################### ; 192.168.20.0/24 ; ######################################### ; utm-printer20-1 IN A 192.168.20.1 utm-tvbox20-11 IN A 192.168.20.11 utm-tvbox20-12 IN A 192.168.20.12 utm-tv20-21 IN A 192.168.20.21 utm-tv20-22 IN A 192.168.20.22 utm-lamp20-31 IN A 192.168.20.31 ; ; ; ######################################### ; TEST CNAME ; ######################################### ; www IN CNAME HOME-PC Andrey IN CNAME HOME-PC Maxim IN CNAME WORK-PC ```
#### Создание файлов обратной зоны **/etc/bind/zones/db.1.168.192** ```bash sudo nano /etc/bind/zones/db.1.168.192 ```
Содержание файла /etc/bind/zones/db.1.168.192 [Ссылка на файл в GitHub](https://github.com/utenkov-maxim/all-configs/blob/main/Servers/utm-server3/etc/bind/zones/db.1.168.192) ``` ; ; BIND reverse data file for local loopback interface ; ; sudo nano /etc/bind/zones/db.1.168.192 ; $TTL 604800 @ IN SOA ns1.utmhome.ru. admin.utmhome.ru. ( 2025111801 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS ns1.utmhome.ru. ; 3 IN PTR ns1.utmhome.ru. ; 1 IN PTR utm-router1.utmhome.ru. 3 IN PTR utm-server3.utmhome.ru. 4 IN PTR utm-server4.utmhome.ru. 5 IN PTR utm-server5.utmhome.ru. 6 IN PTR utm-desktop6.utmhome.ru. 50 IN PTR utm-router50.utmhome.ru. 100 IN PTR utm-k8s-haproxy.utmhome.ru. ```
**/etc/bind/zones/db.2.168.192** ```bash sudo nano /etc/bind/zones/db.2.168.192 ```
Содержание файла /etc/bind/zones/db.2.168.192 [Ссылка на файл в GitHub](https://github.com/utenkov-maxim/all-configs/blob/main/Servers/utm-server3/etc/bind/zones/db.2.168.192) ``` ; ; BIND reverse data file for local loopback interface ; ; sudo nano /etc/bind/zones/db.2.168.192 ; $TTL 604800 @ IN SOA ns1.utmhome.ru. admin.utmhome.ru. ( 2025111801 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS ns1.utmhome.ru. ; 3 IN PTR ns1.utmhome.ru. ; 1 IN PTR WORK-PC.utmhome.ru. 2 IN PTR HOME-PC.utmhome.ru. 3 IN PTR GPBNB28791.utmhome.ru. 4 IN PTR MAXIM-PC.utmhome.ru. 5 IN PTR NOTE-PC.utmhome.ru. 6 IN PTR ANDREY-PC.utmhome.ru. ```
**/etc/bind/zones/db.3.168.192** ```bash sudo nano /etc/bind/zones/db.3.168.192 ```
Содержание файла /etc/bind/zones/db.3.168.192 [Ссылка на файл в GitHub](https://github.com/utenkov-maxim/all-configs/blob/main/Servers/utm-server3/etc/bind/zones/db.3.168.192) ``` ; ; BIND reverse data file for local loopback interface ; ; sudo nano /etc/bind/zones/db.3.168.192 ; $TTL 604800 @ IN SOA ns1.utmhome.ru. admin.utmhome.ru. ( 2025111801 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS ns1.utmhome.ru. ; 3 IN PTR ns1.utmhome.ru. ; 0 IN PTR utm-proxy3-0.utmhome.ru. 1 IN PTR utm-k8s-master3-1.utmhome.ru. 5 IN PTR utm-k8s-node3-5.utmhome.ru. 6 IN PTR utm-k8s-node3-6.utmhome.ru. 11 IN PTR utm-test3-11.utmhome.ru. ```
**/etc/bind/zones/db.4.168.192** ```bash sudo nano /etc/bind/zones/db.4.168.192 ```
Содержание файла /etc/bind/zones/db.4.168.192 [Ссылка на файл в GitHub](https://github.com/utenkov-maxim/all-configs/blob/main/Servers/utm-server3/etc/bind/zones/db.4.168.192) ``` ; ; BIND reverse data file for local loopback interface ; ; sudo nano /etc/bind/zones/db.4.168.192 ; $TTL 604800 @ IN SOA ns1.utmhome.ru. admin.utmhome.ru. ( 2025111801 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS ns1.utmhome.ru. ; 3 IN PTR ns1.utmhome.ru. ; 1 IN PTR utm-k8s-master4-1.utmhome.ru. 5 IN PTR utm-k8s-node4-5.utmhome.ru. 6 IN PTR utm-k8s-node4-6.utmhome.ru. 9 IN PTR utm-db4-9.utmhome.ru. 10 IN PTR utm-minecraft4-10.utmhome.ru. 31 IN PTR utm-test4-31.utmhome.ru. ```
**/etc/bind/zones/db.5.168.192** ```bash sudo nano /etc/bind/zones/db.5.168.192 ```
Содержание файла /etc/bind/zones/db.5.168.192 [Ссылка на файл в GitHub](https://github.com/utenkov-maxim/all-configs/blob/main/Servers/utm-server3/etc/bind/zones/db.5.168.192) ``` ; ; BIND reverse data file for local loopback interface ; ; sudo nano /etc/bind/zones/db.5.168.192 ; $TTL 604800 @ IN SOA ns1.utmhome.ru. admin.utmhome.ru. ( 2025111801 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS ns1.utmhome.ru. ; 3 IN PTR ns1.utmhome.ru. ; 1 IN PTR utm-k8s-master5-1.utmhome.ru. 5 IN PTR utm-k8s-node5-5.utmhome.ru. 6 IN PTR utm-k8s-node5-6.utmhome.ru. ```
**/etc/bind/zones/db.10.168.192** ```bash sudo nano /etc/bind/zones/db.10.168.192 ```
Содержание файла /etc/bind/zones/db.10.168.192 [Ссылка на файл в GitHub](https://github.com/utenkov-maxim/all-configs/blob/main/Servers/utm-server3/etc/bind/zones/db.10.168.192) ``` ; ; BIND reverse data file for local loopback interface ; ; sudo nano /etc/bind/zones/db.10.168.192 ; $TTL 604800 @ IN SOA ns1.utmhome.ru. admin.utmhome.ru. ( 2025111801 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS ns1.utmhome.ru. ; 3 IN PTR ns1.utmhome.ru. ; ```
**/etc/bind/zones/db.20.168.192** ```bash sudo nano /etc/bind/zones/db.20.168.192 ```
Содержание файла /etc/bind/zones/db.20.168.192 [Ссылка на файл в GitHub](https://github.com/utenkov-maxim/all-configs/blob/main/Servers/utm-server3/etc/bind/zones/db.20.168.192) ``` ; ; BIND reverse data file for local loopback interface ; ; sudo nano /etc/bind/zones/db.20.168.192 ; $TTL 604800 @ IN SOA ns1.utmhome.ru. admin.utmhome.ru. ( 2025111801 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS ns1.utmhome.ru. ; 3 IN PTR ns1.utmhome.ru. ; 1 IN PTR utm-printer20-1.utmhome.ru. 11 IN PTR utm-tvbox20-11.utmhome.ru. 12 IN PTR utm-tvbox20-12.utmhome.ru. 21 IN PTR utm-tv20-21.utmhome.ru. 22 IN PTR utm-tv20-22.utmhome.ru. 31 IN PTR utm-lamp20-31.utmhome.ru. ```
### Проверка конфигурации и перезапуск BIND9 Проверка конфигураций: ```bash sudo named-checkzone utmhome.ru /etc/bind/zones/db.utmhome.ru sudo named-checkzone 1.168.192.in-addr.arpa /etc/bind/zones/db.1.168.192 sudo named-checkzone 2.168.192.in-addr.arpa /etc/bind/zones/db.2.168.192 sudo named-checkzone 3.168.192.in-addr.arpa /etc/bind/zones/db.3.168.192 sudo named-checkzone 4.168.192.in-addr.arpa /etc/bind/zones/db.4.168.192 sudo named-checkzone 5.168.192.in-addr.arpa /etc/bind/zones/db.5.168.192 sudo named-checkzone 10.168.192.in-addr.arpa /etc/bind/zones/db.10.168.192 sudo named-checkzone 10.168.192.in-addr.arpa /etc/bind/zones/db.20.168.192 ``` Если всё в порядке, мы увидим сообщение *Ok* **Перезапуск службы BIND9**: ```bash sudo systemctl restart bind9 ``` **Проверка работы BIND9:** ```bash dig @192.168.1.3 utmhome.ru ``` ```bash resolvectl status ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://utm-1.gitbook.io/utm-docs/dokumentaciya/utm-it/programmnoe-obespechenie/linux-servera/sistemnoe-po/bind-dns1-master-rezhim.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.