LINUX.ORG.RU
ФорумAdmin

isc-dhpcd, ddns-update

 


0

1

Уважаемые, подскажите куда :).....
isc-dhcpd и ddns-update
Если делать всё по классике жанра

ddns-update-style interim;
ddns-updates on;
update-conflict-detection false;
update-static-leases on;
authoritative;

subnet 192.168.16.0 netmask 255.255.255.0 {
  range 192.168.16.10 192.168.16.125;
  option domain-name "adm16.local";
  option domain-name-servers 192.168.227.250, 192.168.224.251, 192.168.225.250;
  option routers 192.168.16.251;
  option broadcast-address 192.168.16.255;
  default-lease-time 259200;
  max-lease-time 604800;
}
то всё прекрасно работает.

Но есть сервер с несколькими сетями с конфигом вида:

authoritative;
ddns-update-style interim;
ddns-updates on;
update-conflict-detection false;
update-static-leases on;
allow unknown-clients;
deny bootp;
update-optimization on;

shared-network "net26" {
subnet 192.168.26.0 netmask 255.255.255.0 {
    server-identifier 192.168.26.253;
    range 192.168.26.11 192.168.26.249;
    option subnet-mask 255.255.255.0;
    option routers 192.168.26.254;
    option broadcast-address 192.168.26.255;
    default-lease-time 2592000;
    max-lease-time 3456000;
    option domain-name "adm26.local";
    option domain-name-servers 192.168.227.250, 192.168.224.251, 192.168.225.250;
    option ip-forwarding off;
    }
}

shared-network "net22" {
subnet 192.168.22.0 netmask 255.255.255.0 {
    server-identifier 192.168.22.253;
    range 192.168.22.11 192.168.22.249;
    option subnet-mask 255.255.255.0;
    option routers 192.168.22.254;
    option broadcast-address 192.168.22.255;
    default-lease-time 2592000;
    max-lease-time 3456000;
    option domain-name "adm22.local";
    option domain-name-servers 192.168.227.250, 192.168.224.251, 192.168.225.250;
    option ip-forwarding off;
    }
}

shared-network "net24" {
subnet 192.168.24.0 netmask 255.255.255.0 {
    server-identifier 192.168.24.253;
    range 192.168.24.11 192.168.24.249;
    option subnet-mask 255.255.255.0;
    option routers 192.168.24.254;
    option broadcast-address 192.168.24.255;
    default-lease-time 2592000;
    max-lease-time 3456000;
    option domain-name "adm24.local";
    option domain-name-servers 192.168.227.250, 192.168.224.251, 192.168.225.250;
    option ip-forwarding off;
    }
}
 
и вот на этом сервере не получается ddns-update, ни когда оно в глобальной секции, ни когда внутри
shared-network { }
ни когда внутри
shared-network { subnet { } }

dhcpd запустил с флагом -d, в логах ничего :(

кто подскажет как это делается?
isc-dhcpd-4.3.5



Последнее исправление: guest80 (всего исправлений: 2)

200 с лишним по ноутбучному DHCP и [lease].? Да вам, батенька, никто и никогда такой возможности не сможет предоставить.

anonymous
()
Ответ на: комментарий от anonymous

т.е. надо весь конфиг? я просто не понял вашего акцента :( хорошо я поправлюсь

guest80
() автор топика
Ответ на: комментарий от anonymous

исправил стартовый топик, привёл полные конфиги в логах ничего кроме обычного:

Oct  5 15:38:41 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.33 (74:27:ea:4b:9c:aa) via eth0
Oct  5 15:39:08 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.25 via eth0
Oct  5 15:39:08 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.25 (74:27:ea:4b:d3:3e) via eth0
Oct  5 15:39:20 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.26 via eth0
Oct  5 15:39:20 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.26 (74:27:ea:4b:9e:45) via eth0
Oct  5 15:39:49 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.32 via eth0
Oct  5 15:39:49 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.32 (74:27:ea:4b:9d:3e) via eth0
Oct  5 15:39:59 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.11 via eth0
Oct  5 15:39:59 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.11 (74:27:ea:4b:9b:27) via eth0
Oct  5 15:40:44 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.12 via eth0
Oct  5 15:40:44 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.12 (74:27:ea:4b:9b:33) via eth0
Oct  5 15:40:54 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.52 via eth0
Oct  5 15:40:54 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.52 (74:d4:35:01:0b:2c) via eth0
Oct  5 15:40:55 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.32 via eth0
Oct  5 15:40:55 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.32 (74:27:ea:4b:9d:3e) via eth0
Oct  5 15:41:40 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.21 via eth0
Oct  5 15:41:40 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.21 (74:27:ea:4b:99:63) via eth0
Oct  5 15:41:41 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.34 via eth0
Oct  5 15:41:41 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.34 (74:27:ea:4b:d3:3b) via eth0
Oct  5 15:42:46 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.21 via eth0
Oct  5 15:42:46 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.21 (74:27:ea:4b:99:63) via eth0
Oct  5 15:42:49 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.34 via eth0
Oct  5 15:42:49 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.34 (74:27:ea:4b:d3:3b) via eth0
Oct  5 15:43:41 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.33 via eth0
Oct  5 15:43:41 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.33 (74:27:ea:4b:9c:aa) via eth0
Oct  5 15:44:17 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.12 via eth0
Oct  5 15:44:17 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.12 (74:27:ea:4b:9b:33) via eth0
Oct  5 15:44:20 dhcp-srv dhcpd[12622]: DHCPINFORM from 192.168.26.26 via eth0
Oct  5 15:44:20 dhcp-srv dhcpd[12622]: DHCPACK to 192.168.26.26 (74:27:ea:4b:9e:45) via eth0
в debud.log:
Oct  5 06:45:57 dhcp-srv dhcpd[12622]: reuse_lease: lease age 83451 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.46
Oct  5 06:52:45 dhcp-srv dhcpd[12622]: reuse_lease: lease age 259588 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.40
Oct  5 06:55:05 dhcp-srv dhcpd[12622]: reuse_lease: lease age 86790 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.11
Oct  5 07:21:16 dhcp-srv dhcpd[12622]: reuse_lease: lease age 604460 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.24
Oct  5 07:22:53 dhcp-srv dhcpd[12622]: reuse_lease: lease age 172215 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.21
Oct  5 07:25:37 dhcp-srv dhcpd[12622]: reuse_lease: lease age 256057 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.39
Oct  5 07:26:06 dhcp-srv dhcpd[12622]: reuse_lease: lease age 517802 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.12
Oct  5 07:31:09 dhcp-srv dhcpd[12622]: reuse_lease: lease age 259334 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.16
Oct  5 07:34:25 dhcp-srv dhcpd[12622]: reuse_lease: lease age 86594 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.26
Oct  5 07:37:51 dhcp-srv dhcpd[12622]: reuse_lease: lease age 604683 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.34
Oct  5 07:39:09 dhcp-srv dhcpd[12622]: reuse_lease: lease age 259475 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.49
Oct  5 07:43:34 dhcp-srv dhcpd[12622]: reuse_lease: lease age 173416 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.18
Oct  5 07:43:57 dhcp-srv dhcpd[12622]: reuse_lease: lease age 87116 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.42
Oct  5 07:53:16 dhcp-srv dhcpd[12622]: reuse_lease: lease age 87925 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.20
Oct  5 09:13:03 dhcp-srv dhcpd[12622]: reuse_lease: lease age 246454 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.47
Oct  5 12:32:38 dhcp-srv dhcpd[12622]: reuse_lease: lease age 277423 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.26.16

guest80
() автор топика
Ответ на: комментарий от guest80

прописать в каждом сабнете

ddns-updates on;
ddns-domainname
ddns-hostname

глобально описать зоны обновления согласно ddns- прямые и обратные типа

zone 0.168.192.in-addr.arpa. {
    primary 127.0.0.1;
    key rndckey;
    }
и сам rndckey. в логах должы быть запросы на обновления зон или их ошибки.

anonymous
()
Ответ на: комментарий от anonymous

подскажите как указывать для всего range

         ddns-hostname name;

         The name parameter should be the hostname that will be used in setting up the client's A and PTR records.  If no  ddns-hostname  is  specified  in
         scope, then the server will derive the hostname automatically, using an algorithm that varies for each of the different update methods.
??

указал в сабнете:

authoritative;
ddns-update-style interim;
ddns-updates on;
update-conflict-detection false;
update-static-leases on;
allow unknown-clients;
deny bootp;
update-optimization on;

shared-network "net26" {
subnet 192.168.26.0 netmask 255.255.255.0 {
    ddns-updates on;
    ddns-domainname "adm26.local.";
    server-identifier 192.168.26.253;
    range 192.168.26.11 192.168.26.249;
    option subnet-mask 255.255.255.0;
    option routers 192.168.26.254;
    option broadcast-address 192.168.26.255;
    default-lease-time 2592000;
    max-lease-time 3456000;
    option domain-name "adm26.local";
    option domain-name-servers 192.168.227.250, 192.168.224.251, 192.168.225.250;
    option ip-forwarding off;
    }
}
ДНС сервера это виндовые контроллеры домена (в зонах стоит разрешения для не безопасных обновлений) Зоны из первого пример (где всё работает) расположены на них же, ddns отрабатывает без проблем.

В логах по прежнему ничего нет :(

guest80
() автор топика
Ответ на: комментарий от guest80

гуглится, напимер:

ddns-hostname = pick-first-value(
            option host-name,
            option fqdn.hostname,
            concat( "dhcp-",binary-to-ascii( 10, 8, "-", leased-address ) )

зоны описаны ? rndckey наверное, не нужен для ms dns.

anonymous
()
Ответ на: комментарий от anonymous

сделал по примеру :( результат нулевой.... :( зоны описаны (и есть другой dhcp-сервер с классической настройкой ddns, который обновляет на этих же ДНС-серверах записи в зонах) мне не понятно почему в логах ничего по по поводу ddns, как будто его вообще нет...

guest80
() автор топика
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.