search for: mclt

...things. In your script you are using the port 519 and 520 for the failover: -------------- failover peer "dhcp-failover" { primary; address dc1.samdom.example.com; port 519; peer address dc2.samdom.example.com; peer port 520; max-response-delay 60; max-unacked-updates 10; mclt 3600; split 128; load balance max seconds 3; } -------------- Why are you using this ports? Are this ports TCP or UDP? Will they be opened automatically? A short explanation would be good. As I told you before, it's one of the best howtos in the wiki. Stefan -------------- next part ---...

...failover to your wiki: I think I found a little bug in your howto. You defined the part for the failover: ## Primary ## failover peer "dhcp-failover" { primary; address dc1.samdom.example.com; peer address dc2.samdom.example.com; max-response-delay 60; max-unacked-updates 10; mclt 3600; split 128; load balance max seconds 3; } ########## ## Secondary ## failover peer "dhcp-failover" { secondary; address dc2.samdom.example.com; peer address dc1.samdom.example.com; max-response-delay 60; max-unacked-updates 10; mclt 3600; load balance max seconds 3...

Anybody have any experience with setting up dhcpd in failover mode between two servers? I set this up on a couple of servers, and it seems to be working, but I don't think it is working "right". It appears both servers are replying to all requests (which for renewals works okay because they both give the same address, but new requests get two different responses). I thought that

..."dhcp-failover" {         primary; # declare this to be the primary server         address 192.168.0.90;         port 647;          peer address 192.168.0.91;         peer port 647;         max-response- delay 30;         max-unacked-updates 10;         load balance max seconds 3;         mclt 1800;         split 255; } as you can see only one server is actively handing out IPs but both try to update the DNS entries. The dynDNS was done as per the WIKI instructions. Regards > Rowland > > >

Hello all, we recently did an classic upgrade of our NT-style domain with LDAP backend to AD (Version 4.4.9-SerNet on CENTOS 7). We had some small issues but all in all it worked pretty good. Now we are in production with 3 DC and have some questions/observations: -- We used to have a WINS server in our old domain and we kept this running without change. Is it possible to migrate this to the DCs?

...d the following for the failover peers to the configuration files on the primary: failover peer "dhcp-failover" { primary; address dc1.samdom.example.com; port 519; peer address dc2.samdom.example.com; peer port 520; max-response-delay 60; max-unacked-updates 10; mclt 3600; split 128; load balance max seconds 3; } ..and secondary: failover peer "dhcp-failover" { secondary; address dc2.samdom.example.com; port 520; peer address dc1.samdom.example.com; peer port 519; max-response-delay 60; max-unacked-updates 10; load bala...

If I don't use DHCP failover, can you tell me how to do to to have manually dhcp start method working... I think I could made a mistake, this is what i did : ( I using Louis script from "old set of script" directory : https://secure.bazuin.nl/scripts/ ) - On server S4 : resolv.conf set to S4 first and S4bis in second - On server S4 : in dhcp-dyndns-debian.sh,

...configuration files on > the primary: > > failover peer "dhcp-failover" { > primary; > address dc1.samdom.example.com; > port 519; > peer address dc2.samdom.example.com; > peer port 520; > max-response-delay 60; > max-unacked-updates 10; > mclt 3600; > split 128; > load balance max seconds 3; > } > > ..and secondary: > > failover peer "dhcp-failover" { > secondary; > address dc2.samdom.example.com; > port 520; > peer address dc1.samdom.example.com; > peer port 519; > max-res...

...---- And from the master --------------------- authoritative; ddns-update-style none; #Start failover configuration failover peer "dhcp-failover" { primary; address sambabuch.example.net; peer address sambabuch-02.example.net; max-response-delay 60; max-unacked-updates 10; mclt 3600; split 128; load balance max seconds 3; } # End failover configuration subnet 192.168.56.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option broadcast-address 192.168.56.255; option time-offset 0; # option routers 192.168.0.1; option domain-name "example.net&...

Hello All, I have 2 samba4 AD server with dhpd and dynamic DNS. I have well understand that for now it's not possible to have 2 DHCP server running in the same time. So I would have at a time only one dhcp server running. If the first server got a problem I want to manually start the isc-dhcp service in the second to rescue the system. But It's not working as I expected... If I switch