Our Domain name is host by other supplier and they host our website.
They point the mx record to our mail server with fix ip.
We only need to use their DNS by only fill in our mail server.
Should I need to setup a DNS server and domainkey by following the
instruction of Qmailtoaster?
Ho wrote:
Our Domain name is host by other supplier and they host our website.
They point the mx record to our mail server with fix ip.
We only need to use their DNS by only fill in our mail server.
Should I need to setup a DNS server and domainkey by following the
instruction of
Jake Vickers wrote:
You have to set up at least a caching name server on your mail server to
run the new version.
Why? This is important to me because I use toaster on machines that run
mydns, which only serves as a primary source nameserver and does not
return records for other domains. Is
Warren (mailing lists) wrote:
Jake Vickers wrote:
You have to set up at least a caching name server on your mail server to
run the new version.
Why? This is important to me because I use toaster on machines that run
mydns, which only serves as a primary source
Jake Vickers wrote:
The domainkeys function requires at least a caching DNS server on the
mail server itself to help speed up the requests. I believe (someone
correct me if I'm wrong) this is for answering requests by other
machines, not for local requests.
So then any requests made of this
Jake Vickers wrote:
Warren (mailing lists) wrote:
Jake Vickers wrote:
You have to set up at least a caching name server on your mail server to
run the new version.
Why? This is important to me because I use toaster on machines that run
mydns, which only serves as a primary source
Eric Shubes wrote:
I think we need Nick to chime in here with the definitive answer.
That being said, here's my (mis?)understanding.
Yes, you need a *caching* nameserver with the new version that supports
domain keys. This is so that the mail server isn't querying the
nameserver(s)
Warren (mailing lists) wrote:
Eric Shubes wrote:
I think we need Nick to chime in here with the definitive answer.
That being said, here's my (mis?)understanding.
Yes, you need a *caching* nameserver with the new version that supports
domain keys. This is so that the mail server isn't
I'm not Nick, but I'll chime in. You are correct.
On 7/28/06, Eric Shubes [EMAIL PROTECTED] wrote:
Jake Vickers wrote:
Warren (mailing lists) wrote:
Jake Vickers wrote:
You have to set up at least a caching name server on your mail server to
run the new version.
Why? This is important
But then if what you are saying is true, then a caching name server is
not *needed* but is a good thing to have to stop inefficiencies. Again,
I say this because I have setups that only have an authoritative name
server on them and the caching name server is the machine immediately
below it in
10 matches
Mail list logo
