can you help with why my own website email is failing?

[CoolHands]

I have my own website I use for a few minor things, inc use of the emails which I get gmail to pick up. But it seems to have failed lately. The website still works, and I can log on through my cpanel to look at email and even send one to my gmail, but if I send an email to my website email (any of the email addresses I have) it fails. In gmail it has this if I look at complete header etc. Can anyone makes sense of it? (I've changed my gmail address to xxxx in this post to stop spam):



Delivered-To: [e-mail]
Received: by 10.112.207.103 with SMTP id lv7csp872738lbc;
Fri, 3 Jul 2015 00:23:05 -0700 (PDT)
X-Received: by 10.50.225.40 with SMTP id rh8mr20425940igc.39.1435908184909;
Fri, 03 Jul 2015 00:23:04 -0700 (PDT)
Return-Path: <>
Received: from mail-la0-f70.google.com (mail-la0-f70.google.com. [209.85.215.70])
by mx.google.com with ESMTPS id p65si2918646iop.13.2015.07.03.00.23.04
for <[e-mail]>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 03 Jul 2015 00:23:04 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of mail-la0-f70.google.com designates 209.85.215.70 as permitted sender) client-ip=209.85.215.70;
Authentication-Results: mx.google.com;
spf=pass (google.com: best guess record for domain of mail-la0-f70.google.com designates 209.85.215.70 as permitted sender) smtp.mail=;
dkim=pass header.i=@googlemail.com;
dmarc=pass (p=QUARANTINE dis=NONE) header.from=googlemail.com
Received: by mail-la0-f70.google.com with SMTP id x9so14022409lag.2
for <[e-mail]>; Fri, 03 Jul 2015 00:23:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlemail.com; s=20120113;
h=mime-version:from:to:subject:message-id:date:content-type;
bh=j3kMmXHodqw5dNqzMQnONZ0i7bMxXYWQivcpPdsOPrw=;
b=gWH4XhkJlwZbCo2SSY6BDFqKdMcB9V5VCKnLFZKHOG/vLDkxVuPx4ilmRpKrY/SVRj
yIi1uGr2jjyC7eNKVgrZpcZp+J0pdkfAjY9o5iuEBRLfRnjcHOExkwrIZEb+rWTm5a9L
HFnqo7gWoCJ61OepJQfwtW5s0UOlkaCGZSro4SLm7l2eDVsMvedDVRIGbiVxx5tMDHL8
ZIj8WFepfnZhJgS/Mqz4X4ph4auggJMaReSu/ONm2KKexfzrXTk0p8F/y8VSde49Ecif
c5sqD+/y5EgMP5F5aYSf7+ctRr3rgJVwp+YDNaUMbCFmAS+RKk+d77Ngd8Xf+TzPau8N
ZbIw==
X-Received: by 10.152.43.134 with SMTP id w6mr31303896lal.120.1435908183976;
Fri, 03 Jul 2015 00:23:03 -0700 (PDT)
MIME-Version: 1.0
Return-Path: <>
Received: by 10.152.43.134 with SMTP id w6mr14877728lal.120; Fri, 03 Jul 2015
00:23:03 -0700 (PDT)
From: Mail Delivery Subsystem <[e-mail]>
To: [e-mail]
Subject: Delivery Status Notification (Delay)
Message-ID: <[e-mail]>
Date: Fri, 03 Jul 2015 07:23:03 +0000
Content-Type: text/plain; charset=UTF-8

This is an automatically generated Delivery Status Notification

THIS IS A WARNING MESSAGE ONLY.

YOU DO NOT NEED TO RESEND YOUR MESSAGE.

Delivery to the following recipient has been delayed:

[e-mail]

Message will be retried for 1 more day(s)

Technical details of temporary failure:
DNS Error: MX lookup of chilliwack.co.uk returned error DNS server returned general failure

---

Original message -----

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:date:message-id:subject:from:to:content-type;
bh=XICl5Qn8f4NvOEXzDKN1DdevXWNBggAG1VSwg6W1k6U=;
b=cJd1I9ol49kZZKOlch6S75aELo/qHQ5mNgMqicr8TDITd3WpuQqao3MdD3ROaZ2K/9
3gErOS2lDyXHG4JiXJiY3KhsH/uBXPgD62X5ylF8jgBeCiWoCGRQ8LT2/oigRkgDCMgJ
npA/vGdg7Yl1+APkiDJjPUE0kDVLp5z6HBTDIpv2ww7Q7D+RxwLqtAOvwUJjac8tCRnc
QomLoB9WzdajPbOdrf/ueqciWovt0vMDd6ED7BnuApeo22AhysmASxZluKPpVvyhrjRC
afL84qP63PsCbl/cDrlGnq1PnIB6IeVU5Uiwu6U6RO6YEpB4sD3Cw+nomujJlhKMNNRa
6g9g==
MIME-Version: 1.0
X-Received: by 10.152.43.134 with SMTP id w6mr21346537lal.120.1435733160843;
Tue, 30 Jun 2015 23:46:00 -0700 (PDT)
Received: by 10.112.164.71 with HTTP; Tue, 30 Jun 2015 23:46:00 -0700 (PDT)
Date: Wed, 1 Jul 2015 07:46:00 +0100
Message-ID: <CAPtJajVX2zQSbZhr3EGmXQznKRCdwnD7XG8-N=[e-mail]>
Subject: test
From: xx <[e-mail]>
To: [e-mail]
Content-Type: multipart/alternative; boundary=001a11c1a8080b628f0519caad5e

test

[buggalugs]

The name server settings on your domain are incorrect, or your host's (justhostme.net) nameservers are down.

There are different name servers listed for justhostme than the ones you have got set on your domain, but those nameservers still don't have any MX records for your domain.

Phone call to them in the morning.

Edited by buggalugs on Sunday 5th July 21:20

[marshalla]

Your domain isn't returning anything on a DNS lookup and justhostme.net' s name servers are not responding. They need to sort it out (and you probably need to move to a better hosting company).

[bitchstewie]

^^

This, something with your host is fked.

[CoolHands]

ah.

thanks

(annoying as of course I recently renewed my m/bike insurance using that email address! No docs received!)

BTW I don't understand any of this stuff. Is one of these settings anything I can change? ie I'm trying to make sure it's not something I should be entering differently is it? I remember entering nameserver stuff on gmail to get it working before.

[buggalugs]

No, you need to call justhostme to get it resolved.

[CoolHands]

thanks, you were right. Bit of a lame response though - no indication of how long its been like that! Who knows how many important emails I've missed! That's half the point of having my own reliable email - gits . No apology either.

",

I have corrected the name servers of your domain. Your email issue should now be resolved.

If you have any further questions please do not hesitate to contact us."

[bitchstewie]

Honestly this is why if you need reliable email it's usually simpler to just use Gmail or 365 - they're not without fault but offer a lot more flexibility and enterprise features than the stuff you get with a basic we bhosting package.

[buggalugs]

Senders would have got a bounce message so at least they will know that their mail didn't get through.

Whois was showing your domain last updated in 2013 before today's changes, so it's something that's changed re. justhostme's nameservers rather than a setting you've messed with. i.e. they messed things up. They probably re-arranged some of their back end without properly checking who was using what.