From owner-freebsd-net Fri Apr 20 11:55:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from black.purplecat.net (ns1.purplecat.net [209.16.228.148]) by hub.freebsd.org (Postfix) with ESMTP id B9FC437B42C for ; Fri, 20 Apr 2001 11:55:11 -0700 (PDT) (envelope-from peter@black.purplecat.net) Received: from localhost (peter@localhost) by black.purplecat.net (8.8.8/8.8.8) with ESMTP id OAA07609 for ; Fri, 20 Apr 2001 14:57:36 -0400 (EDT) (envelope-from peter@black.purplecat.net) Date: Fri, 20 Apr 2001 14:57:36 -0400 (EDT) From: Peter Brezny To: freebsd-net@freebsd.org Subject: dual dns weirdness, DNS/bind guru needed. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've managed to get two different instances of bind running on my primary name server, but there's something weird. Since I've gotten them running. I can't ftp to anything from the box, or even ftp through that box if a client is using it as a gateway, yet nslookup appears to work fine. my resolv.conf file shows the loopback as the name server to use, and the internal instance is configured to listen on the loopback, which it does if you run nslookup ( see below ). I also continue to be rejected by the freebsd.org mail and ftp servers due to something they don't like about the dns of virtual2.sysadmin-inc.com. I've even downloaded the djbdns tools package and used their dnstrace utility to try and find the problem, with no luck. I've attached errors and config files. Any ideas on this one? Thanks in advance. Apr 20 14:48:14 virtual2 qmail: 987792494.040993 delivery 167: deferral: 216.136.204.18_does_not_like_recipient./Remote_host_said:_450_Client_host _rejected:_cannot_find_your_hostname,_[209.16.228.145]/Giving_up_on _216.136.204.18./ ftp: purplecat.net: Non-recoverable failure in name resolution ftp> virtual2# nslookup Default Server: localhost.sysadmin-inc.com Address: 127.0.0.1 > purplecat.net Server: localhost.sysadmin-inc.com Address: 127.0.0.1 Non-authoritative answer: Name: purplecat.net Address: 209.16.228.148 virtual2# vi /etc/resolv.conf domain sysadmin-inc.com nameserver 127.0.0.1 internal named.conf options section. // $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.1 2000/07/15 07:49:29 kris Exp $ options { listen-on { 10.10.1.2; 10.30.1.1; 127.0.0.1; }; directory "/usr/local/etc/namedb-int"; forwarders { 209.16.228.145; }; allow-transfer { 10.10.1.1; //virtual 10.10.1.71; //bsd1 10.10.1.21; //wcsslaw 10.10.1.25; //allsouls 10.30.1.14; //dggw 10.30.1.20; //gkgw 10.30.1.30; }; //cumcgw allow-query { 10.0.0.0/8; 127.0.0.1; }; query-source address 10.10.1.2 port 53; transfer-source 10.10.1.2; 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 named.conf options section. // $FreeBSD: src/etc/namedb/named.conf,v 1.6.2.1 2000/07/15 07:49:29 kris Exp $ options { directory "/etc/namedb"; forwarders { 207.230.75.34; //ns1.deltacom.net 207.230.75.50; //ns2.deltacom.net 206.191.128.46; //c2901.wa.net 199.166.24.1; }; //ns1.vrx.net allow-transfer { 209.16.228.140; //virtual/ns2 209.16.228.150; //virtual alias 209.16.228.145; //virtual2 209.16.228.146; //bsd1 209.16.228.141; //sas 209.16.228.142; //sas 208.133.43.7; //available.New-Era.net 207.230.75.34; //ns1.deltacom.net // potentially bogus? 204.181.41.4; //ns1.deltacom.net * 207.230.75.50; }; //ns2.deltacom.net query-source address 209.16.228.145 port 53; transfer-source 209.16.228.145; listen-on { 209.16.228.145; 209.16.228.150; }; 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