Mail bouncing with "host or domain name not found"

[Chris Marriott]

All mail sent to either my "demon.co.uk" or my domain account (hosted by
demon) has started bouncing with:

Final-Recipient: rfc822; sa...@skymap.com
Original-Recipient: rfc822;sa...@skymap.com
Action: failed
Status: 5.4.4
Diagnostic-Code: X-Postfix; Host or domain name not found. Name service
error
for name=filter.maildefender type=A: Host not found

Anyone else seeing the same or is it only me?

Thanks,

Chris

[Bob Evans]

In article <nZqts.512886$lz1.1...@fx28.am4>, Chris Marriott
<ch...@nowhere.com> wrote

>All mail sent to either my "demon.co.uk" or my domain account (hosted
>by demon) has started bouncing

I am currently seeing bounces of mail to another demon subdomain (that
was accepting such mail earlier today).

Here we go again :(

--
Bob Evans

[Chris Marriott]

Seems to be OK again now.

This same problem occurred about a week ago. Server problems which result in
hard bounces with "host not found" are extremely serious. I'll raise a
strongly-worded complaint about it with Demon.

Chris

[Simon Turner]

On Wednesday, in article <nZqts.512886$lz1.1...@fx28.am4>

I saw the same thing on a message at 16:17, but another one at 16:46 got
through OK (and it had been OK at 12:35 as well). I see people are
reporting the same thing on the forums; from the description, it looks
like they have screwed something up in the MailDefender process.

Oh goody.

--
Simon Turner DoD #0461
si...@twoplaces.co.uk
Trust me -- I know what I'm doing! -- Sledge Hammer

[Richard_C]

Not just you, happened to me a few moments ago, but a test I sent
shortly after that was OK.

Bounce message (name changed)

Reporting-MTA: dns; mdfmta005.tbr.inty.net
X-Postfix-Queue-ID: 37708A672B5
X-Postfix-Sender: rfc822; h...@rjcresources.co.uk
Arrival-Date: Wed, 28 Nov 2012 16:30:33 +0000 (GMT)

Final-Recipient: rfc822; M...@MYDOMAIN.demon.co.uk
Original-Recipient: rfc822;M...@MYDOMAIN1.demon.co.uk

Action: failed
Status: 5.4.4
Diagnostic-Code: X-Postfix; Host or domain name not found. Name service
error
for name=filter.maildefender type=A: Host not found

And another thing,

Simultaneously, taking several goes to send via smtp.demon.co.uk, just
like it did on the 23rd or thereabouts. Went on 5th try.

And another nother thing,

Mail sent out via Demon to a perfectly valid address which I use daily
has just bounced back.


Looks like demon mail is screwed up again. Getting cross now.

[Andy]

In message <nZqts.512886$lz1.1...@fx28.am4>, Chris Marriott
<ch...@nowhere.com> wrote

I have just had a phone call from a friend complaining that emails to me
both direct and via-Gradwell are bouncing. Headers unclear. Will dig
deeper :(
--
Andy Taylor [Editor, Austrian Philatelic Society].
Visit <URL:http://www.austrianphilately.com>

[Neil Jackson]

Looking at the error-report, it would seem that the machine (or host)
'filter.maildefender' (which is presumably a local LAN-only hostname,
given that it has no TLD suffix of any kind) has somehow failed to
complete a DNS lookup for MYDOMAIN.demon.co.uk.

That would indicate that there was either a transient failure whereby
IntY were unable to reach their own DNS cache of Demon's domain-data
(please god they DO have their own local copy of Demon's DNS?) or they
were unable to reach Demon's authoritative DNS servers upon which to
look up your address.

Either way, it smacks of infrastructure weakness between IntY and Demon
at some level. At least with the old punt mail system, it (a) had access
to its own copy of the Demon DNS zone data at its fingertips (and
several backup servers), all 'on the local net' so to speak and (b)
didn't have to reach out across the dirty big internet to talk to the
DNS servers to query local mailbox and domain info, and (c) would simply
hang on a lot longer until it got a valid DNS result for a local user,
before giving up with a hard-failure error.

MS's own Exchange blurb says this about a 5.4.4 extended SMTP error (at
http://support.microsoft.com/kb/284204 )

===QUOTE===
Numeric Code: 5.4.4

First Available: Exchange 2000 Service Pack 1

Possible Cause: No route to message, next hop not found. You have set up
a Routing Group topology, but there is no Routing Group Connector set up
between the Routing Groups.

Troubleshooting: Add or configure your Routing Group Connector between
Routing Groups.
===ENDQUOTE===

IMHO, it's a self-inflicted loss of DNS, by virtue of them having borked
their Exchange/MSSMTP routing config. Are they really up to handling an
entire ISP's primary mailstore, if this kind of fubar can happen? Even
temporarily?
--
Neil

[Richard]

I put a posting on the Demon email forum - seemed to come back about
4.30 but the only response was "Engineers are looking into it". Problem
is of course its unlikely we'll know how much incoming email was rejected.