bind update on .... from dhcp rejected: incoming update is less critical than outgoing update

Fabien Mauger Fabien.Mauger at axeip.fr
Fri Dec 19 15:50:01 UTC 2008


Hi,

I m experiencing the following log message in the secondary peer of my
DHCP servers.

For every bind I've got the message:

==> bind update on ... from dhcp rejected: incoming update is less
critical than outgoing update

Everything seems to work, but I was wondering what can generate those
logs?

I m running the version V3.1.2rc1

With the following configuration:

####################################
## configuration DHCPD de primary ##
####################################

ddns-update-style ad-hoc;
one-lease-per-client true;
default-lease-time 300;
max-lease-time 300;
authoritative;

local-address 172.16.21.38;
#log-facility local7;

failover peer "dhcp" {
         primary;
         address 172.16.21.38;
         port 519;
         peer address 172.16.21.51;
         peer port 520;
         max-response-delay 60;
         max-unacked-updates 10;
         mclt 600;
         split 128;
         load balance max seconds 3;
         }

# include du fichier contenant les scopes. #

include "/etc/dhcpd.master";


######################################
## configuration DHCPD de secondary ##
######################################

ddns-update-style ad-hoc;
one-lease-per-client true;
default-lease-time 300; 
max-lease-time 300;
authoritative;

local-address 172.16.21.51;
#log-facility local7;

failover peer "dhcp" {
         secondary;
         address 172.16.21.51;
         port 520;
         peer address 172.16.21.38;
         peer port 519;
         max-response-delay 60;
         max-unacked-updates 10;
}




#################################################
##############  dhcpd.master ####################
#################################################
subnet 192.168.1.0 netmask 255.255.255.0 
        { 

        option broadcast-address 192.168.1.255;
        option routers 192.168.1.254;


        pool { 
                failover peer "dhcp";
                range 192.168.1.10 192.168.1.13;
                deny dynamic bootp clients;
                } 
        group ADSL-Flore {
                host Fraise { hardware ethernet 00:14:7F:00:5D:A8;}
                host Agrumes { hardware ethernet 00:14:7F:00:5F:EB;}
                host Fleurs { hardware ethernet 00:14:7F:00:5D:49;}
                host Arbres { hardware ethernet 00:14:7F:00:5F:6E;}
                host Legumes { hardware ethernet 00:14:7F:00:5D:67;}
                host Poisson { hardware ethernet 00:14:7F:00:5F:FC;}
                host Mammifere { hardware ethernet 00:14:7F:00:5D:8B;}
                host laminestet { hardware ethernet 00:15:C5:C7:5C:B8;}
                filename "xxxxxx";
                next-server 172.16.21.59;
                }
        }

Ty in advance.

Fabien

 
  
" Ce message et toutes les pieces jointes sont etablis a l'attention 
exclusive de ses destinataires et sont confidentiels.  L'internet ne 
permettant pas d'assurer l'integrite de ce message, le contenu de ce
message ne represente en aucun cas un engagement de la part de notre 
societe. Si vous recevez ce message par erreur, merci de le detruire 
et d'en avertir immediatement l'expediteur.

  This message contains privileged and confidential information.  Given 
that the internet does not allow us to make sure of the communication's
integrity,  the content of this message does not  represent in any case
a commitment from our compagny.  If you are not the intended recipient,  
please notify  us  immediately and delete  this  e-mail  (including any 
attachments) from your system. "



More information about the dhcp-users mailing list