Servizo de BIND
BIND execútase como un servizo, polo que será un proceso que está correndo de fondo.
Estado de BIND
Para consultar o estado do servizo de BIND, debemos executar o seguinte comando:
$ systemctl status named
Saída do comando
$ systemctl status named
● named.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2021-01-17 21:41:47 CET; 32min ago
Docs: man:named(8)
Main PID: 7797 (named)
Tasks: 8 (limit: 4615)
Memory: 29.9M
CGroup: /system.slice/named.service
└─7797 /usr/sbin/named -f -u bind
ene 17 21:41:48 pc named[7797]: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
ene 17 21:41:48 pc named[7797]: network unreachable resolving './NS/IN': 2001:dc3::35#53
ene 17 21:41:48 pc named[7797]: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
ene 17 21:41:48 pc named[7797]: network unreachable resolving './NS/IN': 2001:500:a8::e#53
ene 17 21:41:48 pc named[7797]: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
ene 17 21:41:48 pc named[7797]: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
ene 17 21:41:48 pc named[7797]: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
ene 17 21:41:48 pc named[7797]: network unreachable resolving './NS/IN': 2001:500:1::53#53
ene 17 21:41:48 pc named[7797]: managed-keys-zone: Initializing automatic trust anchor management for zone '.'; DNSKEY ID 20326 is now trusted, waiving the normal 30-day wai>
ene 17 21:41:48 pc named[7797]: resolver priming query complete
Podemos empregar ← ↑ → ↓ para desprazarnos pola información mostrada e Q para saír.
A propiedade Active poderá ter os seguintes valores:
active (running): BIND está executándose correctamente.inactive (dead): BIND non se está execuantdo.failed: BIND non se está execuantdo porque se producíu un error.
Como calquera servizo, podemos arrancalo, paralo ou reinicialo. Os comandos, no caso de executarse correctamente, non mostran ningunha saída.
Arrancar BIND
$ sudo systemctl start named
Parar BIND
$ sudo systemctl stop named
Reiniciar BIND
$ sudo systemctl restart named
O comando de reinicio de BIND é equivalente a executar o seguinte:
$ sudo systemctl stop named
$ sudo systemctl start named
Se queremos comprobar que calquera das operacións anteriores se levou a cabo correctamente (arranque, parada ou reinicio), podemos executar o comando de comprobación do estado de BIND despois de executar un deles. Por exemplo:
$ sudo systemctl stop named
$ systemctl status named
Saída dos comandos
$ sudo systemctl stop named
$ systemctl status named
● named.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Sun 2021-01-17 22:20:01 CET; 2s ago
Docs: man:named(8)
Process: 7797 ExecStart=/usr/sbin/named -f $OPTIONS (code=exited, status=0/SUCCESS)
Process: 8796 ExecStop=/usr/sbin/rndc stop (code=exited, status=0/SUCCESS)
Main PID: 7797 (code=exited, status=0/SUCCESS)
ene 17 22:20:01 pc named[7797]: no longer listening on 127.0.0.1#53
ene 17 22:20:01 pc named[7797]: no longer listening on 10.0.1.134#53
ene 17 22:20:01 pc named[7797]: no longer listening on ::1#53
ene 17 22:20:01 pc named[7797]: no longer listening on fe80::e3d:2993:25dc:f5ac%2#53
ene 17 22:20:01 pc named[7797]: shutting down: flushing changes
ene 17 22:20:01 pc named[7797]: stopping command channel on 127.0.0.1#953
ene 17 22:20:01 pc named[7797]: stopping command channel on ::1#953
ene 17 22:20:01 pc named[7797]: exiting
ene 17 22:20:01 pc systemd[1]: named.service: Succeeded.
ene 17 22:20:01 pc systemd[1]: Stopped BIND Domain Name Server.
Pulsamos Q para saír do comando.
O servizo de BIND recibe o nome de named, pero tamén se pode facer referencia el mediante bind9. En todos os comandos relacionados co servizo, pódese empregar indistintamente bind9 e named. Polo tanto, estes comandos tamén funcionarán:
$ systemctl status bind9
$ sudo systemctl stop bind9
$ sudo systemctl start bind9
$ sudo systemctl restart bind9