Hosting question

[Johny]

Hi all

I have a problem with my hosting

I have the name regisyered through 1 company and I have changed the
nameservers so it points to my hosting company and the site works fine but
my emails don't.

I have contacted the hosting company and they have replied with the
following:-

The problem with xxxxxxxx.com is little more tricky. Those mails are
being rejected (you should get bounce messages). That's because the domain
is only on our nameservers and not actually under our control. This means
the mail server needs to do a DNS lookup to check whether it's supposed to
deliver locally or relay. It's currently seeing the old DNS so it thinks it
has to relay, but isn't allowed so it rejects. That problem should fix
itself when the cached DNS records expire.


Whats it mean and what should I do to rectify the problem?

Thanks
J

 

[Tom Pepper Willett]

It means you must be patient and wait until the old cached DNS records
expire across all the routers in cyberspace.

--
===
Tom "Pepper" Willett
Microsoft MVP - FrontPage
---
About FrontPage 2003:
http://office.microsoft.com/home/office.aspx?assetid=FX01085802
FrontPage 2003 Product Information:
http://www.microsoft.com/office/frontpage/prodinfo/default.mspx
Understanding FrontPage:
http://msdn.microsoft.com/office/understanding/frontpage/
===
| Hi all
|
| I have a problem with my hosting
|
| I have the name regisyered through 1 company and I have changed the
| nameservers so it points to my hosting company and the site works fine but
| my emails don't.
|
| I have contacted the hosting company and they have replied with the
| following:-
|
| The problem with xxxxxxxx.com is little more tricky. Those mails are
| being rejected (you should get bounce messages). That's because the domain
| is only on our nameservers and not actually under our control. This means
| the mail server needs to do a DNS lookup to check whether it's supposed to
| deliver locally or relay. It's currently seeing the old DNS so it thinks
it
| has to relay, but isn't allowed so it rejects. That problem should fix
| itself when the cached DNS records expire.
|
|
| Whats it mean and what should I do to rectify the problem?
|
| Thanks
| J
|
|

 

[Tom J]

And when I moved one 2 years ago, it took about 3 weeks to clear all
the hurdles.

I have since moved the domain registration to the company that
supplies the servers to avoid some of those conflicts.

Tom J

 

[Chris Leeds, MVP-FrontPage]

The DNS should never take more than a couple of days to resolve.

--
Chris Leeds,
Microsoft MVP-FrontPage

ContentSeed: great tool for web masters,
a fantastic convenience for site owners.
http://contentseed.com/
--

 

[Tom J]

The DNS should never take more than a couple of days to resolve.

I agree, but if you have Network Solutions involved in the transfer,
anything that can go wrong will, or it did for me on 2 different
transfers. I'll never have web pages with a different provider than
the hosting company ever again.

On the other hand I just did an add-on domain with my current provider
and It propagated in less than a hour and was listed by google within
2 days.

Tom J

 

[Chris Leeds, MVP-FrontPage]

Network Solutions....
I feel your pain.

I've had a reseller account with Wild West domains (part of godaddy) set up
for a few years. I think I pay around $100/yr for it but it's well worth
the fee because I can usually recoup it even with the domains set at $9.95
each.
Plus it makes it a lot easier when clients need their DNS settings changed
and whatnot.

--
Chris Leeds,
Microsoft MVP-FrontPage

ContentSeed: great tool for web masters,
a fantastic convenience for site owners.
http://contentseed.com/
--