Best Practice for SD-WAN and rDNS

Solved
MrKKnick
Just browsing

Best Practice for SD-WAN and rDNS

We've recently started send email direct to the internet instead of going through a 3rd party gateway.  We have 2 MX250 in redundancy with 2 load-balanced internet circuits.  This equates to 4 public IP addresses.  I've got to complete the Reverse DNS entries to satisfy some remote email server spam requirements.  Do I need to add our email server HELO/EHLO response with all 4 of the rDNS entries?  Is there a better way of handling the SD-WAN environments with rDNS?  

1 Accepted Solution
alemabrahao
Kind of a big deal
Kind of a big deal

Hi @MrKKnick

 

I think the best option in your case is to configure the virtual IP.

 

https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair#Virtual...

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

View solution in original post

2 Replies 2
alemabrahao
Kind of a big deal
Kind of a big deal

Hi @MrKKnick

 

I think the best option in your case is to configure the virtual IP.

 

https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair#Virtual...

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

I missed a configuration on the WAN2 side for the virtual IP.  With it configured, now I only have to add 2 instead of 4 entries in the rDNS tables.  Thanks for the suggestion.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels