Author Topic: VM issue xfer controller to controller  (Read 1318 times)

Offline dan231

  • Sr. Member
  • ****
  • Posts: 338
  • Country: us
  • Karma: +0/-0
    • View Profile
VM issue xfer controller to controller
« on: October 17, 2018, 03:05:11 PM »
First, I have no idea how this was working to begin with, but now this is broken.
All I did was replace an on-prem email spam filter, with a cloud based server.

My vm xfer to other branches no longer works.  I was told to 'simply' create DNS entries for the controllers on my internal DNS.  I can not do this as the "PTR record cannot be created, probably because the reference reverse lookup zone cannot be found"

Should I manually create the reverse lookup zone on my DNS?


Offline dan231

  • Sr. Member
  • ****
  • Posts: 338
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: VM issue xfer controller to controller
« Reply #1 on: October 17, 2018, 03:26:05 PM »
What about adding an INTERNAL RELAY in my exchange server?
Would this work?


Mitel 5000
« Last Edit: October 17, 2018, 05:18:36 PM by dan231 »

Offline dan231

  • Sr. Member
  • ****
  • Posts: 338
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: VM issue xfer controller to controller
« Reply #2 on: October 18, 2018, 03:52:11 PM »
1 piece eliminated:

On the OLD on-prem spam filter, there was a “Do not use MX Records”
This setting IS NOT a setting on the cloud ESS product.

Offline dan231

  • Sr. Member
  • ****
  • Posts: 338
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: VM issue xfer controller to controller
« Reply #3 on: November 09, 2018, 02:20:39 PM »
Just checking to see if anyone knew how to set this up properly? 


 

Sitemap 1 2 3 4 5 6 7 8 9 10