DNS on Windows Server 2003
by Cricket Liu, Matt Larson, Robbie Allen

The unconfirmed error reports are from readers.  They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.

Here's a key to the markup:
        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification

This page was updated August 5, 2008.


UNCONFIRMED  errors and comments from readers: 

[example code] Print zone list (Perl);
I make this as 'serious' only because the code will not run without this fix...

This:

foreach my $objZone (in $objZones) {
print ' ' . $objZOne->Name, "\n";
}

Should be:

foreach my $objZone (in $objZones) {
#print ' ' . $objZOne->Name, "\n";
print ' ' . $objZone->Name, "\n";
}

# Lowecase 'o' in '$objZone->Name' ...


(72)Bottom of page, just below "The Zone Datafiles" heading;
The last sentence refers to Figure 4-2, however 4-2 obviously cannot be the correct figure, based on the textual descripion of what the figure should show. I am not sure which figure would be correct, if any.


[336-340]  entire discussion;
I think that there needs to be an updated treatment of the problem of DNS cache
poisoning on W2kS and W2k3S, when MS DNS is set up to use DNS forwarders.

Even when MS DNS Servers have been configured for "Secured DNS," to prevent cache
poisoning, there is still a major problem when MS DNS is set up to use forwarders and
receives a cache-poisoned response back from the responding DNS server.  It seems
that when MS DNS is set up to use forwarding, it will blindly accept cache-poisoned
responses.  This is a huge problem when the forwarder is not, or cannot be configured
(which seems to be the case with BIND4 and BIND8), to sanitize against cache
poisoning.