Forum Linux.pl

System => Sieć => Wątek zaczęty przez: w 2008-04-05, 12:16:05

Tytuł: problem z BIND
Wiadomość wysłana przez: w 2008-04-05, 12:16:05
witam,
może ktoś na tym forum będzie znał odp na mój problem:

chciałem skonfigurować named i uruchomić ale nie działa, oto co pokazują logi:


Apr  5 12:57:32 bsd named[1085]: starting BIND 9.4.2
Apr  5 12:57:32 bsd named[1085]: command channel listening on 127.0.0.1#953
Apr  5 12:57:32 bsd named[1085]: command channel listening on ::1#953
Apr  5 12:57:32 bsd named[1085]: db.127.0.0:2: ignoring out-of-zone data (0.0.127.in-addr.arpa)
Apr  5 12:57:32 bsd named[1085]: db.127.0.0:9: ignoring out-of-zone data (0.0.127.in-addr.arpa)
Apr  5 12:57:32 bsd named[1085]: db.127.0.0:10: ignoring out-of-zone data (1.0.0.127.in-addr.arpa)
Apr  5 12:57:32 bsd named[1085]: zone 0.0.127.in-addr.apra/IN: has 0 SOA records
Apr  5 12:57:32 bsd named[1085]: zone 0.0.127.in-addr.apra/IN: has no NS records
Apr  5 12:57:32 bsd named[1085]: db.192.168.0:2: ignoring out-of-zone data (0.168.192.in-addr.arpa)
Apr  5 12:57:32 bsd named[1085]: db.192.168.0:9: ignoring out-of-zone data (0.168.192.in-addr.arpa)
Apr  5 12:57:32 bsd named[1085]: db.192.168.0:12: ignoring out-of-zone data (1.0.168.192.in-addr.arpa)
Apr  5 12:57:32 bsd named[1085]: db.192.168.0:13: ignoring out-of-zone data (55.0.168.192.in-addr.arpa)
Apr  5 12:57:32 bsd named[1085]: zone 0.168.192.in-addr.apra/IN: has 0 SOA records
Apr  5 12:57:32 bsd named[1085]: zone 0.168.192.in-addr.apra/IN: has no NS records
Apr  5 12:57:32 bsd named[1085]: running
Apr  5 13:00:13 bsd named[1085]: checkhints: L.ROOT-SERVERS.NET/A (199.7.83.42) missing from hints
Apr  5 13:00:13 bsd named[1085]: checkhints: L.ROOT-SERVERS.NET/A (198.32.64.12) extra record in hints



dodam, że jak dam polecenie :
host  bsd.company.com to działa
jak dam
host 192.168.0.1 to nie działa, a błąd jest taki:
HOST 1.0.168.192.in-addr.arpa not found : 3(NXDOMAIN)


oto moje pliki conf

named.conf:


options {
directory "/var/named/etc/namedb";   //katalog w którym jest named
auth-nxdomain yes;
listen-on {192.168.0.1;};
pid-file "named.pid";
};


zone "." IN {
type hint;
file "named.root";
};



zone "localhost" IN {
type master;
file "db.localhost";
};


zone "0.0.127.in-addr.apra" IN {
type master;
file "db.127.0.0";
};



zone "company.com" IN {
type master;
file "db.company.com";
};



zone "0.168.192.in-addr.apra" IN {
type master;
file "db.192.168.0";
};


----------------------------------------------------------------

db.192.168.0

$ttl 3h;
0.168.192.in-addr.arpa.   IN   SOA   bsd.faunet.pl.   root.faunet.pl.(
02030202
3H
15M
1W
1H);

0.168.192.in-addr.arpa.   IN   NS   bsd.faunet.pl.


1.0.168.192.in-addr.arpa.   IN   PTR   bsd.faunet.pl.
55.0.168.192.in-addr.arpa.   IN   PTR   it.faunet.pl.

----------------------------------------------------------------------




db.company.com

$ttl 3h;

company.com.  IN SOA bsd.company.com. root.company.com.(

2002081001
3H
15M
1W
1D);

company.com. IN NS bsd.company.com.

bsd.company.com. IN A 192.168.0.1
it.company.com.  IN A 192.168.0.55

-----------------------------------------------------------------------------

db.localhost


$ttl 3h;
localhost. IN SOA localhost. root.localhost.(
42
3H
15M
1W
1D
);

localhost. IN NS localhost.
localhost. IN A 127.0.0.1


---------------------------------------------------------------------------------


db.127.0.0


$ttl 3h;
0.0.127.in-addr.arpa.   IN   SOA   localhost.   root.localhost.(
42
3H
15M
1W
1D);

0.0.127.in-addr.arpa.   IN   NS   localhost.
1.0.0.127.in-addr.arpa.   IN   PTR   localhost.




------------------------------------------------------------------------------

na wszystkich plikach zostało wykonane polecenie named-checkzone
i jest OK.

czy ktoś wie co jest grane ??