<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16544" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2>
<DIV><FONT face=Arial size=2><SPAN class=124062109-31102007>This week we moved
from dhcpd 3.0.5 to 3.1.0. One of the reasons was the new option
update-conflict-detection.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=124062109-31102007>After some testing
some things are not clear.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=124062109-31102007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=124062109-31102007>If
update-conflict-detection is true, the dhcp-server updates the dns-server with
the A, PTR and TXT record.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=124062109-31102007>If
update-conflict-detection is false, the dhcp-server updates the dns-server with
only the A and PTR record.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=124062109-31102007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=124062109-31102007>But what we see in
de dhcpd.log file is that when a system releases it's ip-adress, the dhcp-server
does first a check if the TXT record exist. If it fails (and it does because no
TXT record was written to the dns-server), the A record is not removed. The
reverse mapping is removed from the dns-server.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=124062109-31102007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=124062109-31102007>Why first a check?
Why not removing the A record on a release?</SPAN></FONT></DIV>
<DIV></FONT> </DIV></DIV>
<DIV align=left><FONT face=Arial size=2>--</FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Meindert van den
Berg</FONT></DIV></BODY></HTML>