Wrong size read

Re: Wrong size read

From:

Date:

Time:

The Bind server is sending the zone transfer in a format that
QuickDNS Server doesn't understand. The old format, which is
understood by QuickDNS, is called "one-answer". The new format is
called "many-answer".

The Bind server must be configured to use the older format. In the
'options' statement block, the Bind server administrator must enter
this statement:

transfer-format one-answer;

This must replace any other transfer-format statement currently in place.

Note that one-answer format is the default for Bind 8, but
many-answer format is the default for Bind 9.
____________________________________________________________________
Chris Buxton Men & Mice
Customer Support Specialist Making DNS Easy

At 6:17 PM -0400 6/24/03, Javier Galvez wrote:
>Hi,
>
>I'm getting this "Wrong Size Read" message every time that I try to get a
>zone from a server.
>
>According to the QDNS 3.5.3 manual says...
>
>Wrong size read
>This message appears when QuickDNS receives a packet of a different size
>than what it expects during a secondary zone transfer.
>
>However does not say how to fix either QDNS server or the other side that
>is running BIND.
>
>The server that I must do a complete zone transfer is:
>
>utama.bolnet.bo
>
>and the TLD is "BO" (meaning Bolivia)
>
>Getting the records from a BIND environment I did this:
>
>zone "bo" {
> type slave;
> file "bo";
> masters { 166.114.1.40; };
>};
>
>and the server transfered this info... that I'm not sure if it's right or
>not (partial shown)
>
>$ORIGIN .
>$TTL 86400 ; 1 day
>bo IN SOA utama.bolnet.bo. soporte.nic.bo. (
> 2003062405 ; serial
> 7200 ; refresh (2 hours)
> 3600 ; retry (1 hour)
> 86400 ; expire (1 day)
> 43200 ; minimum (12 hours)
> )
> NS ns.nic.cl.
> NS utama.bolnet.bo.
> NS auth100.ns.uu.net.
>$ORIGIN bo.
>asoban MX 10 correo.asoban.org
>$ORIGIN asoban.bo.
>www CNAME ns.asoban.org.bo.
>$ORIGIN bo.
>astro MX 10 jupiter.umsanet.edu
>$ORIGIN com.bo.bo.
>manpower NS ns4.freeservers.com.
>pennzoil NS ns1.ilatina.com.
>$ORIGIN bo.
>bolnet NS utama.bolnet
> NS maillp.zuper.net.
>$ORIGIN bolnet.bo.
>utama A 166.114.1.40
> MX 0 utama
>$ORIGIN bo.
>bonosol NS ns.bonosol
>$ORIGIN bonosol.bo.
>ns A 166.114.57.240
>$ORIGIN bo.
>$ORIGIN com.bo.
>10 NS ns.entelnet.bo.
>1010123 NS polux.entelchile.cl.
> NS castor.entelchile.cl.
>123 NS polux.entelchile.cl.
> NS castor.entelchile.cl.
>123americatelcentroamerica NS polux.entelchile.cl.
> NS castor.entelchile.cl.
>123americatelelsalvador NS polux.entelchile.cl.
> NS castor.entelchile.cl.
>123americatelguatemala NS polux.entelchile.cl.
> NS castor.entelchile.cl.
>123americatelhonduras NS polux.entelchile.cl.
> NS castor.entelchile.cl.
>
>Thank you for your help on fixing this on the TDL "BO" or in my QDNS 3.5.3
>server
>
>
>
>
>Javier Galvez
>MegaLink
>+(591)-715-22149
>jcgalvez@megalink.com

Sales:
888/4-DPOINT

Support:
858/452-3696