This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
host tool used for RIPE hostcounts
- Previous message (by thread): host tool used for RIPE hostcounts
- Next message (by thread): host tool used for RIPE hostcounts
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Mon Nov 26 23:41:15 CET 2001
>>>>> "Olafur" == Olafur Osvaldsson <oli at isnic.is> writes: Olafur> We've been using the host tool from ftp.ripe.net for the Olafur> hostcounts since I don't remember when but noticed some Olafur> strange behaviour this month. Olafur> We got a bunch of these errors: Olafur> *** incomplete resource record for Olafur> ppp129-110.islandssimi.is, offset 8186 ;; response Olafur> truncated to 8192 bytes ;; got answer, 23618 bytes: ;; Olafur> ns_initparse: Message too long *** expand error in Olafur> resource record for islandssimi.is, offset 8186 Olafur> After some diging it looks like this only happens when Olafur> transfering from nameservers with version 9 of bind, wich Olafur> seems to be sending the whole transfer at once instead of Olafur> sending one RR at a time like bind 8 does. Er not quite. The default mode for zone transfers in BIND9 is many-answers. It tries to pack as many RRs into each packet as possible -- not necessarily the whole zone! -- instead of just one RR at a time. Who maintains that host program now? ISTR Brad Knowles mumbling something about taking on that responsibility.
- Previous message (by thread): host tool used for RIPE hostcounts
- Next message (by thread): host tool used for RIPE hostcounts
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]