Richard G
Verified User
We have a customer which had his site with us.
A couple of years ago he moved his site to another host but wanted to keep the mail with us.
We had to change the nameservers at the registrar to the nameservers of this other host because of the use of some website builder on their subdomain.
Now this worked good for several years, but since a short while we get their mail back with this notice:
Which is odd, because from another server:
An nslookup to mail.userdomain.nl also gives the correct ip address.
When I try to send mail from another ISP or another server, there are no issues.
So it looks like the problem only occurs on mails send from the server where the domain is residing.
Nameservers are pointing to my own nameservers. Do they need to point locally to the other hosters nameservers too?
We did not do this before so it's odd this problem suddenly occurs.
Any help or insight is appreciated.
A couple of years ago he moved his site to another host but wanted to keep the mail with us.
We had to change the nameservers at the registrar to the nameservers of this other host because of the use of some website builder on their subdomain.
Now this worked good for several years, but since a short while we get their mail back with this notice:
all relevant MX records point to non-existent hosts
Which is odd, because from another server:
Code:
dig +short mx userdomain.nl
10 mail.userdomain.nl.
An nslookup to mail.userdomain.nl also gives the correct ip address.
When I try to send mail from another ISP or another server, there are no issues.
So it looks like the problem only occurs on mails send from the server where the domain is residing.
Nameservers are pointing to my own nameservers. Do they need to point locally to the other hosters nameservers too?
We did not do this before so it's odd this problem suddenly occurs.
Any help or insight is appreciated.