From owner-freebsd-hackers  Wed Oct 18 07:27:50 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id HAA02606
          for hackers-outgoing; Wed, 18 Oct 1995 07:27:50 -0700
Received: from chrome.jdl.com (chrome.onramp.net [199.1.166.202])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA02601
          for <freebsd-hackers@freebsd.org>; Wed, 18 Oct 1995 07:27:46 -0700
Received: from localhost.jdl.com (localhost.jdl.com [127.0.0.1]) by chrome.jdl.com (8.6.11/8.6.9) with SMTP id JAA09753 for <freebsd-hackers@freebsd.org>; Wed, 18 Oct 1995 09:27:38 -0500
Message-Id: <199510181427.JAA09753@chrome.jdl.com>
X-Authentication-Warning: chrome.jdl.com: Host localhost.jdl.com didn't use HELO protocol
To: freebsd-hackers@freebsd.org
Subject: DNS question
Clarity-Index: null
Reply-To: jdl@chromatic.com
Threat-Level: none
Software-Engineering-Dead-Seriousness: There's no excuse for unreadable code.
Net-thought: If you meet the Buddha on the net, put him in your Kill file.
Date: Wed, 18 Oct 1995 09:27:38 -0500
From: Jon Loeliger <jdl@chrome.onramp.net>
Sender: owner-hackers@freebsd.org
Precedence: bulk

Hackers,

Is there a way to reliably claim to do DNS for anything less than
a full Class-C subnet?  I only have a 3-bit subnet, and I question
my 'Net friendliness if I claim this in my named.boot:

    directory       /etc/namedb

    cache     .                                   named.root
    primary   0.0.127.IN-ADDR.ARPA                localhost.rev

    primary   jdl.com                             jdl.hosts
    primary   166.1.199.IN-ADDR.ARPA              jdl.rev

The point here is that I appear to resolve all of subet 199.1.166.*
when I really only can legitimately resolve 199.1.166.[200-207].
Is there some syntax not revealed in the Albitz/Cricket book that
means sort-a like:

    primary   200.166.1.199.IN-ADDR.ARPA/29              jdl.rev

Meta-question: Is there a better DNS list to question for this one?

Thanks,
jdl