Point existing domain to new server issues

[Batista]

HI guys


I have a windows shared hosting package with afrihost and a dedicated server.
I want to make the site name on my shared hosting point to my new servers web site.
I was told to do a dns on their client zone to point my sitename to the new server.

Sitename on shared hosting is- test.x.co.za
In my dedicated server i access my site through 1xx.xx.xx.xx:8081 (changed iis to use 8081), so the site is up and running on the server.

I was told to make a dns that looks like this

test.x.co.za -> 1xx.xx.xx.xx

I did that and had to wait 30 mins for it to reflect, and finally tried test.x.co.za in my browser and got an error, unable to resolve host!

Should it have been
test.x.co.za -> 1xx.xx.xx.xx :8081?
Since my site is sitting on port 8081?

Pls help...
Thanks

 

[shauntir]

Looks like you aren't able to get the A record to point to non-standard ports: http://support.simpledns.com/kb/a35...r-in-dns-other-than-the-standard-port-80.aspx

Looks like you have to change IIS to use standard port 80.

Edit, have a look at using SRV records: http://stackoverflow.com/questions/19015138/how-to-redirect-dns-to-different-ports

 

[w1z4rd]

HI guys


I have a windows shared hosting package with afrihost and a dedicated server.
I want to make the site name on my shared hosting point to my new servers web site.
I was told to do a dns on their client zone to point my sitename to the new server.

Sitename on shared hosting is- test.x.co.za
In my dedicated server i access my site through 1xx.xx.xx.xx:8081 (changed iis to use 8081), so the site is up and running on the server.

I was told to make a dns that looks like this

test.x.co.za -> 1xx.xx.xx.xx

I did that and had to wait 30 mins for it to reflect, and finally tried test.x.co.za in my browser and got an error, unable to resolve host!

Should it have been
test.x.co.za -> 1xx.xx.xx.xx :8081?
Since my site is sitting on port 8081?

Pls help...
Thanks

DNS propagation can take 4-48 hours. Your DNS is probably cached. If you have a VPS or something somewhere else, try login to that and ping that host name from a different ISP. I dont think this has anything to do with SRV records and you definitely do not put a port number into a DNS record But yeah, most likely cached DNS.

If you dont have a VPS somewhere, feel free to PM me and I can check your records for you. I literally do this stuff for a living

To see if your subdomain is configured to point at the right address use NSLOOKUP or a NSLOOKUP tool like this:

http://network-tools.com/nslook/

Basically put in your sub domain in the one field and put the nameserver that Afrihost gave you in the nameserver field and then query it. It will tell you if your DNS is configured correctly.

 

[Batista]

Looks like you aren't able to get the A record to point to non-standard ports: http://support.simpledns.com/kb/a35...r-in-dns-other-than-the-standard-port-80.aspx

Looks like you have to change IIS to use standard port 80.

Edit, have a look at using SRV records: http://stackoverflow.com/questions/19015138/how-to-redirect-dns-to-different-ports

This sounds right, darnit, I only put it on port 8081 because WAMP uses 80 and IIS now uses 8081.So now I will have to make WAMP run on a different port?

 

[Batista]

DNS propagation can take 4-48 hours. Your DNS is probably cached. If you have a VPS or something somewhere else, try login to that and ping that host name from a different ISP. I dont think this has anything to do with SRV records and you definitely do not put a port number into a DNS record But yeah, most likely cached DNS.

If you dont have a VPS somewhere, feel free to PM me and I can check your records for you. I literally do this stuff for a living

To see if your subdomain is configured to point at the right address use NSLOOKUP or a NSLOOKUP tool like this:

http://network-tools.com/nslook/

Basically put in your sub domain in the one field and put the nameserver that Afrihost gave you in the nameserver field and then query it. It will tell you if your DNS is configured correctly.

Its cool, I just use cmd ping - usually takes around 30 mins to reflect though.You hit the nail on the head when you said , cant put port number in DNS

 

[shauntir]

Probably best to separate Apache onto it's own box. Depends what you are trying to do, you can possibly use IIS to run php stuff if that is a requirement.

The reverse is also true, you can try mod_mono on apache for C# apps.

 

[DrJohnZoidberg]

DNS doesn't care about port numbers.

If you create an A record for test.x.co.za -> 1xx.xx.xx.xx and you want to access port 8081, then you must go to test.x.co.za:8081.

 

[Batista]

Hey coders

I fixed the issue by changing WAMPS port to 8085, default web site to 8081 and my web site to 80,Works like a bomb now!

Thanks for the help!

 

[Batista]

Probably best to separate Apache onto it's own box. Depends what you are trying to do, you can possibly use IIS to run php stuff if that is a requirement.

The reverse is also true, you can try mod_mono on apache for C# apps.

Thanks Shaun, my site is asp.net/c#.