Forum URL: http://ihosting.vforums.co.uk -> http://support.ihosting.co.cc
Problem:
Ok, I need to change my domain name. which is the support one. I need it to redirect to support.powerwh.com instead of what it is now. If at all possible?
Thanks.
edit:
I already got the domain, and everything. So now all I have to do is have the support forum changed to the powerwh.com domain.
Just to clarify, you want to change the custom domain attached to that forum?
Have you setup the relevant CNAME record for the new domain yet?
Yes, I want it to be http://support.powerwh.com
and yes, the CNAME is already set up for that.
Thanks
Bump Bump Rossy? Everything is set up, if you click on http://support.powerwh.com it takes you to http://virtualforums.co.uk/notfound/code/101/forum/support.p owerwh.com
It can be redirected right?
Hi Nick,
Should be setup this end.
However I am having trouble testing as the name servers for both of those domains seem to be down.
Let me know if it is working.
- Ross
Hi Nick,
Should be setup this end.
However I am having trouble testing as the name servers for both of those domains seem to be down.
Let me know if it is working.
- Ross
Nope doesn't work. the NS servers are NS1.powerwh.com and NS2.powerwh.com if that's what you mean.![]()
Those are not the name servers I'm getting for the domain. I would suggest checking you've set them up right. If you're using NS which are sub-domains of the domain itself then you may need to setup glue records for this.
See this tool, it doesn't return any DNS records.
http://who.is/dns/powerwh.com
Oh, that's odd on why it's still ColorHost.
This site shows my NS Records: http://www.dnsstuff.com/tools/whois/?tool_id=66&token=&toolhandler_redirect=0&ip=powerwh.com
edit:
Yeah, that site seems to keep old records or something, I have not been apart of CinchHost for iDirectory for a good few months now. http://www.who.is/dns/idirectory.us/ Which on my GoDaddy, I have it updated to NS1.powerwh.com and NS2.powerwh.com
It also seems as things are all messed upI don't quite understand why.
http://www.dnsstuff.com/tools/
whois/?tool_id=66&token=&toolhandler_redirect=0&ip=idirectory.us
![]()
I've always trusted who.is and use it several times a day. I've never known it to be wrong![]()
But if you want another source:
http://www.dnswatch.info/dns/dnslookup?la=en&host=support.powerwh.com&type=NS&submit=Resolve
That is unable to connect to your name server (singular as both ns1 and ns2 seem to point to the same IP address).
Also:
http://ping.eu/nslookup/
http://www.kloth.net/services/nslookup.php
They all have trouble looking up any info on your domain.
I've always trusted who.is and use it several times a day. I've never known it to be wrong![]()
But if you want another source:
http://www.dnswatch.info/dns/dnslookup?la=en&host=support.powerwh.com&type=NS&submit=Resolve
That is unable to connect to your name server (singular as both ns1 and ns2 seem to point to the same IP address).
Also:
http://ping.eu/nslookup/
http://www.kloth.net/services/nslookup.php
They all have trouble looking up any info on your domain.
Trufax. I always use who.is at work and it's never let me down before.
*leaves before he derails the thread*
edit: Ok, the forum now shows up, and is in place.![]()
edit 2: Kind of. Might be a DNS issue as I tried logging in and it said Oops! Google Chrome could not find support.powerwh.com![]()
I checked the A Records, and some how something was added to it it was ns1.powerwh.com.powerwh.com and ns2.powerwh.com.powerwh.com So I re-did it and it now only shows 1 .powerwh.com
Try now.
Seems as everything finally updated with my own NS records.![]()
Lately GoDaddy has been having loads of trouble finally updating their nameservers/dns information. It took my friend's a WEEK before the other sites saw her dns update. GoDaddy denied it took that long they said it went through instantly.
but, I've seen a lot of complaints about this over the past few weeks.
Power Web Hosting wasn't registered by GoDaddy, but http://colorhost.co Which is my own Host. iDirectory is registered with GoDaddy. I had to update several times because it wouldn't go through, did it like 4 times, but it went through, and people could still access it, even though other sites showed the old NS records.