The OpenNET Project / Index page

[ новости /+++ | форум | теги | ]

форумы  помощь  поиск  регистрация  майллист  ВХОД  слежка  RSS
"Не хочет работать DHCP+DDNS"
Вариант для распечатки Архивированная нить - только для чтения! 
Пред. тема | След. тема 
Форумы OpenNET: Виртуальная конференция (Public)
Изначальное сообщение [Проследить за развитием треда]

"Не хочет работать DHCP+DDNS"
Сообщение от rumiancev emailИскать по авторуВ закладки(ok) on 15-Мрт-05, 13:35  (MSK)
Звезал dns в chroot, поставил dhcp
Но при выдаче адреса dhcp пишет что нет прав на доб-ие записи!!!
В чём проблема ?
  Рекомендовать в FAQ | Cообщить модератору | Наверх

 Оглавление

Индекс форумов | Темы | Пред. тема | След. тема
Сообщения по теме

1. "Не хочет работать DHCP+DDNS"
Сообщение от rumiancev emailИскать по авторуВ закладки(ok) on 15-Мрт-05, 15:34  (MSK)
>Звезал dns в chroot, поставил dhcp
>Но при выдаче адреса dhcp пишет что нет прав на доб-ие записи!!!
>
>В чём проблема ?


Да,, вот логи dns-а:

15-Mar-2005 13:52:38.664 zone 0.0.127.in-addr.arpa/IN: loaded serial 20050312
15-Mar-2005 13:52:38.665 zone 30.168.192.in-addr.arpa/IN: loaded serial 20050312
15-Mar-2005 13:52:38.666 zone 173.85.194.in-addr.arpa/IN: loaded serial 20051112
15-Mar-2005 13:52:38.667 zone petrsu.ru/IN: loaded serial 20050311
15-Mar-2005 13:52:38.668 running
15-Mar-2005 14:14:35.385 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:35.385 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:38.725 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:38.726 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:39.735 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:39.735 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:40.742 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:40.742 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:41.748 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:41.748 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:42.770 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:42.771 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:43.777 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:43.777 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:44.784 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:44.784 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:45.790 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:45.790 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:46.797 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:46.797 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:47.804 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:47.804 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:48.811 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:48.811 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:49.817 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:49.817 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:50.824 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:50.824 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:51.830 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:51.830 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:52.836 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:52.836 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:53.842 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:53.842 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:54.848 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:54.848 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:55.854 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:55.854 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:56.862 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:56.862 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:57.868 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:57.868 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:58.874 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:58.874 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:14:59.880 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:14:59.880 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:00.886 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:00.886 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:01.892 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:01.892 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:02.899 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:02.899 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:03.906 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:03.906 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:04.912 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:04.912 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:05.919 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:05.919 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:06.925 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:06.926 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:07.932 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:07.932 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:08.938 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:08.938 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:09.944 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:09.944 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:10.950 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:10.950 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:11.956 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:11.957 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:12.964 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:12.964 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:13.970 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:13.970 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:14.977 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:14.977 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:15.983 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:15.983 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:16.989 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:16.989 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:17.998 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:17.998 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:19.004 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:19.004 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:20.013 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:20.013 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:21.019 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:21.019 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:22.027 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:22.027 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:23.033 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:23.033 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:24.039 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:24.039 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:25.045 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:25.045 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:26.051 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:26.051 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:27.057 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:27.057 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:28.063 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:28.063 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:29.070 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:29.070 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:30.076 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:30.077 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:31.083 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:31.083 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:32.089 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:32.089 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:33.095 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:33.095 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:34.101 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:34.101 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:35.107 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:35.107 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:36.114 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:36.114 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:37.120 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:37.120 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:38.128 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:38.128 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:39.134 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:39.134 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:40.140 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:40.140 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:41.146 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:41.146 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:42.153 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:42.153 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:43.160 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:43.160 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:44.166 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:44.166 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:45.172 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:45.172 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:46.180 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:46.181 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:47.187 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:47.187 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:48.193 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:48.193 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:49.201 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:49.201 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:50.207 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:50.207 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:51.215 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:51.215 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:52.220 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:52.220 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:53.227 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:53.227 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:54.233 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:54.233 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:55.240 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:55.240 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:56.246 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:56.246 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:57.253 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:57.253 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:58.259 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:58.259 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:15:59.266 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:15:59.266 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:16:00.272 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:16:00.272 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:16:01.278 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:16:01.278 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:16:02.284 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:16:02.284 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:16:03.290 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:16:03.291 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:16:04.297 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 14:16:04.297 master/petrsu.ru.jnl: create: permission denied
15-Mar-2005 14:22:43.797 zone 0.0.127.in-addr.arpa/IN: loaded serial 20050312
15-Mar-2005 14:22:43.798 zone 30.168.192.in-addr.arpa/IN: loaded serial 20050312
15-Mar-2005 14:22:43.799 zone 173.85.194.in-addr.arpa/IN: loaded serial 20051112
15-Mar-2005 14:22:43.800 zone petrsu.ru/IN: loaded serial 20050311
15-Mar-2005 14:22:43.802 running
15-Mar-2005 16:26:12.304 journal file master/petrsu.ru.jnl does not exist, creating it
15-Mar-2005 16:26:12.312 journal file master/30.168.192.in-addr.arpa.jnl does not exist, creating it

  Рекомендовать в FAQ | Cообщить модератору | Наверх

2. "Не хочет работать DHCP+DDNS"
Сообщение от e719 emailИскать по авторуВ закладки(??) on 15-Мрт-05, 15:46  (MSK)
Ну, насколько я знаю, DNS-серверу надо сказать, чтобы он принимал сообщения nsupdate от DHCP. Что-то типа options {allow-update...
А во-вторых, как можно предположить из логов, делается попытка создать файл журнала master/petrsu.ru.jnl По-моему этим журналом DNS занимается. Нужно дать права DNS на запись в директорию master. Если у тебя DNS не под рутом запускается, а под bind, тогда надо chown bind:bind master
chmod 644 master ну или там сам разберёшься
Вот, такое у меня видение проблемы
  Рекомендовать в FAQ | Cообщить модератору | Наверх

3. "Не хочет работать DHCP+DDNS"
Сообщение от rumiancev emailИскать по авторуВ закладки(ok) on 15-Мрт-05, 16:07  (MSK)
>Ну, насколько я знаю, DNS-серверу надо сказать, чтобы он принимал сообщения nsupdate
>от DHCP. Что-то типа options {allow-update...
>А во-вторых, как можно предположить из логов, делается попытка создать файл журнала
>master/petrsu.ru.jnl По-моему этим журналом DNS занимается. Нужно дать права DNS на
>запись в директорию master. Если у тебя DNS не под рутом
>запускается, а под bind, тогда надо chown bind:bind master
>chmod 644 master ну или там сам разберёшься
>Вот, такое у меня видение проблемы


Да всё так и сделано, но вот фиха вот вывод логов dhcpd :
он пытается много раз сделать запись и только потом выдайт.
Я думаю, может когда я пропис-я в named.conf directory /etc/namedb
для chroot а dhcp смотрит реальную и не может найти ?
Вот лог dhcpd:
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
Added new forward map from fuk.petrsu.ru to 192.168.30.247
added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104

  Рекомендовать в FAQ | Cообщить модератору | Наверх

4. "Не хочет работать DHCP+DDNS"
Сообщение от rumiancev emailИскать по авторуВ закладки(ok) on 15-Мрт-05, 16:14  (MSK)
>>Ну, насколько я знаю, DNS-серверу надо сказать, чтобы он принимал сообщения nsupdate
>>от DHCP. Что-то типа options {allow-update...
>>А во-вторых, как можно предположить из логов, делается попытка создать файл журнала
>>master/petrsu.ru.jnl По-моему этим журналом DNS занимается. Нужно дать права DNS на
>>запись в директорию master. Если у тебя DNS не под рутом
>>запускается, а под bind, тогда надо chown bind:bind master
>>chmod 644 master ну или там сам разберёшься
>>Вот, такое у меня видение проблемы
>
>
>Да всё так и сделано, но вот фиха вот вывод логов dhcpd
>:
>он пытается много раз сделать запись и только потом выдайт.
>Я думаю, может когда я пропис-я в named.conf directory /etc/namedb
>для chroot а dhcp смотрит реальную и не может найти ?
>Вот лог dhcpd:
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>DHCPDISCOVER from 00:60:97:74:36:50 via vlan104
>DHCPOFFER on 192.168.30.247 to 00:60:97:74:36:50 via vlan104
>Added new forward map from fuk.petrsu.ru to 192.168.30.247
>added reverse map from 247.30.168.192.in-addr.arpa to fuk.petrsu.ru
>DHCPREQUEST for 192.168.30.247 (192.168.30.249) from 00:60:97:74:36:50 via vlan104
>DHCPACK on 192.168.30.247 to 00:60:97:74:36:50 via vlan104

Да и что это бы значило ?
Can't update forward map fuk.petrsu.ru to 192.168.30.247: timed out
Права на master стоят
drwxr-xr-x  2 root  wheel   512 Mar 15 17:05 master
потом
ns# ls -la /var/named/etc/namedb/master/
total 12
drwxr-xr-x  2 root  wheel  512 Mar 15 17:05 .
drwxr-xr-x  4 root  wheel  512 Mar 15 17:05 ..
-rw-r--r--  1 bind  bind   263 Mar 14 20:01 173.85.194.in-addr.arpa
-rw-r--r--  1 bind  bind   415 Mar 15 16:37 30.168.192.in-addr.arpa
-rw-r--r--  1 bind  bind   443 Mar 12 13:35 localhost.rev
-rw-r--r--  1 bind  bind   454 Mar 15 16:38 petrsu.ru
В чём дело не понимаю ???

  Рекомендовать в FAQ | Cообщить модератору | Наверх

5. "Не хочет работать DHCP+DDNS"
Сообщение от Andrey Искать по авторуВ закладки(??) on 15-Мрт-05, 16:23  (MSK)
>Права на master стоят
>drwxr-xr-x  2 root  wheel   512 Mar 15 17:05

а пускается bind из под юзера ?? и с какого хе.. он тебе будет в него писАть?

  Рекомендовать в FAQ | Cообщить модератору | Наверх

6. "Не хочет работать DHCP+DDNS"
Сообщение от rumiancev emailИскать по авторуВ закладки(ok) on 15-Мрт-05, 16:28  (MSK)
>>Права на master стоят
>>drwxr-xr-x  2 root  wheel   512 Mar 15 17:05
>
>а пускается bind из под юзера ?? и с какого хе.. он
>тебе будет в него писАть?

Дак в том и дело что при старте бинда на master папку автоматом ставятся права root-а, если меняю их явно сам, то вроде пишет, нооо посмотри что при этом в логах updat-а бинда!

15-Mar-2005 17:19:41.093 update: info: client 127.0.0.1#57554: updating zone 'petrsu.ru/IN': adding an RR at 'fuk.petrsu.ru' A
15-Mar-2005 17:19:41.094 update: info: client 127.0.0.1#49626: updating zone '30.168.192.in-addr.arpa/IN': deleting rrset at '247.30.168.192.in-addr.arpa' PTR
15-Mar-2005 17:19:41.094 update: info: client 127.0.0.1#49626: updating zone '30.168.192.in-addr.arpa/IN': adding an RR at '247.30.168.192.in-addr.arpa' PTR
15-Mar-2005 17:19:42.098 update: info: client 127.0.0.1#60554: updating zone 'petrsu.ru/IN': update unsuccessful: fuk.petrsu.ru: 'name not in use' prerequisite not satisfied (YXDOMAIN)
15-Mar-2005 17:19:42.099 update: info: client 127.0.0.1#51094: updating zone 'petrsu.ru/IN': deleting rrset at 'fuk.petrsu.ru' A
15-Mar-2005 17:19:42.099 update: info: client 127.0.0.1#51094: updating zone 'petrsu.ru/IN': adding an RR at 'fuk.petrsu.ru' A
15-Mar-2005 17:19:42.100 update: info: client 127.0.0.1#55052: updating zone '30.168.192.in-addr.arpa/IN': deleting rrset at '247.30.168.192.in-addr.arpa' PTR
15-Mar-2005 17:19:42.100 update: info: client 127.0.0.1#55052: updating zone '30.168.192.in-addr.arpa/IN': adding an RR at '247.30.168.192.in-addr.arpa' PTR
15-Mar-2005 17:19:43.104 update: info: client 127.0.0.1#53210: updating zone 'petrsu.ru/IN': update unsuccessful: fuk.petrsu.ru: 'name not in use' prerequisite not satisfied (YXDOMAIN)
15-Mar-2005 17:19:43.105 update: info: client 127.0.0.1#50263: updating zone 'petrsu.ru/IN': deleting rrset at 'fuk.petrsu.ru' A
15-Mar-2005 17:19:43.105 update: info: client 127.0.0.1#50263: updating zone 'petrsu.ru/IN': adding an RR at 'fuk.petrsu.ru' A
15-Mar-2005 17:19:43.106 update: info: client 127.0.0.1#64037: updating zone '30.168.192.in-addr.arpa/IN': deleting rrset at '247.30.168.192.in-addr.arpa' PTR
15-Mar-2005 17:19:43.106 update: info: client 127.0.0.1#64037: updating zone '30.168.192.in-addr.arpa/IN': adding an RR at '247.30.168.192.in-addr.arpa' PTR
15-Mar-2005 17:19:44.110 update: info: client 127.0.0.1#50896: updating zone 'petrsu.ru/IN': update unsuccessful: fuk.petrsu.ru: 'name not in use' prerequisite not satisfied (YXDOMAIN)
15-Mar-2005 17:19:44.111 update: info: client 127.0.0.1#60766: updating zone 'petrsu.ru/IN': deleting rrset at 'fuk.petrsu.ru' A
15-Mar-2005 17:19:44.111 update: info: client 127.0.0.1#60766: updating zone 'petrsu.ru/IN': adding an RR at 'fuk.petrsu.ru' A
15-Mar-2005 17:19:44.112 update: info: client 127.0.0.1#64702: updating zone '30.168.192.in-addr.arpa/IN': deleting rrset at '247.30.168.192.in-addr.arpa' PTR
15-Mar-2005 17:19:44.112 update: info: client 127.0.0.1#64702: updating zone '30.168.192.in-addr.arpa/IN': adding an RR at '247.30.168.192.in-addr.arpa' PTR


Т.е он по сто раз делает одно и то же и в конце концов IP выдаётся, запиь паявляется..

  Рекомендовать в FAQ | Cообщить модератору | Наверх

7. "Не хочет работать DHCP+DDNS"
Сообщение от e719 emailИскать по авторуВ закладки(??) on 15-Мрт-05, 16:32  (MSK)
>>Права на master стоят
>>drwxr-xr-x  2 root  wheel   512 Mar 15 17:05
Я ж написал chown bind:bind master
чтобы получилось
>>drwxr-xr-x  2 bind bind   512 Mar 15 17:05
  Рекомендовать в FAQ | Cообщить модератору | Наверх

8. "Не хочет работать DHCP+DDNS"
Сообщение от e719 emailИскать по авторуВ закладки(??) on 15-Мрт-05, 16:37  (MSK)
Ну уже прогресс, по крайней мере
Но тут я уже ничего не могу сказать, в DHCP я не спец :(
  Рекомендовать в FAQ | Cообщить модератору | Наверх

9. "Не хочет работать DHCP+DDNS"
Сообщение от rumiancev emailИскать по авторуВ закладки(ok) on 15-Мрт-05, 17:37  (MSK)
>Ну уже прогресс, по крайней мере
>Но тут я уже ничего не могу сказать, в DHCP я не
>спец :(

Вот вроде разобрался, но не до конца.
Фиха в том, что до этого я дхсп подымал на виланах, и в этой сети есть ещё один дхсп, а вот ща попробывал воткнуть в хаб тот куда воткнут клиент, ифайс em1. И всё ок. Вот ктонить ответил мне, что происходит еле в сети 2 дхцп как происходит и с какого дхсп выдача IP ?

  Рекомендовать в FAQ | Cообщить модератору | Наверх

10. "Не хочет работать DHCP+DDNS"
Сообщение от e719 emailИскать по авторуВ закладки(??) on 15-Мрт-05, 18:52  (MSK)
>дхцп как происходит и с какого дхсп выдача IP ?
С любого, кто первый ответил

  Рекомендовать в FAQ | Cообщить модератору | Наверх

11. "Не хочет работать DHCP+DDNS"
Сообщение от e719 emailИскать по авторуВ закладки(??) on 15-Мрт-05, 18:55  (MSK)
А ДНС будет принимать только с того, с которого ты ему разрешил
  Рекомендовать в FAQ | Cообщить модератору | Наверх

12. "Не хочет работать DHCP+DDNS"
Сообщение от rumiancev emailИскать по авторуВ закладки(ok) on 17-Мрт-05, 10:04  (MSK)
>А ДНС будет принимать только с того, с которого ты ему разрешил
>
Проблема вроде решилась, но остаётся вопрос. Как в dhcp сделать файл с логами ? И логируется ли в leases файл хосты статические, т.е по MAC ?

  Рекомендовать в FAQ | Cообщить модератору | Наверх


Удалить

Индекс форумов | Темы | Пред. тема | След. тема
Пожалуйста, прежде чем написать сообщение, ознакомьтесь с данными рекомендациями.




Партнёры:
PostgresPro
Inferno Solutions
Hosting by Hoster.ru
Хостинг:

Закладки на сайте
Проследить за страницей
Created 1996-2025 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру