Mailing List Archive: Bug in tcp-env

Bug in tcp-env

Mar 10, 1997, 10:18 AM

Post #1 of 3 (417 views)

tcp-env is refusing connections for sites that have 2 addresses.

Here is an example:

Mar 8 16:57:28 conductor tcp-env@conductor.synapse.net[24210]: warning:
host name/address mismatch: 194.72.245.189 != ns.zetnet.co.uk
Mar 8 16:57:28 conductor tcp-env@conductor.synapse.net[24210]: refused
connect from 194.72.245.189

Nameservice says:

> 194.72.245.189
Server: conductor.synapse.net
Address: 199.84.54.18

Name: ns.zetnet.co.uk
Address: 194.72.245.189

> ns.zetnet.co.uk
Server: conductor.synapse.net
Address: 199.84.54.18

Non-authoritative answer:
Name: ns.zetnet.co.uk
Addresses: 194.72.245.189, 194.247.47.47

Clearly, the forwards and reverse nameservice are in accordance here.

As an aside, I'm already running qmail-smtpd through tcpd; is there any
need for tcp-env at all?

Evan

Re: Bug in tcp-env [ In reply to ]

schinder at leprss

Mar 10, 1997, 10:28 AM

Post #2 of 3 (409 views)

Permalink

On Mon, 10 Mar 1997, Evan Champion wrote:

> Date: Mon, 10 Mar 1997 12:18:39 -0500 (EST)
> From: Evan Champion <evanc@synapse.net>
> To: qmail <djb-qmail@koobera.math.uic.edu>
> Subject: Bug in tcp-env
>
> tcp-env is refusing connections for sites that have 2 addresses.
>
> Here is an example:
>
> Mar 8 16:57:28 conductor tcp-env@conductor.synapse.net[24210]: warning:
> host name/address mismatch: 194.72.245.189 != ns.zetnet.co.uk
> Mar 8 16:57:28 conductor tcp-env@conductor.synapse.net[24210]: refused
> connect from 194.72.245.189
>
> Nameservice says:
>
> > 194.72.245.189
> Server: conductor.synapse.net
> Address: 199.84.54.18
>
> Name: ns.zetnet.co.uk
> Address: 194.72.245.189
>
> > ns.zetnet.co.uk
> Server: conductor.synapse.net
> Address: 199.84.54.18
>
> Non-authoritative answer:
> Name: ns.zetnet.co.uk
> Addresses: 194.72.245.189, 194.247.47.47
>
> Clearly, the forwards and reverse nameservice are in accordance here.

Well, something is wrong, because here's what I get:

% nslookup ns.zetnet.co.uk
Server: leprss.gsfc.nasa.gov
Address: 128.183.127.224

Non-authoritative answer:
Name: ns.zetnet.co.uk
Address: 194.247.47.47

Although 194.72.256.189 is also found to be an address for
ns.zetnet.co.uk, it isn't the first one that comes up. (I run BIND
4.9.5-p1.) Better double check the nameservice.

> As an aside, I'm already running qmail-smtpd through tcpd; is there any
> need for tcp-env at all?
>
> Evan
>
>

--------
Paul J. Schinder
NASA Goddard Space Flight Center,
Code 693, Greenbelt, MD 20771 USA
301-286-1550
schinder@leprss.gsfc.nasa.gov

Re: Bug in tcp-env [ In reply to ]

jrg at blodwen

Mar 16, 1997, 9:08 AM

Post #3 of 3 (404 views)

Permalink

In article <Pine.BSI.3.95.970310121530.28049E-100000@piano.synapse.net> evanc@synapse.net (Evan Champion) writes:
> Mar 8 16:57:28 conductor tcp-env@conductor.synapse.net[24210]: warning:
> host name/address mismatch: 194.72.245.189 != ns.zetnet.co.uk

that's your resolver code syslog'ing that message.

usually it happens when there's an inconsistency between PTR records
and A records for the hostname.

James.