Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Jan 2001 15:31:05 -0800
From:      Edwin Culp <eculp@EnContacto.Net>
To:        J & C Frazier <admin@csocs.com>
Cc:        alex huppenthal <alex@aspenworks.com>, isp@FreeBSD.ORG
Subject:   Re: Problems with sendmail and NSI
Message-ID:  <979860665.3a677cb933ea8@Mail.MexComUSA.net>
In-Reply-To: <3A67727D.44A40EF4@csocs.com>
References:  <Pine.BSF.4.21.0101171719490.22366-100000@workhorse.iMach.com> <3A663920.A79412FC@csocs.com> <3A663AE7.E1F2AFA5@csocs.com> <00dc01c080e8$166f6120$1700a8c0@d7k> <979796477.3a6681fda7468@Mail.MexComUSA.net> <014701c0811a$27800cd0$1700a8c0@d7k> <979824566.3a66efb633063@Mail.MexComUSA.net> <3A67727D.44A40EF4@csocs.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Quoting J & C Frazier <admin@csocs.com>:

> Negative, that is obviously a problem of yours.  csocs.com resolves just
> fine.

Could be, I'm far from perfect, but with about 4,000 emails yesterday yours is
the only one that I have screwed up and the only one that has a problem
resolving.  

This may be interesting.

Using one of PacBell's Name Servers since mine is screwed up:

# nslookup csocs.com
Server:  dns1-sf.snfc21.pacbell.net
Address:  206.13.28.12
 
*** dns1-sf.snfc21.pacbell.net can't find csocs.com: Non-existent host/domain   
-----------------------------------------------------
Same PacBell Name Server will tell us who your NS's are:

# nslookup
Default Server:  dns1-sf.snfc21.pacbell.net
Address:  206.13.28.12
 
> set type=ns
> csocs.com
Server:  dns1-sf.snfc21.pacbell.net
Address:  206.13.28.12
 
Non-authoritative answer:
csocs.com       nameserver = NS2.COLOCATEUSA.NET
csocs.com       nameserver = NS2.csocs.com
csocs.com       nameserver = NS.csocs.com
 
Authoritative answers can be found from:
NS2.COLOCATEUSA.NET     internet address = 207.49.20.5
NS2.csocs.com   internet address = 207.49.21.235
NS.csocs.com    internet address = 207.49.21.234 
------------------------------------------------------
Hmmm.... I'm a little confused as to why PacBell doesn't resolve for csocs.com.

> There is no dns problem here, only a routing/filter problem with a node
> inbetween me and NSI.

I'm very glad to hear that you don't have a dns problem, please let me/us know
what it was when you find it because I'm confused.

Good luck,

ed
> 
> Edwin Culp wrote:
> 
> > Alex,
> >
> > Thanks.  I just found what is probably the Network Solutions problem in
> my
> > maillog quite by accident.
> >
> > I have several hundred of these.
> >
> > Jan 18 05:20:38 EnContacto sendmail[83075]: f0IDKcm83075:
> ruleset=check_mail,
> > arg1=<admin@csocs.com>, relay=root@shell.csocs.com [207.49.21.231] (may
> be
> > forged), reject=451 4.1.8 <admin@csocs.com>... Domain of sender address
> > admin@csocs.com does not resolve
> > Jan 18 05:20:38 EnContacto sendmail[83075]: f0IDKcm83075:
> > from=<admin@csocs.com>, size=1313, class=0, nrcpts=0, proto=ESMTP,
> daemon=MTA,
> > relay=root@shell.csocs.com [207.49.21.231] (may be forged)
> > Jan 18 05:20:39 EnContacto sendmail[83076]: f0IDKdm83076:
> ruleset=check_mail,
> > arg1=<admin@csocs.com>, relay=root@shell.csocs.com [207.49.21.231] (may
> be
> > forged), reject=451 4.1.8 <admin@csocs.com>... Domain of sender address
> > admin@csocs.com does not resolve
> > Jan 18 05:20:39 EnContacto sendmail[83076]: f0IDKdm83076:
> > from=<admin@csocs.com>, size=4310, class=0, nrcpts=0, proto=ESMTP,
> daemon=MTA,
> > relay=root@shell.csocs.com [207.49.21.231] (may be forged)
> > Jan 18 05:22:46 EnContacto sendmail[83115]: f0IDMhm83115:
> ruleset=check_mail,
> > arg1=<admin@csocs.com>, relay=root@shell.csocs.com [207.49.21.231],
> reject=451
> > 4.1.8 <admin@csocs.com>... Domain of sender address admin@csocs.com does
> not
> > resolve
> >
> > IMHO, step one is fix the DNS and take it from there.  Hopefully/probably
> this
> > will get him up a going.
> >
> > provecho y saludos,
> >
> > ed
> >
> > Quoting alex huppenthal <alex@aspenworks.com>:
> >
> > > Ed,
> > >
> > >  Thanks for your comments.  I agree, it's strange. However, J & C
> Frazier
> > > commented that there are 'A' record in that server. Unless it's
> configured
> > > to be available only to private users, there's definitely a problem. no
> A
> > > records means Bind is broken there. *s
> > >
> > >  Hope it helps.  It's pretty nice to see everyone pitching in to help
> out
> > > like this.
> > >
> > >  -Alex
> > >
> > > ----- Original Message -----
> > > From: "Edwin Culp" <eculp@EnContacto.Net>
> > > To: "alex huppenthal" <alex@aspenworks.com>
> > > Cc: "J & C Frazier" <admin@csocs.com>; "Forrest W. Christian"
> > > <forrestc@imach.com>; <freebsd-isp@FreeBSD.ORG>
> > > Sent: Wednesday, January 17, 2001 10:41 PM
> > > Subject: Re: Problems with sendmail and NSI
> > >
> > >
> > > > Alex,
> > > >
> > > > Thanks, nice to have access to dlint - webbased.  I can think of many
> > > times when
> > > > it would have really come in handy.
> > > >
> > > > As far as the csocs.com problem is concerned, one thing really got my
> > > attention.
> > > >
> > > >  ;; trying nameserver NS.csocs.com.
> > > > ERROR: no A records found.
> > > >
> > > > That might be a good place to start.
> > > >
> > > > I also get that none of the NS are authoritative
> > > >
> > > > named-xfer[1610]: [207.49.21.234] not authoritative for csocs.com,
> SOA
> > > query got
> > > > rcode 0, aa 0, ancount 1, aucount 0
> > > > and
> > > >  named-xfer[1624]: [207.49.20.5] not authoritative for csocs.com, SOA
> > > query got
> > > > rcode 0, aa 0, ancount 1, aucount 3
> > > > and
> > > >  named-xfer[1629]: [207.49.21.235] not authoritative for csocs.com,
> SOA
> > > query
> > > > got rcode 0, aa 0, ancount 1, aucount 0
> > > >
> > > > not good
> > > >
> > > > ed
> > > >
> > > > Quoting alex huppenthal <alex@aspenworks.com>:
> > > >
> > > > > you are welcome to use our dlint window to debug your DNS
> > > > >
> > > > > http://aspenworks.com/development/dns2.php
> > > > >
> > > > > dlint is a nice utility, we've just put a php wrapper around it for
> > > > > web-based use.
> > > > >
> > > > > Cheers,
> > > > >
> > > > >  -Alex
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "J & C Frazier" <admin@csocs.com>
> > > > > To: "Forrest W. Christian" <forrestc@imach.com>; "Edwin Culp"
> > > > > <eculp@EnContacto.Net>; <freebsd-isp@FreeBSD.ORG>
> > > > > Sent: Wednesday, January 17, 2001 5:37 PM
> > > > > Subject: Re: Problems with sendmail and NSI
> > > > >
> > > > >
> > > > > > Interesting, it also appears ns.csocs.com is giving
> non-authoritive
> > > > > > responces on zones and domains it should be controlling.  What
> > > > > > a mess.
> > > > > >
> > > > > > J & C Frazier wrote:
> > > > > >
> > > > > > > The IP is 207.49.21.231 (csocs.com).  Also note the following:
> > > > > > >
> > > > > > > # nslookup
> > > > > > > Default Server:  localhost.csocs.com
> > > > > > > Address:  127.0.0.1
> > > > > > >
> > > > > > > > networksolutions.com
> > > > > > > Server:  localhost.csocs.com
> > > > > > > Address:  127.0.0.1
> > > > > > > Non-authoritative answer:
> > > > > > > Name:    networksolutions.com
> > > > > > > Address:  216.168.224.69
> > > > > > >
> > > > > > > > ns1.netsol.com
> > > > > > > Server:  localhost.csocs.com
> > > > > > > Address:  127.0.0.1
> > > > > > > Non-authoritative answer:
> > > > > > > Name:    ns1.netsol.com
> > > > > > > Address:  216.168.224.200
> > > > > > >
> > > > > > > > server ns1.netsol.com
> > > > > > > Default Server:  ns1.netsol.com
> > > > > > > Address:  216.168.224.200
> > > > > > >
> > > > > > > > csocs.com
> > > > > > > Server:  ns1.netsol.com
> > > > > > > Address:  216.168.224.200
> > > > > > > *** Request to ns1.netsol.com timed-out
> > > > > > >
> > > > > > > > networksolutions.com
> > > > > > > Server:  ns1.netsol.com
> > > > > > > Address:  216.168.224.200
> > > > > > > *** Request to ns1.netsol.com timed-out
> > > > > > >
> > > > > > > This tells me there's evidently some sort of dns issue I guess.
> > > > > > >
> > > > > > > J.C. Frazier
> > > > > > >
> > > > > > > "Forrest W. Christian" wrote:
> > > > > > >
> > > > > > > > If you don't have TCP connectivity between you and them, there
> is
> > > > > > > > definately some sort of routing or filtering issue between
> point
> > > a
> > > > > and
> > > > > b.
> > > > > > > >
> > > > > > > > Would you be kind enough to (perhaps privately) send me the
> IP
> > > > > address
> > > > > of
> > > > > > > > the machine in question so I can see what it looks like
> > > routing-wise
> > > > > from
> > > > > > > > here (perhaps I can see something).
> > > > > > >
> > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > > > > > with "unsubscribe freebsd-isp" in the body of the message
> > > > > >
> > > > > >
> > > > > >
> > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > > > > with "unsubscribe freebsd-isp" in the body of the message
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > EnContacto.Net - InternetSalon.Org - CafeMania.Net
> > > > --
> > > >
> > >
> > >
> >
> > --
> > EnContacto.Net - InternetSalon.Org - CafeMania.Net
> > --
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-isp" in the body of the message
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-isp" in the body of the message
> 



-- 
EnContacto.Net - InternetSalon.Org - CafeMania.Net
--


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?979860665.3a677cb933ea8>