Quoting Scott D. Yelich ([EMAIL PROTECTED]):
> > > > Jun 26 01:10:23 ns1 tcp-env[4348]: refused connect from 216.221.160.30
> > > > dig -x output...
> > > > ;; ANSWER SECTION:
> > > > 30.160.221.216.in-addr.arpa. 11h22m24s IN PTR cobalt.
> > > > 30.160.221.216.in-addr.arpa. 11h22m24s IN PTR cobalt.propagation.net.
>
> Well, I don't want to get into a pissing contest -- but I hate to make
> hacks on software (ie: qmail/tcp-env) to allow a special case to work.
> I'm going to wait and continue to investigate if this is a tcp-env snafu
> or a loose bind implementation, etc.
The problem here is, as DJB pointed out, tcp wrappers can't do a
lookup on 216.221.160.30 and cobalt.propagation.net and get the
responses to jive. cobalt.propagation.net=216.221.160.30 but
216.221.160.30=cobalt. Why do you have two PTR entries? The second,
correct PTR record is sufficient, unless I'm really missing something.
Tcp wrappers behaves like this if compiled with D_PARANOID set or
something, or "ALL: PARANOID" is in /etc/hosts.deny.
In any case, if you dropped the first entry, it would probably work
fine. I'd just use tcpserver, really, as Dan suggested quite
vehemently :-).
Aaron
