Nope, I'm suggesting he keep the old PTR on the original IP and add a
new PTR for the new IP.
--Ed
On 09/21/2013 04:46 AM, Chris Ferebee wrote:
> Ed,
>
> Are you suggesting David should use multiple reverse-DNS PTR records on his new IP address, i. e., the previous one and the new one? That's certainly possible (if the colo provider supports it, which many don't), but I question whether it's a good idea, as it could trigger spam detection in receiving SMTP hosts that don't check more than one PTR record.
>
> Best,
> Chris
>
> Am 20.09.2013 um 23:48 schrieb Ed HIDDEN@ent.net>:
>
>> I would say in regards #2, ADD another PTR for the new IP, keep your existing one as well.
>>
>> --Ed
>>
>> On 09/20/2013 05:06 PM, David Camm wrote:
>>> chris also wrote about using g_bind_out.
>>>
>>> my dns currently has this:
>>>
>>> mail IN A 1.2.3.4
>>>
>>> and customer dns's have
>>>
>>> MX 10 mail.advwebsys.com
>>>
>>> if i were to add 5.6.7.8 into the network config and then do g_bind_out
>>> '5.6.7.8'
>>>
>>> someone sending TO us would still see 1.2.3.4
>>>
>>> someone receiving FROM us would see 5.6.7.8 as source ip and therefore
>>> i'd need to change the ptr record (maintained by my colo provider to
>>> 5.6.7.8). i should not, i think, change 1.2.3.4 to 5.6.7.8 in my dns.
>>>
>>> so i think your solution (ed) is correct in that i need to:
>>>
>>> 1. add the additional ip address
>>> 2. change the ptr to point to it
>>> 3. set g_bind_out to the new ip address
>>>
>>> since bind_out will force writing on the new ip, i don't think the
>>> gateway statement is necessary.
>>>
>>> thoughts????
>>>
>>> david camm
>>> advanced web systems
>>> keller, tx
>>>
>>>
>>>
>>>
>>>
>>> On 9/20/2013 2:08 PM, Ed wrote:
>>>> There's a couple different and easy ways to do this :
>>>>
>>>> Just add the new IP to the server. Add a g_gateway entry for all
>>>> email and bind that to the new IP. Then all you need is to add to
>>>> your DNS an A and PTR record for the new IP. MX and everything else
>>>> stays the same. All you're trying to do is get surge to use a
>>>> different IP to send with.
>>>>
>>>> Optionally you can set g_bind_out to get surge to "send" on the new
>>>> IP. You still need the new DNS entries. This is the way we do it
>>>> with multi-homed servers behind load balancing. g_bind_out can take a
>>>> comma separated list and both ip4 and ip6.
>>>>
>>>> Food for thought ?
>>>>
>>>> --Ed
>>>>
>>>> On 09/20/2013 02:59 PM, David Camm wrote:
>>>>> thanks for the suggestions, but neither gatewaying to another server nor
>>>>> changing the ip is viable for me.
>>>>>
>>>>> a) i don't have another server to gateway TO and
>>>>>
>>>>> b) the server is multi-homed already. just adding another ip will not
>>>>> get surge to use it. i'd have to reconfigure networking, change the dns
>>>>> that points to the server AND get my colo facility to change their
>>>>> reverse dns entry.
>>>>>
>>>>> david camm
>>>>> advanced web systems
>>>>> keller, tx
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
>> --
>> -----------------------------------------------------------
>> EAS Enterprises LLC
>> World Class Web and Email Hosting Solutions
>> IPv6 ready today for your needs of tomorrow!
>> Ask us about dual-stacking your site
>> www.easent.net
>>
>
>
>
--
-----------------------------------------------------------
EAS Enterprises LLC
World Class Web and Email Hosting Solutions
IPv6 ready today for your needs of tomorrow!
Ask us about dual-stacking your site
www.easent.net
|
