<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jan 12, 2011, at 11:09 PM, Gordon A. Lang wrote:</div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div bgcolor="#ffffff"><div><font face="Arial" size="2">Does Microsoft DNS client code ever use any other DDNS target identifier other than the MNAME? I know some old codes used the NS records and/or the client's resolver list, but it is my understanding that both of those techniques have been completely abandoned -- does anyone believe otherwise? And are there any other techniques used by Microsoft that perhaps I've never heard of -- anyone know?</font></div><div><font face="Arial" size="2"></font></div></div></span></blockquote></div><br><div>I believe Microsoft clients tend to try all three behaviors you've mentioned.</div><div><br></div><div>The last standard I read for this said that the SOA MName is to be used if and only if it corresponds to an NS record of the same name. Otherwise, a random NS record is to be chosen. Of course, many actual DDNS updaters ignore this, trying the MName host regardless of whether it has an NS record; this includes the nsupdate command itself.</div><div><br></div><div>However, ISC's dhcpd, at least version 3.1, follows the standard set forth above unless configured to do otherwise.</div><div><br></div><div>Regards,</div><div>Chris Buxton</div><div>BlueCat Networks</div><div><br></div></body></html>