From owner-freebsd-isp Thu May 14 11:16:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16844 for freebsd-isp-outgoing; Thu, 14 May 1998 11:16:53 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16838 for ; Thu, 14 May 1998 11:16:52 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: from localhost (fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) with SMTP id NAA23513 for ; Thu, 14 May 1998 13:16:53 -0500 (CDT) Date: Thu, 14 May 1998 13:16:53 -0500 (CDT) From: "Matthew D. Fuller" To: isp@FreeBSD.ORG Subject: named messages Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org OK, it's not FreeBSD related, but I imagine there's someone here who knows what these strange messages we've been getting from named mean. Most are of the form: ns named[pid]: ns_resp: TCP truncated: "some.domain.we.dont.serve" IN A some instead show a "1.2.3.4.in-addr-arpa" IN PTR (with of course a real domain and real IP). Is this a problem on someone else's end trying to secondary a domain we don't serve off us, or what? Usually happen either every hour, every half hour, or every 20 minutes or so, randomly switching between intervals. Thoughts? *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message