error using BIND 8.2.1 against Microsoft's DNS

[Jim Reid]

>>>>> "Daniel" == Daniel A Monjar <dmonjar at orgtek.com> writes:

    Daniel> I have MS's DNS running on NT 4.0 SP3.  It is the primary.
    Daniel> I'm trying to set up an 8.2.1 on Linux 2.2.5 as a
    Daniel> secondary.  I've got the book (Cricket's) and have read
    Daniel> it.  BIND starts but it looks like it can't 
    Daniel> do a zone transfer from the MS POS DNS:

    >> Aug  9 10:30:38 monjard named-xfer[4483]: "orgtek.com IN 65281" - unknown type (65281)
    >> Aug  9 10:30:38 monjard named-xfer[4483]: print_output: unparseable answer (4), zone orgtek.com
    >> Aug  9 10:30:38 monjard named-xfer[4484]: "155.10.in-addr.arpa IN 65282" - unknown type (65282)
    >> Aug  9 10:30:38 monjard named-xfer[4484]: print_output: unparseable answer (4), zone 155.10.in-addr.arpa

    Daniel> My intent is to let the MS DNS be primary so that it can feed the WINS/DHCP addresses to the BIND
    Daniel> secondaries.  I'm only going to let the clients know about the BIND secondaries because the MS DNS
    Daniel> flakes out too frequently.

    Daniel> Is the "unknown type (65282)" a known problem with MS DNS's or is it a config error on my end?

Both. The M$ name server is generating proprietary, undocumented and
non-standard WINS resource records. [M$ just plucked a number out of
the ether for this RR type.] No other name server implementations
support these AFAIK. What you have to do is tell your M$ name server
to stop pumping these out, which seems to defeat what you are trying
to do.

I've been told that ticking some box in the M$ Zone Properties window
- something like "settings only affects the local server" - stops it
spouting WINS RR types into the DNS. You probably need to reboot the
box after you do this too.