> > That is mostly how I thought it worked. What I had in mind more
> > specifically was:
> >
> > adi.com zone:
> > mackerel.adi.com. IN A 75.100.245.141
> > mackerel.adi.com. IN A 96.85.104.76
> >
> > reverse zones:
> > 141.245.100.75.in-addr.arpa. IN PTR mackerel.adi.com
> > 76.104.85.
> That is mostly how I thought it worked. What I had in mind more
> specifically was:
>
> adi.com zone:
> mackerel.adi.com. IN A 75.100.245.141
> mackerel.adi.com. IN A 96.85.104.76
>
> reverse zones:
> 141.245.100.75.in-addr.arpa. IN PTR mackerel.adi.com
> 76.104.85.96.in-addr.arpa.
> Tom, when your mail server establishes a connection to another host, the
> receiving host will likely automatically check the PTR record of the IP
> address your server used as it's source address. This PTR record should
> have a corresponding A record that points to the same IP address that
On 18/03/16 14:52, /dev/rob0 wrote:
On Fri, Mar 18, 2016 at 10:04:05AM -0400, Thomas Schulz wrote:
I turns out that it is harder than I thought to allow incomming
connections from both providers at the same time, so I may not do
that after all.
Multiple route tables (and rules to choose the ap
Which FQDN does your mail server use for its EHLO? It should use the
same name that's listed in reverse DNS.
John
On Thu, Mar 17, 2016 at 9:53 AM, Thomas Schulz wrote:
> This is not a BIND question but I hope people here will know the answer.
> We are switching service providers and I understan
Tom, when your mail server establishes a connection to another host, the
receiving host will likely automatically check the PTR record of the IP
address your server used as it's source address. This PTR record should
have a corresponding A record that points to the same IP address that
was look
On 17.03.16 09:53, Thomas Schulz wrote:
This is not a BIND question but I hope people here will know the answer.
We are switching service providers and I understand that many email SPAM
prevention systems insist on the reverse DNS matching the forward DNS.
If I have two A records for our mail ser
> Am 17.03.2016 um 14:53 schrieb Thomas Schulz:
>> This is not a BIND question but I hope people here will know the answer
>> We are switching service providers and I understand that many email
>> SPAM prevention systems insist on the reverse DNS matching the forward
>> DNS. If I have two A records
In article ,
sch...@adi.com (Thomas Schulz) wrote:
> This is not a BIND question but I hope people here will know the answer.
> We are switching service providers and I understand that many email SPAM
> prevention systems insist on the reverse DNS matching the forward DNS.
> If I have two A recor
Am 17.03.2016 um 14:53 schrieb Thomas Schulz:
This is not a BIND question but I hope people here will know the answer.
We are switching service providers and I understand that many email SPAM
prevention systems insist on the reverse DNS matching the forward DNS.
If I have two A records for our
Thomas Schulz wrote:
> We are switching service providers and I understand that many email SPAM
> prevention systems insist on the reverse DNS matching the forward DNS.
> If I have two A records for our mail server and the reverse record matches
> one of them, will that be good enough. Or will th
On Fri, Mar 18, 2016 at 10:04:05AM -0400, Thomas Schulz wrote:
> I turns out that it is harder than I thought to allow incomming
> connections from both providers at the same time, so I may not do
> that after all.
Multiple route tables (and rules to choose the appropriate table) are
fairly easy
12 matches
Mail list logo
