Re: [cobalt-developers] bind - named.conf error

["Gerald Waugh" <gerald@xxxxxxxxx>]

"Kal Amry" <kamry1888@xxxxxxxxx> wrote
> Gerald do you have the problem of not being able to do a reverse look up on
> the Raq 4. Is it an ISP problem or Cobalt. I'm not running the DNS as you
> know, and I was using our ISPs dns, but today it wasn't functioning and I
> had to use US WEST DNS without their knowledge just to be able to use e-mail
> services.
>
> Whenever an e-mail is received, the cobalt tries to do a reverse lookup when
> it shouldn't. Thus, if an e-mail comes from yahoo.com then I won't be able
> to get it 'cause the Cobalt tries to do a reverse lookup on yahoo, and since
> the original dns of our ISP doesn't look to the outside world from the
> inside (Where our Server Resides), we can't get an e-mail. I heard that the
> Raq 3 doesn't behave in this way and it is Only the Raq 4 and no one knew
> why is it doing a reverse lookup upon getting an e-mail????

Hi Kal,
I really don't know, I am having some problems with my RaQ4's pop-before-relay
but they receive mail just fine. How were you using US WEST to rectify the
issue?
If your ISP's name Severs (which are really your Name Servers) were down,
you could certainly have problems receiving mail. Does US WEST have a zone file
and or MX records for your domains?

The problem I have with the RaQ reverse getting screwed up only affects us when
we
try to send mail using an offsite mail host, as our mail host performs
pop-before-relay
(that's another issue) also and if they can't readily perform a reverse
(checking name-ip)
you have to wait for timeouts on both primary and secondary (takes a long time)
but works
Wish I could be of more help and still curious about how ES WEST helped.
Gerald