<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> Latest patch is there. <a class="moz-txt-link-freetext" href="http://rawhide.redhat.com/pub/redhat/linux/rawhide/i386/RedHat/RPMS/bind-9.2.2.P3-1.i386.rpm">http://rawhide.redhat.com/pub/redhat/linux/rawhide/i386/RedHat/RPMS/bind-9.2.2.P3-1.i386.rpm</a> Paul Iadonisi wrote: <blockquote type="cite" cite="mid1064618529.8805.15.camel@va.local.linuxlobbyist.org"> <pre wrap="">On Fri, 2003-09-26 at 15:28, Michal Jaegermann wrote: [snip] </pre> <blockquote type="cite"> <pre wrap="">A solution turned out to be to explictitely declare a name resolution order to 'winbind lmhosts ....', or whatever that is called, in smb.conf. I do not have Samba here so I cannot check that directive but it is mentioned explicitely in one of 'BROWSING' documents. </pre> </blockquote> <pre wrap=""> If your customer has control of his DNS server and it's running bind, then the delegation-only patch can be applied and then he can list all the gTLDs /etc/named.conf. There may be patches for other DNS servers as well. I applied the patch at <a class="moz-txt-link-abbreviated" href="http://www.isc.org">www.isc.org</a> and am now happily seeing the normal, non-Verisign corrupted dns behavior. (The version in rawhide is actually a bit outdated. It's 9.2.2-P1 and ISC recommends 9.2.2-P3.) At least until they circumvent it some other way. *sigh* </pre> </blockquote> </body> </html>