2
DNS CNAME failure in SM 17
Problem reported by Elazar Broad - 11/20/2018 at 2:40 PM
Resolved
I use a 3rd party gateway for outbound email, and they use CNAME records for load balancing. On a newly upgraded instance of v17(build 6897), I get the following error in my delivery log when attempting to send any outbound messages:

16:33:59.898 [94048] Error in getting recipient A records. Message: LookupA.Exception: Unable to cast object of type 'DnsClient.Protocol.CNameRecord' to type 'DnsClient.Protocol.AddressRecord'.

For the time being, I'm using an IP address instead of the host name in the Gateway configuration, however this is not a long solution.

Thanks,
 Elazar

5 Replies

Reply to Thread
0
Employee Replied
Employee Post
Elazar, I have added this to our bugs lists for further investigation by the dev. team.
0
Elazar Broad Replied
Thanks Robert! I've DM'd you some additional details.
1
Employee Replied
Employee Post Marked As Resolution
This issue should be resolved with the latest 6911 release of SM17.
0
Elazar Broad Replied
Hi Robert -
 I can confirm that it has been resolved in 6911. Thanks!
0
Jade D Replied
Great response times here from the ST team

Jade https://absolutehosting.co.za

Reply to Thread