URL Redirecting Query

  • Thread starter Thread starter Guest
  • Start date Start date
An 'A' record is a way of converting a hostname to an IP address

For example if you ping www.overclockers.co.uk in your command prompt you will get the IP address for it, www.overclockers.co.uk is an A record.

Code:
Pinging [url]www.overclockers.co.uk[/url] [91.151.217.10] with 32 bytes of data:

if your webhosting is with ukwebsolutionsdirect you will need to change the 'A' record for www.domainname.com to point to the IP address of the destinations web server.
 
Pinging www.redbullog.com would give you the webserver that is listed for the domain in DNS already, as such yes 83.170.69.53 would probably have been the uk2.net server.

Changing the Name Servers to ns1.svr25-speedyservers.com and ns2.svr25-speedyservers.com will change the DNS servers completely for your domain.

You need to make sure that the DNS records in place at ns1.svr25-speedyservers.com and ns2.svr25-speedyservers.com are correct.

i.e for www.domainname.com this needs to point to the IP address of your ukwebsolutionsdirect webserver and any MX (mail) records you had would need to be updated also.
 
The DNS is pointing to the right place now according to my DNS check:

CheckDNS.NET verifies www servers
Checking HTTP server www.redbullog.com [193.189.74.89]
HTTP server www.redbullog.com[193.189.74.89] answers on port 80
Received: HTTP/1.1 302 Moved Temporarily (Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8g mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635) Location: http://193.189.74.89/
Your main page redirects to another location. Several search engines will be unable to index your site.

I would advise that you contact ukwebsolutionsdirect about this and ask them to make sure their webserver is configured correctly for your domain name.

I am only familiar with IIS as opposed to Apache but in IIS this would need a 'site' to be created with your domain name and pointing this site to your folder on the local server.

I am not sure with Apache.
 
Correct me if i'm wrong but did you not have the nameservers pointing to the ukwebsolutions servers and it didn't make a difference?

If you changed the name servers then uk2.net should have no involvement in your DNS anymore.

To put it as simply as I can, to resolve this you should:

1) Point the nameservers to whoever you want to manage your DNS - i.e when someone types www.yourdomain.com you want to be in control of what IP address is returned.

2) Configure the server the domain is pointed to so that when the site is visited it gets displayed, this should obviously be a web server and the server should handle the rest. For example you point the www.yourdomain.com record to the IP address of the ukwebsolutions webserver.

I will give you an example.

so I go and register a domain name through uk2.net, let's say I register www.eulogy.co.uk for arguments sake.

I then purchase some webspace with another provider, again for arguments sake let's say this is 34sp.com.

34sp.com say to me "if you want to use our webspace change your domain name servers to point to":

ns1.34sp.com
ns1.34sp.com

So off I go to uk2.net and get the name servers changed.

Now all DNS resolution is taken care of by 34sp.com's name servers rather than uk2.net. UK2.net should no longer have a say in what addresses are returned when someone tries to email to you on that domain or type www.eulogy.com into their browser.

34sp.com make sure that the DNS records they have for your domain are correct, they would need to setup a WWW record for www.eulogy.com and point it to the IP address of their webservers.

They then configure their webservers so that when access requests are made over the internet on TCP port 80 your site is loaded.

All is well.

You can remove any 302/301 redirects you have setup in your homepage code.
 
Back
Top Bottom