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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
