Creazione di una zona diretta e di una inversa con Bind9
Jump to navigation
Jump to search
- Installare bind normalmente
- Creazione del file della zona diretta per il dominio example.priv:
cat | sudo tee /etc/bind/example.priv.db <<'EOFile'
;
; BIND data file for example.priv
;
$TTL 604800
@ IN SOA example.priv. hostmaster.example.priv. (
2007011501 ; Serial
7200 ; Refresh
120 ; Retry
2419200 ; Expire
604800) ; Default TTL
;
@ IN NS myserver.example.priv.
myserver.example.priv. IN A 192.168.1.1
proxy IN CNAME myserver
EOFile
- Controllo della sintassi:
cd /etc/bind named-checkzone example.priv example.priv.db zone example.priv/IN: loaded serial 2007011501 OK
- Creazione della zona inversa
cat | sudo tee /etc/bind/1.168.192.in-addr.arpa.db <<'EOFile'
$TTL 1d ;
$ORIGIN 1.168.192.in-addr.arpa.
@ IN SOA myserver.example.priv. hostmaster.example.priv. (
2007011501
7200
120
2419200
604800
)
@ IN NS myserver.example.priv.
1 IN PTR myserver.example.priv.
EOFile
- Controllo della sintassi:
cd /etc/bind named-checkzone 1.168.192.in-addr.arpa 1.168.192.in-addr.arpa.db zone 1.168.192.in-addr.arpa/IN: loaded serial 2007011501 OK
- Inserimento delle zone nella configurazione di bind:
cat | sudo tee -a /etc/bind/named.conf.local > /dev/null <<EOFile
zone "example.priv" {
type master;
file "/etc/bind/example.priv.db";
};
zone "1.168.192.in-addr.arpa" {
type master;
file "/etc/bind/1.168.192.in-addr.arpa.db";
};
EOFile
- Controllarne la sintassi
cd /etc/bind sudo named-checkconf -z named.conf.local
- Testare il tutto:
sudo invoke-rc.d bind9 stop sudo invoke-rc.d bind9 start
host myserver myserver.example.priv has address 192.168.1.1 host proxy proxy.example.priv is an alias for myserver.example.priv. myserver.example.priv has address 192.168.1.1 host 192.168.1.1 1.1.168.192.in-addr.arpa domain name pointer myserver.example.priv