Link to home
Start Free TrialLog in
Avatar of joshgeake
joshgeake

asked on

Do I have DNS set to find the correct mailbox server?

We have signed up to fasthosts to have several simple mailboxes hosted. Fasthosts don't manage the domain so we've had another company change the DNS settings so the MX record points to Fasthosts. The domain is rosienieper.co.uk

If I look at the DNS records for rosienieper.co.uk then it states the following...

;; QUESTION SECTION:
;rosienieper.co.uk. IN MX

;; ANSWER SECTION:
rosienieper.co.uk. 86400 IN MX 10 mail.rosienieper.co.uk.

;; ADDITIONAL SECTION:
ns59.1and1.co.uk. 9339 IN A 195.20.224.84
ns60.1and1.co.uk. 9339 IN A 212.227.123.78

Hence the MX record points to mail.rosienieper.co.uk. So now looking at mail.rosienieper.co.uk...

;; QUESTION SECTION:
;mail.rosienieper.co.uk. IN MX

;; ANSWER SECTION:
mail.rosienieper.co.uk. 73359 IN MX 10 smtpin.livemail.co.uk.

;; AUTHORITY SECTION:
rosienieper.co.uk. 159758 IN NS ns60.1and1.co.uk.
rosienieper.co.uk. 159758 IN NS ns59.1and1.co.uk.

;; ADDITIONAL SECTION:
smtpin.livemail.co.uk. 57558 IN A 213.171.216.65
ns59.1and1.co.uk. 9192 IN A 195.20.224.84
ns60.1and1.co.uk. 9192 IN A 212.227.123.78

So mail.rosienieper.co.uk points to smtpin.livemail.co.uk which in turn points to the correct ip - 213.171.216.65.

However - Emails to this domain bounce back and when I ping mail.rosienieper.co.uk (expecting to get 213.171.216.65) I actually go to the A record for rosienieper.co.uk (212.227.92.65). Why does this happen and how can I fix it?
Avatar of btassure
btassure
Flag of United Kingdom of Great Britain and Northern Ireland image

It seems to resolve OK from here:
Pinging mail.rosienieper.co.uk [213.171.216.65] with 32 bytes of data:

I tried to telnet to mail.rosienieper.co.uk on port 25 and it would not connect. Are you sure that the IP you have specified for that A record is correct for the fasthosts mail server?
Non-authoritative answer:
rosienieper.co.uk       internet address = 212.227.92.65
rosienieper.co.uk       nameserver = ns60.1and1.co.uk
rosienieper.co.uk       nameserver = ns59.1and1.co.uk
rosienieper.co.uk
        primary name server = ns59.1and1.co.uk
        responsible mail addr = hostmaster.1and1.co.uk
        serial  = 2008102006
        refresh = 28800 (8 hours)
        retry   = 7200 (2 hours)
        expire  = 604800 (7 days)
        default TTL = 86400 (1 day)
rosienieper.co.uk       MX preference = 10, mail exchanger = mail.rosienieper.co.uk
 
ns60.1and1.co.uk        internet address = 212.227.123.78
ns59.1and1.co.uk        internet address = 195.20.224.84
mail.rosienieper.co.uk  internet address = 213.171.216.65

Open in new window

Avatar of jar3817
jar3817

Looks good from here too.
Avatar of joshgeake

ASKER

looks like it's pinging ok from here too but here's the kb from fasthosts...

http://www.fasthosts.co.uk/knowledge-base/?article_id=603
The setup is correct. What is the error code in the non-delivery reports you get when you send to one of these addresses?

It sounds like the fasthosts just haven't setup the users or accounts yet on their end.
This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

    tony@rosienieper.co.uk

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 554 554 <tony@rosienieper.co.uk>: Relay access denied (state 14).
yup, fasthosts hasn't setup that server to accept mail either for that domain or specifically for that user. Call them and ask them to fix it.
Called them and they've said the mx record should go to smtpin1.livemail.co.uk (213.171.216.1) which is contrary to all their other information. However, even if I telnet directly to that address it can't verify the users.
Relaying in is denied to that address... Again, it's a fasthosts problem.
god they're ****ers
Same thing:

220 smtp-in-77.livemail.co.uk ESMTP Postfix
EHLO harleyschool.org
250-smtp-in-77.livemail.co.uk
250-PIPELINING
250-SIZE 31457280
250-VRFY
250-ETRN
250 8BITMIME
MAIL FROM: ***@********
250 Ok
RCPT TO: ****@rosienieper.co.uk
554 <****@rosienieper.co.uk>: Relay access denied
quit
221 Bye
Yup. I am not a fan. I would rather crawl over broken glass for an Exchange licence than use them!
I've had the DNS settings changed to EXACTLY what they wanted. I'll wait until this time tomorrow before calling them and asking why the same damn thing is happening. Watch this space.
DNS seems to be replicating with other ISPs pretty quickly. My money is on them not having the service provision available for new mailboxes yet and they are scrambling to get it ready.
Dear Jogh,

Thank you for your enquiry.

The domain rosienieper.co.uk does not exist on our network for hosting.

The domain in your account is called blankdomain.com which is invalid.

It appears you need to remove blankdomain.com from the package first.

You should then get the domains registration transferred from the other account to this one before you can add hosting.  Alternatively, get the other account holder to delegate hosting so you can add it to the package you have here.

You have not created any email addresses that are valid as the domain is not hosted.

Currently the domain is not hosted by Fasthosts so you need to contact the other account holder or 1&1.

Hope this helps.
--

Nicholaus Darley-Jones
Customer Support
Fasthosts Internet Ltd.


What
A MORON!!! Of course it's not hosted with them, if he bothered checking their records they would see this.
Heh. Try another provider?
you mean one that can spell my name correctly?!
On the bright side I suppose it means that they aren't using a script to autogenerate that email. Or if they are it is so badly written that you are better off knowing about it now and shopping around :o)
What do people make of their reply?...

Thank you for your reply.

To help I have answered your points below:

Q1)  Firstly, I signed up for mailbox hosting - I don't want to transfer the domain to you.
A1)  You don't have to move the domains registration to your account.  But, the domain is already with a Fasthosts customer and they are pointing the domain away from us.  You would need to:
1)  Get them to change the name servers to Fasthosts name servers.
2)  Select the option to delegate hosting.
3)  Remove the blankdomain.com form the package.  (removes invalid email addresses)
4)  Add the correct domain to the pacakge.
5)  Create the mailboxes.


Q2)  Secondly, the sales person said that all I have to do is point the MX
records to smtpin.livemail.co.uk.
A2)  This will only work if the domain is hosted on the Fasthosts network.  As you have already worked out it isn't.  You would ahve to have hosting to do that and you can only add hosting if the other account delegates it.  Please follow steps 2 - 5.

Q3)  Thirdly, I've questioned the blankdomain.com account and your
representative stated that it's because the domain is hosted elsewhere,
it's just a default name for our kind of mailbox-only account.

A3)  It is a holding domain otherwise you would not be able to add a hosting package as it has to have a domain assigned to it even if it's not valid.

Q4)  Fourthly, I have created 6 mailboxes within our account.
A4)  They are useless.  You cannot use the mailboxes on your account as the domain is not valid.  They need to be created on the correct domain once hosting has been added to it.

Q5)  Could someone competant please offer some helpful support?
A5)  This is up to you.  You first need to contact the other account holder because until you contact them you cannot host the domain they control.  Once they have delegated hosting we can then remove the blankdomain.com from the pacakge and add the other domain to it.  You would then need to login to create the mailboxes.

Hope this helps.

--

Nicholaus Darley-Jones
Customer Support
Fasthosts Internet Ltd.
ASKER CERTIFIED SOLUTION
Avatar of joshgeake
joshgeake

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Yeah, don't transfer the domain - that will cause you nightmares assuming they even do everything properly. They have had a lot of problems in the last year with deleting mailboxes, services offline etc. Google them. :o)