The following reply was made to PR config/2632; it has been noted by GNATS.
From: Whit Blauvelt <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re[2]: config/2632: access.conf "allow from" erratic in domain name reverse lookups Date: Wed, 15 Jul 1998 21:08:59 -0400 Marc, I still don't see how that would explain the server presenting the page _sometimes_. A lookup against bond.fftw.com goes like this: \/\/ /etc# nslookup gtwy1.fftw.com bond.fftw.com Server: bond.fftw.com Address: 208.203.240.10 *** bond.fftw.com can't find gtwy1.fftw.com: Non-existent host/domain \/\/ /etc# nslookup 208.203.240.9 bond.fftw.com Server: bond.fftw.com Address: 208.203.240.10 Name: gtwy1.fftw.com Address: 208.203.240.9 In other words, it will derive the name from the number just fine, but not the number from the name. Since the secondary name server seems not to be there at all at the moment, I don't expect it's presenting the information that the primary name server won't. So sometimes Apache seems to be accepting the IP without the double lookup. Either that or occassionally bond.fftw.com admits that it knows the number for the name. Perhaps the real fix is "Use IP's - names aren't reliable." The only limitation here would be when the name is a narrower specification than an class C, and this is desired. > There are two reverse DNS servers listed for 208.203.240 in the outside > world: > > 240.203.208.in-addr.arpa. 21600 NS BOND.FFTW.COM. > 240.203.208.in-addr.arpa. 21600 NS AUTH02.NS.UU.NET. > > However, auth02 claims to know nothing about that zone while bond.fftw.com > does give a reverse lookup. This could cause what you are seeing. > \/\/ I-I I T Blauvelt [EMAIL PROTECTED]
