next »

[request]

De curand mi-am instalat bind 9.5.0... & bind-utils...
Nu am reusit sa il fac sa fie caching-nameserver.
Am cautat pe net solutii, intre timp am aflat ca foloseste chroot in /var/lib/named.

Am gasit si un site care scotea in evidenta noile features ale lui http://www.howtoforge.com/forums/showthread.php?p=136549

un output de named status:

Code:

root@Samba360 ~ # /etc/init.d/named status
version: 9.5.0-P1 ()
number of zones: 17
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is ON
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running

[gheorghe]

Pai cred ca in configuratia default e caching. Trebuie doar sa-i setezi nameserverele ISP-ului tau prin configuratie forwarders bla bla, daca nu, face requesturile direct la root nameservers.

[Emil CHERICHEȘ]

si mai verifica in named.conf cui ii raspunde la cererile recursive
allow-recursion  {192.168.0.0/24; 127.0.0.1;};

[request]

Problema rezolvata, acum merge.

Ce am facut ?
Am modificat urmatoarele linii:

Code:

//    forwarders { first_public_nameserver_ip; second_public_nameserver_ip; }; Copiat si modificat
    forwarders { 89.33.233.1; };
........
//    allow-query { trusted_networks; }; Copiat si modificat.
    allow-query { 192.168.5.0/24; 127.0.0.1; };
//    allow-recursion { trusted_networks; }; Copiat si modificat.
    allow-recursion { 192.168.5.0/24; 127.0.0.1; };

Apoi am restartat serverul "/etc/init.d/named restart"