From owner-freebsd-isp Fri Mar 20 07:59:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13795 for freebsd-isp-outgoing; Fri, 20 Mar 1998 07:59:45 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from theonlynet.com (port1.slc.celestar.com [207.201.73.32] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13721 for ; Fri, 20 Mar 1998 07:59:35 -0800 (PST) (envelope-from rricci@theonlynet.com) Received: from theonlynet.com (marvin [192.168.1.2]) by theonlynet.com (8.8.8/8.8.8) with ESMTP id JAA04599 for ; Fri, 20 Mar 1998 09:10:18 -0700 (MST) Message-ID: <35129073.24352D59@theonlynet.com> Date: Fri, 20 Mar 1998 07:51:15 -0800 From: Robert Ricci Organization: Kruton,. Inc. X-Mailer: Mozilla 4.04 [en] (X11; I; IRIX 6.2 IP22) MIME-Version: 1.0 To: FreeBSD ISP Subject: Funky DNS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm having some VERY strange things going on with DNS. We recently moved our server (running 2.2.1), and now it has a different IP address. After changing around things in our zone file, things worked great for a day, then strange things started happening: 1) Many of our customers (who use ns3.theonlynet.com for their name server) have reported that their web browsers work fine, but their mail programs get a DNS error when trying to look up mail.theonlynet.com, which is a CNAME for ns3. Typing "mail.theonlynet.com" in the URL line of Netscape brings up our home page correctly. (www, ftp, mail, etc. are CNAMES for ns3 - we're pretty small.) If they have them enter the actual IP of the server in their mail settings, everything pops up fine. Why will Netscape do DNS lookups when Eudora won't? 2) When I try to use "nslookup" from my home FreeBSD machine, I get the error message :"*** Can't find server name for address 201.201.125.66: Non-existent host/domain" and it falls back on another name server. (207.201.125.66 is ns3's IP) However, like our customers, Netscape will do DNS lookups just fine, using that server. Where should I be looking to find a solution for this? By the way, we're running 4.9.4 (I'd appreciate any thoughts on how easy it is to upgrade to 8). Since this odd behavior started, the following line's been showing up in /var/log/messages every time I start named: Mar 20 08:52:58 ns3 named[7825]: Return from getdtablesize() > FD_SETSIZE , but it still comes up and agrees to answer queries. I'd appreciate any pointers you guys could give me, and if you'd like to see a copy of my named.boot and zone files, I'll post 'em. Robert Ricci rricci@theonlynet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message