На FreeBSD 5.4 в логах/messages вот такие ошибки, нопочта ходит до клиента и обратно инет работает
Jun 27 09:47:38 ks qpopper[902]: Client at "10.0.0.37" resolves to an unknown host name "sm"
Jun 27 09:47:38 ks qpopper[902]: Client address "10.0.0.37" not listed for its host name "sm"
Jun 27 09:47:39 ks qpopper[903]: Client at "10.0.0.37" resolves to an unknown host name "sh.account.local"
Jun 27 09:47:39 ks qpopper[903]: Client address "10.0.0.37" not listed for its host name "sh.account.local"
Jun 27 09:47:40 ks qpopper[904]: Client address "10.0.0.37" not listed for its host name "sh"
Jun 27 09:47:41 ks qpopper[905]: Client at "10.0.0.37" resolves to an unknown host name "cu.account.local"
Jun 27 09:47:41 ks qpopper[905]: Client address "10.0.0.37" not listed for its host name "cu.account.local"
Jun 27 09:55:02 ks qpopper[946]: Client at "10.0.0.17" resolves to an unknown host name "tj.account.local"
Jun 27 09:55:02 ks qpopper[946]: Client address "10.0.0.17" not listed for its host name "tj.account.local"
Jun 27 09:57:20 ks qpopper[949]: Client at "10.0.0.16" resolves to an unknown host name "ti"
Jun 27 09:57:20 ks qpopper[949]: Client address "10.0.0.16" not listed for its host name "ti"
Jun 27 10:01:48 ks qpopper[975]: Client at "10.0.0.11" resolves to an unknown host name "ke"
Jun 27 10:01:48 ks qpopper[975]: Client address "10.0.0.11" not listed for its host name "ke"
Jun 27 10:03:31 ks qpopper[979]: Client address "10.0.0.81" not listed for its host name "ai"
Jun 27 10:03:34 ks qpopper[981]: Client at "10.0.0.25" resolves to an unknown host name "mv"
Jun 27 10:03:34 ks qpopper[981]: Client address "10.0.0.25" not listed for its host name "mv"
Jun 27 10:04:30 ks qpopper[986]: Client at "10.0.0.25" resolves to an unknown host name "mv"
Jun 27 10:04:30 ks qpopper[986]: Client address "10.0.0.25" not listed for its host name "mv"
Чтобы это значило?
>На FreeBSD 5.4 в логах/messages вот такие ошибки, нопочта ходит до клиента
>и обратно инет работает
>
>
>Jun 27 09:47:38 ks qpopper[902]: Client at "10.0.0.37" resolves to an unknown
>host name "sm"
>Jun 27 09:47:38 ks qpopper[902]: Client address "10.0.0.37" not listed for its
>host name "sm"
>Jun 27 09:47:39 ks qpopper[903]: Client at "10.0.0.37" resolves to an unknown
>host name "sh.account.local"
>Jun 27 09:47:39 ks qpopper[903]: Client address "10.0.0.37" not listed for its
>host name "sh.account.local"
>Jun 27 09:47:40 ks qpopper[904]: Client address "10.0.0.37" not listed for its
>host name "sh"
>Jun 27 09:47:41 ks qpopper[905]: Client at "10.0.0.37" resolves to an unknown
>host name "cu.account.local"
>Jun 27 09:47:41 ks qpopper[905]: Client address "10.0.0.37" not listed for its
>host name "cu.account.local"
>Jun 27 09:55:02 ks qpopper[946]: Client at "10.0.0.17" resolves to an unknown
>host name "tj.account.local"
>Jun 27 09:55:02 ks qpopper[946]: Client address "10.0.0.17" not listed for its
>host name "tj.account.local"
>Jun 27 09:57:20 ks qpopper[949]: Client at "10.0.0.16" resolves to an unknown
>host name "ti"
>Jun 27 09:57:20 ks qpopper[949]: Client address "10.0.0.16" not listed for its
>host name "ti"
>Jun 27 10:01:48 ks qpopper[975]: Client at "10.0.0.11" resolves to an unknown
>host name "ke"
>Jun 27 10:01:48 ks qpopper[975]: Client address "10.0.0.11" not listed for its
>host name "ke"
>Jun 27 10:03:31 ks qpopper[979]: Client address "10.0.0.81" not listed for its
>host name "ai"
>Jun 27 10:03:34 ks qpopper[981]: Client at "10.0.0.25" resolves to an unknown
>host name "mv"
>Jun 27 10:03:34 ks qpopper[981]: Client address "10.0.0.25" not listed for its
>host name "mv"
>Jun 27 10:04:30 ks qpopper[986]: Client at "10.0.0.25" resolves to an unknown
>host name "mv"
>Jun 27 10:04:30 ks qpopper[986]: Client address "10.0.0.25" not listed for its
>host name "mv"
>
>Чтобы это значило?Пропиши машины в DNS желательно в обеих зонах.
Сеть организована след образом домен под управлением винды 2000 сервер и шлюз + почтовик по Фряхой
вот файл named.conf
options {
directory "/etc/namedb";
pid-file "/var/run/named/pid";
dump-file "/var/dump/named_dump.db";
statistics-file "/var/stats/named.stats";
listen-on { 127.0.0.1; 222.22.22.222; 10.0.0.5; };
zone "." {
type hint;
file "named.root";
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "master/localhost.rev";
};
// RFC 3152
zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARP A" {
type master;
file "master/localhost-v6.rev";
};
// RFC 1886 -- deprecated
zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT " {
type master;
file "master/localhost-v6.rev";
};
zone "МОЙ.ДОМ.ЕН." {
type master;
file "МОЙ.ДОМ.ЕН.ZONE";
};
//Локальная сеть
zone "0.0.10.in-addr.arpa" {
type slave;
file "slave/0.0.10.in-addr.arpa";
masters {
10.0.0.1;
};
};
zone "account.local" {
type slave;
file "slave/account.local";
masters {
10.0.0.1;
};
};
Не резолвятся hostname'ы авторизующихся машин.
>Не резолвятся hostname'ы авторизующихся машин.Можно по другому сказать, что происходит на машине поддерживающей
обратный резолвинг?Вот здесь...
//Локальная сеть
zone "0.0.10.in-addr.arpa" {
type slave;
file "slave/0.0.10.in-addr.arpa";
masters {
10.0.0.1;
};
};
Т.е. проблема в сервере имен 10.0.0.1 локальной сети? Он кстати под Win2000
>Т.е. проблема в сервере имен 10.0.0.1 локальной сети? Он кстати под Win2000
>
ага....он должен аккуратно и правильно резолвить обратную зону...