<div dir="ltr">It&#39;s the wildcard A record + wrongly configured DNS that resolves anything to *.<a href="http://conviator.com">conviator.com</a> which then fails.<div><br>Remove the &quot;search <a href="http://conviator.com">conviator.com</a>&quot; from /etc/resolv.conf or fix your wildcard DNS.</div>
</div> <div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div style="font-family:arial;font-size:small"><div><br><b>Alex Neuman van der Hans<br></b>Reliant Technologies / Vida Digital<br><a href="http://t.sigopn02.com/link?url=http%3A%2F%2Fvidadigital.com.pa%2F&amp;ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgKCUyroKDA&amp;k=e1d187e7-61d3-4f47-f588-00f93bb763ba" style="color:rgb(17,85,204)" target="_blank">http://vidadigital.com.pa/</a><br>
<br></div><div>Mobile: +507-6781-9505<br>Work: +507-832-6725<br>Work (USA): +1-440-253-9789</div><div>Skype: <a href="http://t.sigopn02.com/link?url=&amp;ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgKCUyroKDA&amp;k=bfa3daa4-f1d7-49ca-85e8-fcd28b94b87c">AlexNeuman</a></div>
<div><br>Don&#39;t miss <a href="http://t.sigopn02.com/link?url=http%3A%2F%2Fnew.livestream.com%2Faccounts%2F5061819&amp;ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgKCUyroKDA&amp;k=575065a1-7cbb-490f-97a1-ce09bbd26671" target="_blank">Vida Digital on LiveStream</a>!</div>
<div>Saturdays 8am-10am on 104.3FM Panama</div><div><br>Follow <b><a href="http://t.sigopn02.com/link?url=https%3A%2F%2Ftwitter.com%2Falexneuman&amp;ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgKCUyroKDA&amp;k=dcba2378-4808-4e8e-d1c8-505fae46ff68" style="color:rgb(17,85,204)" target="_blank">@AlexNeuman</a></b> on Twitter<br>
Like <a href="http://t.sigopn02.com/link?url=https%3A%2F%2Ffacebook.com%2Fvidadigital%2F&amp;ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgKCUyroKDA&amp;k=18d40ca5-10e0-4f1e-9893-aa673206b926" style="color:rgb(17,85,204)" target="_blank">Vida Digital</a> on Facebook</div>
</div><div style="font-family:arial;font-size:small">Follow <a href="http://t.sigopn02.com/link?url=http%3A%2F%2Finstagram.com%2Fvidadigital&amp;ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgKCUyroKDA&amp;k=7829149b-3bcb-4310-ce33-f6461c43e95f" style="color:rgb(17,85,204)" target="_blank">VidaDigital</a> on Instagram</div>
<div style="font-family:arial;font-size:small">Subscribe to <a href="http://t.sigopn02.com/link?url=https%3A%2F%2Fyoutube.com%2Freliantpty&amp;ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgKCUyroKDA&amp;k=96ad93eb-256e-4aac-e915-89f0846ee63e" style="color:rgb(17,85,204)" target="_blank">Vida Digital</a> on Youtube</div>
</div></div>
<br><br><div class="gmail_quote">On Tue, Sep 2, 2014 at 9:55 AM, Steve Freegard <span dir="ltr">&lt;<a href="mailto:steve.freegard@fsl.com" target="_blank">steve.freegard@fsl.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Can you provide a proper example of a domain that exhibits this<br>
behaviour?  Having a non-resolvable primary MX is pretty rare, so I&#39;d be<br>
pretty surprised to see this happening very often.<br>
<br>
I suspect it&#39;s likely caused by your wildcard A record on your domain:<br>
<br>
smf@i7-desktop:~$ host <a href="http://t.sigopn02.com/link?url=http%3A%2F%2Fsdlkfjsdklfjsdklfjsldf.conviator.com%2F&amp;ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgKCUyroKDA&amp;k=13e78ada-4673-4526-e177-6b05f4327235" target="_blank">sdlkfjsdklfjsdklfjsldf.conviator.com</a><br>

<a href="http://t.sigopn02.com/link?url=http%3A%2F%2Fsdlkfjsdklfjsdklfjsldf.conviator.com%2F&amp;ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgKCUyroKDA&amp;k=cbf7b718-6e2f-4a50-d4ac-a1d6e2c93f5d" target="_blank">sdlkfjsdklfjsdklfjsldf.conviator.com</a> has address <a href="tel:86.58.185.222" value="+18658185222">86.58.185.222</a><br>

<br>
And the interaction between that and your search path in resolv.conf.<br>
<br>
I bet if you type something like:<br>
<br>
ping sdklfjsdkljfskl.skdfjsdkjfs<br>
<br>
On that server - it will resolve to <a href="tel:86.58.185.222" value="+18658185222">86.58.185.222</a>.<br>
<br>
Regards,<br>
Steve.<br>
<div class="HOEnZb"><div class="h5"><br>
On 02/09/14 13:19, <a href="mailto:ja@conviator.com">ja@conviator.com</a> wrote:<br>
&gt; hi<br>
&gt; its a bit OT but I hope its OK anyway. We are also using Mailscanner as<br>
&gt; outbound scanner and see a problem that I cannot figure out - probably<br>
&gt; some setting im missing.<br>
&gt; sometimes &quot;we&quot; send emails to a domain where the primary MX record does<br>
&gt; not resolve. I would have expected that sendmail would just try the next<br>
&gt; but instead it resolves to <a href="http://t.sigopn02.com/link?url=http%3A%2F%2Fmxrecord.name.ourdomain.com%2F&amp;ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgKCUyroKDA&amp;k=2f3fbc41-7d8c-4880-df73-c12948711e5f" target="_blank">mxrecord.name.OURDOMAIN.COM</a> (I think) - it<br>

&gt; seams it appends our domain and then tries this server and this server<br>
&gt; says &quot;no thanks&quot; so the delivery fails.<br>
&gt; I tried to lookup the MX myself using the same nameserver as the<br>
&gt; mailscanner server is using - this fails so its not the DNS server that<br>
&gt; appends something to make it resolveable or gives out a standard IP.<br>
&gt; I also checked the resolve file to check that there is not search<br>
&gt; setting that would make it search our domain for a valid IP/lookup.<br>
&gt; how can I stop this behavior and make it try the next MX in line?<br>
&gt; best regards<br>
&gt; Jan<br>
&gt;<br>
&gt;<br>
<br>
<br>
</div></div><div class="HOEnZb"><div class="h5">--<br>
MailScanner mailing list<br>
<a href="mailto:mailscanner@lists.mailscanner.info">mailscanner@lists.mailscanner.info</a><br>
<a href="http://t.sigopn02.com/link?url=http%3A%2F%2Flists.mailscanner.info%2Fmailman%2Flistinfo%2Fmailscanner&amp;ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgKCUyroKDA&amp;k=effce33c-687b-4d32-ecc9-4ba02453d4cb" target="_blank">http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br>

<br>
Before posting, read <a href="http://t.sigopn02.com/link?url=http%3A%2F%2Fwiki.mailscanner.info%2Fposting&amp;ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgKCUyroKDA&amp;k=bac47b07-8e02-41d8-ebeb-0c6dad971052" target="_blank">http://wiki.mailscanner.info/posting</a><br>

<br>
Support MailScanner development - buy the book off the website!<br>
</div></div></blockquote></div><br><img src="http://t.sigopn02.com/img.gif?ukey=agxzfnNpZ25hbHNjcnhyGAsSC1VzZXJQcm9maWxlGICAgKCUyroKDA&amp;key=1cec0fe5-3424-4d22-c5ff-638e9a96dbc7" width="1" height="1" style="display:none"></div>
<div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div style="font-family:arial;font-size:small"><div><br><b>Alex Neuman van der Hans<br></b>Reliant Technologies / Vida Digital<br><a href="http://vidadigital.com.pa/" style="color:rgb(17,85,204)" target="_blank">http://vidadigital.com.pa/</a><br>
<br></div><div>Mobile: +507-6781-9505<br>Work: +507-832-6725<br>Work (USA): +1-440-253-9789</div><div>Skype: <a>AlexNeuman</a></div><div><br>Don&#39;t miss <a href="http://new.livestream.com/accounts/5061819" target="_blank">Vida Digital on LiveStream</a>!</div>
<div>Saturdays 8am-10am on 104.3FM Panama</div><div><br>Follow <b><a href="https://twitter.com/alexneuman" style="color:rgb(17,85,204)" target="_blank">@AlexNeuman</a></b> on Twitter<br>Like <a href="https://facebook.com/vidadigital/" style="color:rgb(17,85,204)" target="_blank">Vida Digital</a> on Facebook</div>
</div><div style="font-family:arial;font-size:small">Follow <a href="http://instagram.com/vidadigital" style="color:rgb(17,85,204)" target="_blank">VidaDigital</a> on Instagram</div><div style="font-family:arial;font-size:small">
Subscribe to <a href="https://youtube.com/reliantpty" style="color:rgb(17,85,204)" target="_blank">Vida Digital</a> on Youtube</div></div></div>
<br><br><div class="gmail_quote">On Tue, Sep 2, 2014 at 9:55 AM, Steve Freegard <span dir="ltr">&lt;<a href="mailto:steve.freegard@fsl.com" target="_blank">steve.freegard@fsl.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Can you provide a proper example of a domain that exhibits this<br>
behaviour?  Having a non-resolvable primary MX is pretty rare, so I&#39;d be<br>
pretty surprised to see this happening very often.<br>
<br>
I suspect it&#39;s likely caused by your wildcard A record on your domain:<br>
<br>
smf@i7-desktop:~$ host <a href="http://sdlkfjsdklfjsdklfjsldf.conviator.com" target="_blank">sdlkfjsdklfjsdklfjsldf.conviator.com</a><br>
<a href="http://sdlkfjsdklfjsdklfjsldf.conviator.com" target="_blank">sdlkfjsdklfjsdklfjsldf.conviator.com</a> has address <a href="tel:86.58.185.222" value="+18658185222">86.58.185.222</a><br>
<br>
And the interaction between that and your search path in resolv.conf.<br>
<br>
I bet if you type something like:<br>
<br>
ping sdklfjsdkljfskl.skdfjsdkjfs<br>
<br>
On that server - it will resolve to <a href="tel:86.58.185.222" value="+18658185222">86.58.185.222</a>.<br>
<br>
Regards,<br>
Steve.<br>
<div class="HOEnZb"><div class="h5"><br>
On 02/09/14 13:19, <a href="mailto:ja@conviator.com">ja@conviator.com</a> wrote:<br>
&gt; hi<br>
&gt; its a bit OT but I hope its OK anyway. We are also using Mailscanner as<br>
&gt; outbound scanner and see a problem that I cannot figure out - probably<br>
&gt; some setting im missing.<br>
&gt; sometimes &quot;we&quot; send emails to a domain where the primary MX record does<br>
&gt; not resolve. I would have expected that sendmail would just try the next<br>
&gt; but instead it resolves to <a href="http://mxrecord.name.OURDOMAIN.COM" target="_blank">mxrecord.name.OURDOMAIN.COM</a> (I think) - it<br>
&gt; seams it appends our domain and then tries this server and this server<br>
&gt; says &quot;no thanks&quot; so the delivery fails.<br>
&gt; I tried to lookup the MX myself using the same nameserver as the<br>
&gt; mailscanner server is using - this fails so its not the DNS server that<br>
&gt; appends something to make it resolveable or gives out a standard IP.<br>
&gt; I also checked the resolve file to check that there is not search<br>
&gt; setting that would make it search our domain for a valid IP/lookup.<br>
&gt; how can I stop this behavior and make it try the next MX in line?<br>
&gt; best regards<br>
&gt; Jan<br>
&gt;<br>
&gt;<br>
<br>
<br>
</div></div><div class="HOEnZb"><div class="h5">--<br>
MailScanner mailing list<br>
<a href="mailto:mailscanner@lists.mailscanner.info">mailscanner@lists.mailscanner.info</a><br>
<a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner" target="_blank">http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br>
<br>
Before posting, read <a href="http://wiki.mailscanner.info/posting" target="_blank">http://wiki.mailscanner.info/posting</a><br>
<br>
Support MailScanner development - buy the book off the website!<br>
</div></div></blockquote></div><br></div>