Date: Mon, 7 Dec 1998 19:54:27 -0500 (EST) From: Bill Vermillion <bill@bilver.magicnet.net> To: freebsd-isp@FreeBSD.ORG Subject: Re: resolver behaviour Message-ID: <199812080054.TAA05239@bilver.magicnet.net> In-Reply-To: <366C42B6.F2F7FA0F@softweyr.com> from Wes Peters at "Dec 7, 98 02:03:50 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Wes Peters recently said: > Tony Kimball wrote: > > I confused you by mentioning two related issues in one email. I > > apologize again for doing this. Please allow me to help you > > overcome this confusion by being very very explicit: The problem > > I described as bullet item 2 is present for everyone who has > > no control over their nameservice. This is the majority of users. > Hmmm. It would seem that the majority of users then need to mutiny > and replace their domain name administrators. I'm not denying this is > a problem, just that the idea of coding around the stupidity of the > legions of "IT Professionals" out there would be an impossible, never- > ending task. The 'majority' ?? If that were ture nothing would be working would it. I can't see how people can screwup something like DNS - unless they never bothered to look at it. > > The problem, restated, is this: For reasons which are not always > > evident, but probably relating to cache pollution, individual > > nameservers have bad data. NXDOMAIN replies occur for valid names. > > Applications relying on libc in FreeBSD are thereby prevented from > > making necessary connections. The occurrence is rare, but has > > become sufficiently annoying to me over time so that I am willing > > to fix it. Is any of this related to the far hosts not being reachable at that time? > Most of the time when nameservers have bad data, it has little to > do with cache pollution and much to do with incompetent management. > Such is the case with reverse lookups on my domain right now; the > named.boot file has the wrong .IN-ADDR.ARPA domain for my reverse > file so it cannot possibly work. Emails to my ISP have netted me > zero results. Is this what you're talking about? ;^) Argh!!. I had reverse problems too. I moved four class C's from one (backbone) provieder to another provided (about a hop of the backbone), and spent what seemed like an eternity moving machine IPs', web sites, etc., a few at a time, and building a new DNS as I went. Then I get a call from someone who can't download because it can't do a reverse DNS on the machine. I got reverse DNS with no problems, but if you did it outside our net nada! I figured I had missed something simple, and spent a long time going over everything - over 4000 lines of entries. I finally gave up and called the NOC. I told them the problem and they confirmed it. They said there was a problem. I asked "Yours or Mine". They said probably mine, but they'd call back. Twenty minutes later they called and said it was fixed. It was their side. They had forgotten to pull the reverse DNS from out site. I'd really not expected that from a major provider - at least a major telco. Sometimes it fall apart much higher up than you'd expect. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812080054.TAA05239>