From owner-freebsd-net  Tue Oct  2  9:30:39 2001
Delivered-To: freebsd-net@freebsd.org
Received: from newmail.skyrunner.net (newmail.skyrunner.net [208.133.44.6])
	by hub.freebsd.org (Postfix) with ESMTP id 86A1937B409
	for <freebsd-net@freebsd.org>; Tue,  2 Oct 2001 09:30:34 -0700 (PDT)
Received: from skyrunne6e8soa (booray.new-era.com [208.150.25.130])
	by newmail.skyrunner.net (8.11.2/8.11.0/SuSE Linux 8.11.0-0.4) with SMTP id f92GUWs29536
	for <freebsd-net@freebsd.org>; Tue, 2 Oct 2001 12:30:32 -0400
From: "Peter Brezny" <peter@skyrunner.net>
To: <freebsd-net@freebsd.org>
Subject: dual dns resolution problem
Date: Tue, 2 Oct 2001 12:27:08 -0400
Message-ID: <NNEHJMNKGDNGPMJJFHCBAEDECDAA.peter@skyrunner.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org

The Problem:

Applications seem unable to resolve dns information.
ssh and sendmail are examples.

Example:

%ssh novell.com
ssh: novell.com: Non-recoverable failure in name resolution

%nslookup novell.com
Server:  localhost.inside-polk.skyrunner.net
Address:  127.0.0.1

Name:    novell.com
Address:  192.233.80.9

I've got a system running two versions of bind, to handle resolution of
public address and their component private addresses for public ip's that
use static nat to hit an internal address.

dig and nslookup work fine, and you can choose which instance of bind to use
to lookup since they each only listen on particular ip's.

Has anyone seen this problem before?  I feel sure that it arises from having
two instances of bind running on the same machine.  I've attached the
options section of each independent instance's named.conf file at the bottom
of this message.


Thanks for your help!


Peter Brezny
Skyrunner.net


Internal instance:
// $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.2 2001/03/05 13:34:52 asmodai
Exp $
//

options {
        directory "/etc/namedb-int";

        forwarders {
                63.167.198.158;
                205.152.121.3;
                205.152.121.2;
        };

        allow-query     { 10.0.0.0/8; 127.0.0.1; };
        query-source address 10.3.0.1 port 53;

        allow-transfer { 10.0.0.0/8; };
        transfer-source 10.3.0.1;

        listen-on { 10.3.0.1; 10.100.100.1; 127.0.0.1; };

        dump-file "s/named_dump.db";
        pid-file "s/named.pid";

};      //end of options

controls { unix "/var/run/ndc-internal" perm 0660 owner 0 group 53; };


External Instance:
// $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.2 2001/03/05 13:34:52 asmodai
Exp $
//

options {
        directory "/etc/namedb";

        forwarders {
                205.152.121.3;
                205.152.121.2;
        };

query-source address 63.167.198.158 port 53;
transfer-source 63.167.198.158;
allow-transfer { none; };

listen-on { 63.167.198.158; 63.167.198.153; };

dump-file "s/named_dump.db";
pid-file "s/named.pid";

};      //end of options

controls { unix "/var/run/ndc-external" perm 0660 owner 0 group 53; };


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message