> -----Mensaje original-----
> De: chechu chechu [mailto:[EMAIL PROTECTED]
> Enviado el: miércoles, 15 de noviembre de 2006 18:12
> Para: Debian españa; Linuca
> Asunto: error bind
>
> hola estoy configurando bind9 para que sea el servidor dns de mi red...
> he conseguido hacer el cacheo(dns-cache)... y ahora estoy intentando que
> resuelve los nombres de mi red interna...pero me encuentro con este log
> en syslog y no me resuelve los nombres de la red interna...
>
> Nov 16 00:04:06 shogun named[11767]: listening on IPv4 interface eth1,
> 192.168.2.3#53
> Nov 16 00:04:06 shogun named[11767]: command channel listening on
> 127.0.0.1#953
> Nov 16 00:04:06 shogun named[11767]: zone 0.in-addr.arpa/IN: loaded
> serial 1
> Nov 16 00:04:06 shogun named[11767]: zone 127.in-addr.arpa/IN: loaded
> serial 1
> Nov 16 00:04:06 shogun named[11767]: zone 255.in-addr.arpa/IN: loaded
> serial 1
> Nov 16 00:04:06 shogun named[11767]:
> dns_master_load: /etc/bind/db.ironman.es:4: no current owner name
> Nov 16 00:04:06 shogun named[11767]: zone ironman.es/IN: loading master
> file /etc/bind/db.ironman.es: no owner
> Nov 16 00:04:06 shogun named[11767]: zone localhost/IN: loaded serial 1
> Nov 16 00:04:06 shogun named[11767]: running
>
> "no owner" y "no current owner name"...mis ficheros de conf son:
>
> named.conf:
>
> // If you are just adding zones, please do that
> in /etc/bind/named.conf.local
>
> #include "/etc/bind/named.conf.options";
>
> // prime the server with knowledge of the root servers
>
> view "internal" {
> match-clients { 192.168.2.1/24; }; // Modificad el match-client para
> vuestro caso, podeis dejar solo el 127.0.0.1 que es el localhost por
> defecto
>
> recursion yes;
>
> zone "." {
> type hint;
> file "/etc/bind/db.root";
> };
>
> // be authoritative for the localhost forward and reverse zones, and for
> // broadcast zones as per RFC 1912
>
> zone "localhost" {
> type master;
> file "/etc/bind/db.local";
> };
>
>
>
> zone "127.in-addr.arpa" {
> type master;
> file "/etc/bind/db.127";
> };
>
> zone "0.in-addr.arpa" {
> type master;
> file "/etc/bind/db.0";
> };
>
> zone "255.in-addr.arpa" {
> type master;
> file "/etc/bind/db.255";
> };
> zone "ironman.es" {
> type master;
> file "/etc/bind/db.ironman.es";
> };
>
> };
> // zone "com" { type delegation-only; };
> // zone "net" { type delegation-only; };
>
> // From the release notes:
> // Because many of our users are uncomfortable receiving undelegated
> answers
> // from root or top level domains, other than a few for whom that
> behaviour
> // has been trusted and expected for quite some length of time, we have
> now
> // introduced the "root-delegations-only" feature which applies
> delegation-only
> // logic to all top level domains, and to the root domain. An
> exception list
> // should be specified, including "MUSEUM" and "DE", and any other top
> level
> // domains from whom undelegated responses are expected and trusted.
> // root-delegation-only exclude { "DE"; "MUSEUM"; };
>
>
> //public address (external) view
> //view "external" {
> // match-clients { any; }; // Ponemos any ya que hemos declarado
> antes la zona interna. "any" se refiere al resto de ips que no hayan
> sido declaradas en algun
> // // match-clients anterior.
> // recursion no;
> //
> // zone "ironman.es" {
> // type master;
> // file "/etc/bind/db.ironman.es.ext";
> // };
>
> //};
>
>
>
>
> #include "/etc/bind/named.conf.local";
>
>
>
> y db.ironman.es:
>
> ;
> ; BIND data file for zone linuxsilo.net
> ;
> $TTL 604800
> $ORIGIN ironman.es
> @ IN SOA ironman.es. hostmaster.ironman.es. (
> 2005052401 ; Serial yyyy/mm/dd/id
> 10800 ; Refresh (3 hours)
> 7200 ; Retry (2 hours)
> 1296000 ; Expire (15 days)
> 172800 ) ; Negative Cache TTL (2 days)
> ;
> NS shogun.ironman.es ; Inet Address of name server
> ;
>
> shogun A 192.168.2.3
> shinobi A 192.168.2.6
> kase A 192.168.2.4
> daymio A 192.168.2.5
>
>
> gracias
>
>
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
Lo estas configurando mal te paso mi configuración
view "internal" {
match-clients { 172.16.48.0/25; };
recursion yes;
zone "." {
type hint;
file "/etc/bind/db.root";
};
zone "zonainterna.com" IN {
type master;
file "/etc/bind/zonainternald.db";
};
zone "48.16.172.in-addr.arpa" IN {
type master;
file "/etc/bind/zonainternalr.db";
};
};
Es decir las zonas de tu red interna deben estar dentro de la vista
Saludos
Luensacon
