james-server-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "JWM" <techst...@malcolms.com>
Subject Epilog: James started not being able to find any external host
Date Thu, 04 May 2006 19:36:11 GMT
OK, I finally figured out what the problem was.  But it was not a reboot
issue.  It was indeed the addition of the "recursion no;" clause in my
named.conf file.

As it turns out, I had hardcoded the dns entries in my James conf file and
had my local host IP first.  Apparently before I added the recursion clause,
my DNS server would forward the request upstream if it did not find the name
in question.  When I set "recursion no;", my DNS server stopped forwarding
the request for names it didn't have configured, meaning that the only
domain names the dns server would resolve are domains I am hosting.  When
James was told to use that DNS server, no external domain names were being
resolved.

So the fix was to remove my local DNS IP address from the James DNS server
list.

Thanks again, Stefano, for all of your assistance.  Not a way in the world I
would have figured this out without your pointers.

Jerry

-----Original Message-----
From: Stefano Bagnara [mailto:apache@bago.org] 
Sent: Thursday, May 04, 2006 12:57 PM
To: James Users List
Subject: Re: James started not being able to find any external host

I don't know what "recursion no" does.

I just know that james discover DNS servers at startup so you have to 
restart james if you change the dns servers.

If you simply change the dns behaviours (and not their IPs) James uses 
the correct time-to-live for the expiration of the dns records.

Stefano

JWM wrote:
> OK, We're getting to the bottom of this.... I am running a DNS server on
my
> box for my hosted domains.  James has my local DNS first in the chain,
> followed by my two upstream DNSs, which points me to the following clue:
> 
> I ran DNSReport.com a couple of days ago on one of my domains and got an
> error saying I needed to add "recursion no" to my DNS server config to
> prevent some sort of spoofing (DNS theory is not my forte...).  I added
that
> and bounced the DNS server a day or so ago.  This morning in desperation
to
> recover from the email catastrophe, I removed that line.
> 
> Now, not having a clue what that recursion thing really does, my question
is
> this: Was it the fact the recursion option line was added to my DNS config
> that caused my problem?  Or was it simply that for some reason I was
> required to restart James after bouncing the DNS server that caused the
> problem.  In other words, is it safe to add that "recursion no" and just
> bounce James when I bounce the DNS server?  Or is that line in the DNS
> config going to cause problems with James, no matter what?
> 
> I really appreciate your help on this.
> 
> Jerry


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Mime
View raw message