IN 65281 - unknown type (65281)

[Jim Reid]

>>>>> "torben" == torben fjerdingstad <unitfj-bind at tfj.rnd.uni-c.dk> writes:

    torben> ns-soa.darenet.dk should run as a slave for a-aarhus.dk,
    torben> but it won't load the zone from dns.a-aarhus.dk:

    torben> Jun 30 15:18:22 ns named-xfer[11632]: "a-aarhus.dk IN 65281" - unknown type (65281) 
    torben> Jun 30 15:18:22 ns named-xfer[11632]: print_output: unparseable answer (4), zone a-aarhus.dk

    torben> Is it the WINS thing?

Yes.

    torben> Can it really make my nameserver reject the whole zone?

Yes.

    torben> What can they do about it?

It depends on why "they" are. You have two choices: stop propagating
WINS names into the DNS or abandon BIND and only use the M$ name
server. WINS names use an "illegal" resource record type which doesn't
have an officially allocated number from IANA. BIND complains about
these non-standard resource records. (Rightly IMHO.)

So, the options are to (a) only use name servers which support WINS
resource records - ie the M$ name server; (b) configure the M$ name
server to stop it polluting the DNS with these proprietary and
non-standard records. Since WINS is due to die with W2K, option (b) is
probably best. It also means your M$ name server for a-aarhus.dk should
have fewer interoperability problems with other DNS implementations.

According to an earlier posting to bind-users from someone who knows
more about WINS and the M$ name server than I do - admittedly that
doesn't say very much! - what you do is find the Zone Properties
Window in the M$ Name Server and click on the Dialogue Box which says
"Settings Affect Only Local Server" or something like that. You might
have to reboot the M$ box after that too.