ok
i replyed back on another post but thanbks for at least replying
i think i will let everyone else figure this out
you are right i was running on experience without any logging info
the origional post indicated that mx records were not being returned?
when i did a dig on my dns system and google's both replied with valid
dns results.
fyi
Happy Tuesday !!!
Thanks - paul
Paul Kudla
Scom.ca Internet Services <http://www.scom.ca>
004-1009 Byron Street South
Whitby, Ontario - Canada
L1N 4S3
Toronto 416.642.7266
Main 1.866.411.7266
Fax 1.888.892.7266
Email p...@scom.ca
On 11/1/2022 10:50 AM, Viktor Dukhovni wrote:
On Tue, Nov 01, 2022 at 10:30:50AM -0400, Paul Kudla wrote:
> The OP, please ignore advice (such as the below) from eager but
> uninformed list contributors.
if i can please get an explanition on what triggered this comment then
please advise - ie regarding unbound (i presume)
Essentially everything in that post was simply wrong. Sorry about that.
A local DNS resolver is recommended on an MTA. Unbound is a perfectly
fine choice of resolver. The OP's issue may not even be DNS. If
messages are being *rejected*, then DNS resolution of the remote MX
hosts is working. Perhaps the OP's own domain is not reliably resolved
by the receiving systems, but that's got nothing to do with the choice
of resolver on the sending side.
As already noted, the OP needs to follow the advice in DEBUG_README,
and post logs related to the problem and configuration information.
