|
I have been using Custom DNS services for a couple of domains for a while now and I have been very pleased with the service. For one of my domain names I am using a third party hosting company to host our web site. I am using a separate company to provide e-mail archiving and the e-mails are then routed to my internal exchange server. So my A record is pointing to the company hosting my web site and the my MX list is pointing to a different company. This has been working fine. The A-record is pointing to a specific IP address. The web hosting company is now transitioning our web site to a virtual server farm and they are requiring us to use their name servers. Reading through the documentation for Custom DNS I understand this is not possible. That I need to use the dyndns name servers. The web hosting company is not providing me any options but to use their name servers or find another hosting company. Is there any other way for me to continue to use DNYDNS Custom DNS service and use this hosting companies Name Servers for this one domain name. Please let me know your thoughts for a resolution, if there are any other than moving to a new hosting provider. Thank you for your assistance. |
|
The only options I can see are to move that domain away from Custom DNS, or move your hosts. Given how uncooperative your hosts are being, I'd suggest the latter may be a good plan anyway. |
It has been more than a month since the originator last visited this thread. Closing to stop the forum bot bumping it.