Domain Registered in One location, Records Elsewhere, Website Another Location....
Discuss Domain Registered in One location, Records Elsewhere, Website Another Location.... in the DNS forum on Dev Shed. Domain Registered in One location, Records Elsewhere, Website Another Location.... DNS forum discussing issues, servers, and configurations. The Domain Name System (DNS) is what the Internet uses to translate website names into IP addresses.
Receive the tools necessary to be the rock star of your field. Our 12-month program teaches you the evolving world of multi-channel marketing as well as the complex issues and opportunities found in the industry.
ASP Free and Iron Speed Designer are giving away $5,500+ in FREE licenses. Iron Speed's RAD CASE toolset can save up to 80% of your coding time. One free license per week, one perpetual license per month! Download and Activate to enter!
Web development can be a daunting task, even for specialists. There is a lot of information to absorb and a lot of technologies to learn in order to manage a superior website. When trying to learn the ropes, developers need a reliable source to introduce new ideas that can be easily implemented. When working on large projects, even web veterans may run into a technology or an aspect of a technology that they are unfamiliar with.
Posts: 3
Time spent in forums: 2 h 5 m 4 sec
Reputation Power: 0
Domain Registered in One location, Records Elsewhere, Website Another Location....
Need a little advice if anyone can assist.
I have a domain registered with GoDaddy and setup with the Name Servers of my VPS hosted elsewhere. On my VPS I am hosting the mail for that site, but the website itself is being run by a third-party on their server. I currently have a meta-refresh in place to forward traffic to the third-party.
What I would like to do is configure the DNS to forward webtrafffic to the third-party while keeping mail direction on my VPS.
The solution I believe is correct:
GoDaddy points to Name Servers of VPS - currently in place
A record pointing to IP of third-party - in place but not functioning
MX record pointing to mail-dot-mydomain-dot-com - in place
CNAME pointing to VPS IP - in place
CNAME for www-dot-mydomain-dot-com pointing mydomain-dot-com - in place
All TTL's are low for quick updates.
Posts: 24
Time spent in forums: 2 h 49 m 37 sec
Reputation Power: 0
In your DNS zone at Godaddy, all you need to do is update the 'www' or whatever other record you choose to use for your website and point it to the IP of the webserver that is hosting your website. Then on the webserver, you will most likely need to update the host headers to accept the domain name for that website. This is very typical for webservers that host more than one website. The webserver needs to send the traffic to the correct website, based on the URL.
Not sure why you have "meta-refresh in place to forward traffic to the third-party." in place if you all you need to do is point the DNS record for your website to the correct IP that is hosting your website.
Posts: 3
Time spent in forums: 2 h 5 m 4 sec
Reputation Power: 0
Quote:
Originally Posted by [JM]
In your DNS zone at Godaddy, all you need to do is update the 'www' or whatever other record you choose to use for your website and point it to the IP of the webserver that is hosting your website. Then on the webserver, you will most likely need to update the host headers to accept the domain name for that website. This is very typical for webservers that host more than one website. The webserver needs to send the traffic to the correct website, based on the URL.
Not sure why you have "meta-refresh in place to forward traffic to the third-party." in place if you all you need to do is point the DNS record for your website to the correct IP that is hosting your website.
Zone records are on my VPS. I believe the web traffic is setup correctly using a A record for the third-party server IP and CNAME for www pointed at the domain name.
Posts: 3
Time spent in forums: 2 h 5 m 4 sec
Reputation Power: 0
Quote:
Originally Posted by [JM]
In your DNS zone at Godaddy, all you need to do is update the 'www' or whatever other record you choose to use for your website and point it to the IP of the webserver that is hosting your website. Then on the webserver, you will most likely need to update the host headers to accept the domain name for that website. This is very typical for webservers that host more than one website. The webserver needs to send the traffic to the correct website, based on the URL.
Not sure why you have "meta-refresh in place to forward traffic to the third-party." in place if you all you need to do is point the DNS record for your website to the correct IP that is hosting your website.
By the way, thank you for your replys, I much appreciate the help.
The meta-refresh was in place until the DNS records updated, which they now have - it was a temporary solution.
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
