Connect your existing build, deployment, management, monitoring, and collaboration platforms. From Puppet to Chef, HipChat to Slack, ServiceNow to JIRA, Splunk to New Relic and beyond, hand off data between systems to engage the right people.
Connect with xMatters.
Course Of The Month
3 days, 21 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
rheapubliclibrary.com resolve to rheapubliclibrary.org
Posted on 2013-01-04
I want rheapubliclibrary.com to resolve to rheapubliclibrary.org.
As a temporary ISP web.com fix, index.htm is:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>W G Rhea Public Library</title>
<meta http-equiv="refresh" content="0;url=http://rheapubliclibrary.org">
</head>
<body>
</body>
</html>
As a permanent fix (rheapubliclibrary.com ISP will be allowed to expire), I changed the Name Servers as below. Changes were made with the web.com support pages
https://support.web.com/DNSManager/DomainContactManagementForm.asp
After update, URL/Google rhealibrary.com returned "Oops! Internet Explorer could not find rheapubliclibrary.com"
As this evidently did not work, how can I acomplish redirection?
Changes to rheapubliclibraryc.com Nameservers:
Old Name Servers:
Domain Name: RHEAPUBLICLIBRARY.COM
Registrar: TUCOWS.COM CO.
Whois Server: whois.tucows.com
Referral URL: http://domainhelp.opensrs.net
Name Server: A.NS.INTERLAND.NET
Name Server: B.NS.INTERLAND.NET
Status: ok
Updated Date: 22-sep-2006
Creation Date: 20-oct-2005
Expiration Date: 20-oct-2015
New Name Servers:
NS39.DOMAINCONTROL.COM
NS40.DOMAINCONTROL.COM
As a temporary ISP web.com fix, index.htm is:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>W G Rhea Public Library</title>
<meta http-equiv="refresh" content="0;url=http://rheapubliclibrary.org">
</head>
<body>
</body>
</html>
As a permanent fix (rheapubliclibrary.com ISP will be allowed to expire), I changed the Name Servers as below. Changes were made with the web.com support pages
https://support.web.com/DNSManager/DomainContactManagementForm.asp
After update, URL/Google rhealibrary.com returned "Oops! Internet Explorer could not find rheapubliclibrary.com"
As this evidently did not work, how can I acomplish redirection?
Changes to rheapubliclibraryc.com Nameservers:
Old Name Servers:
Domain Name: RHEAPUBLICLIBRARY.COM
Registrar: TUCOWS.COM CO.
Whois Server: whois.tucows.com
Referral URL: http://domainhelp.opensrs.net
Name Server: A.NS.INTERLAND.NET
Name Server: B.NS.INTERLAND.NET
Status: ok
Updated Date: 22-sep-2006
Creation Date: 20-oct-2005
Expiration Date: 20-oct-2015
New Name Servers:
NS39.DOMAINCONTROL.COM
NS40.DOMAINCONTROL.COM
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
3 Comments
Hi Marspath,
When it comes to domains there are three entities who you need to deal with:
The Registrar - the company who actually owns the domain who you pay an annual fee to for registration. They maintain your WHOIS record which specifies your nameservers.
The Nameserver - the server which resolves hostnames into IP addresses for your domain, e.g. the company who turns "www.rheapubliclibrary.com" into the IP address of the webserver
The Webserver - the server which actually hosts and serves the website to the users.
Right now you have it set up like this:
Rheapubliclibrary.com
Registrar: Tucows / Web.com
Nameserver: Tucows / Web.com
Webserver: Tucows / Web.com
(The web server hosts a tiny webpage that asks the browser to redirect to Rheapubliclibrary.org)
Rheapubliclibrary.org
Registrar: GoDaddy
Nameserver: GoDaddy
Webserver: GoDaddy
(The web server hosts the actual Rheapubliclibrary.org website)
What you ATTEMPTED to do and did not work was change Rheapubliclibrary.com to this:
Rheapubliclibrary.com
Registrar: Tucows / Web.com
Nameserver: Godaddy
Webserver: ???? - failure!
Why did this fail? Because GoDaddy's nameservers do not know about your .COM domain name and it is refusing to resolve any requests for that domain.
You want to transfer your the domain to GoDaddy. Login to your GoDaddy account and start the process for transferring a new domain into your account.
You can either do a complete transfer of ownership to GoDaddy, in which case you'll end up with this setup:
Rheapubliclibrary.com
Registrar: Godaddy
Nameserver: Godaddy
Webserver: Godaddy
At this point you can configure the domain in GoDaddy to forward to .ORG
OR, if you insist on maintaining your account with Web.com you can do a partial transfer - e.g. GoDaddy recognizes the domain as an externally registered domain. You are responsible for configuring your A and MX records accordingly so that the domain resolves correctly to GoDaddy's servers so that they can host your email and website.... I don't really see any good reason for you to do it this way unless Web.com is twisting your arm somehow.
Rheapubliclibrary.com
Registrar: Tucows / Web.com
Nameserver: Tucows / Web.com <-- A and MX records specially configured so they resolve to GoDaddy's servers
Webserver: Godaddy
When it comes to domains there are three entities who you need to deal with:
The Registrar - the company who actually owns the domain who you pay an annual fee to for registration. They maintain your WHOIS record which specifies your nameservers.
The Nameserver - the server which resolves hostnames into IP addresses for your domain, e.g. the company who turns "www.rheapubliclibrary.com" into the IP address of the webserver
The Webserver - the server which actually hosts and serves the website to the users.
Right now you have it set up like this:
Rheapubliclibrary.com
Registrar: Tucows / Web.com
Nameserver: Tucows / Web.com
Webserver: Tucows / Web.com
(The web server hosts a tiny webpage that asks the browser to redirect to Rheapubliclibrary.org)
Rheapubliclibrary.org
Registrar: GoDaddy
Nameserver: GoDaddy
Webserver: GoDaddy
(The web server hosts the actual Rheapubliclibrary.org website)
What you ATTEMPTED to do and did not work was change Rheapubliclibrary.com to this:
Rheapubliclibrary.com
Registrar: Tucows / Web.com
Nameserver: Godaddy
Webserver: ???? - failure!
Why did this fail? Because GoDaddy's nameservers do not know about your .COM domain name and it is refusing to resolve any requests for that domain.
You want to transfer your the domain to GoDaddy. Login to your GoDaddy account and start the process for transferring a new domain into your account.
You can either do a complete transfer of ownership to GoDaddy, in which case you'll end up with this setup:
Rheapubliclibrary.com
Registrar: Godaddy
Nameserver: Godaddy
Webserver: Godaddy
At this point you can configure the domain in GoDaddy to forward to .ORG
OR, if you insist on maintaining your account with Web.com you can do a partial transfer - e.g. GoDaddy recognizes the domain as an externally registered domain. You are responsible for configuring your A and MX records accordingly so that the domain resolves correctly to GoDaddy's servers so that they can host your email and website.... I don't really see any good reason for you to do it this way unless Web.com is twisting your arm somehow.
Rheapubliclibrary.com
Registrar: Tucows / Web.com
Nameserver: Tucows / Web.com <-- A and MX records specially configured so they resolve to GoDaddy's servers
Webserver: Godaddy
The short answer is transfer your .ORG domain away from Web.com and to your new GoDaddy account so that both the .ORG and the .COM domains are under a single GoDaddy account. After that it's easy to configure GoDaddy to forward one domain to the other and it keeps your billing simple.
Call GoDaddy's support to get the process started: 1-866-938-1119.
Or, read up on how to do it yourself here:
http://products.secureserver.net/products/domain_transfers/transferinsider.pdf
And start the process yourself here:
http://www.godaddy.com/domains/domain-transfer.aspx
Call GoDaddy's support to get the process started: 1-866-938-1119.
Or, read up on how to do it yourself here:
http://products.secureserver.net/products/domain_transfers/transferinsider.pdf
And start the process yourself here:
http://www.godaddy.com/domains/domain-transfer.aspx
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
There have been a lot of times when we have seen the need to enter a large number of DNS entries in a forward lookup zone.
The standard procedure would be to launch the DNS Manager console, create the Zone and start adding new hosts using the New…
Occasionally you run into the website or two that will not resolve properly using your own DNS servers. Some people simply set up global forwarders for their DNS server. I don’t recommend doing this because it can cause problems resolving addresse…
Viewers will learn how to properly install and use Secure Shell (SSH) to work on projects or homework remotely.
Download Secure Shell:
Follow basic installation instructions:
Open Secure Shell and use "Quick Connect" to enter credentials includi…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Suggested Courses
Course of the Month3 days, 21 hours left to enroll
691 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.