This is not a real summary as I didn't raise a query but might be useful. Recently we demoted a Solaris 2.6 DNS server to be a secondary DNS server against a WIN 2000 DNS server with Active Directory enabled. Solaris server was then complaining about:- named-xfer: "blah.blah IN 33" - unknown type (33) then print_output: short answer (blah, blah), zone foobar.co.uk My fix in the absence of anything spotted on Sun Managers or google was to try out bind-9.2.2 to replace the stock in-named. The version of dig bundled worked on a zone transfer so went for running the 9.2.2 named. This appears to have fixed the problem at the moment, but testing so far is limited to a few hours... Your mileage may vary....I'm simply fixing up an internal network... If anyone can give me reasons as to why I shouldn't do this it would be appreciated and raise a second summary :-) Cheers, Stuart --- Onsite mailto:Stuart.Little@leotel.co.uk Base mailto:Stuart.Little@amberjack.demon.co.uk Phone(onsite): +44-1438-220202 FAX(onsite): +44-1438-233777 _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Thu May 1 11:23:59 2003
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:10 EST