setting up own server

[KevCB226]

OK, I just bought a domain name from 123-reg.co.uk, and I've just decided to use IIS instead of apache since it's already on the machine, but now I'm having problems setting it up.

I've created a domain in the forward lookup zones pointing to the nameserver of 123-reg.

But it still isn't working, are there any other settings I need to configure in IIS or on the 123-reg site?

Also do I need a domain in the reverse lookup up zones?

I thought I'd post a thread here since so many of you have got domain names from them, can anyone help?

[kmount]

Ok, im a linux/unix guy so im COMPLETELY anti IIS.

Log into 123-reg, and point the domain's dns to your ip.

This will mean that when someone visits yourdomain.com it will look to http://yourip/

Port forward port 80 from your router to your machine so that requests to http://yourip/ on port 80 will be forwarded to the correct place and not bounced by your router.

This should get you started. If you want to use PHP, use apache, if you want to use ASP use IIS.

[KevCB226]

OK just so I understand, when I go into modify DNS, I change the @ and www ip addresses to my computers ip address e.g. if my ip address was 123.456.789.0
I simply change it to that or do I have to add :80 on the end to look at that port.

I've already set my router to allow access to port 80.

[kmount]

You dont need to add :80 as normal HTTP requests are on port 80.

If you intend to host your own email server, you also require an MX record to point to you (IE, a mail exchange record which basically gives your machine authority to be email server)

[KevCB226]

OK, I've done that, but now it keeps connecting to my router, even tho I've allowed inbound access on port 80.

Why is it doing this?

[John]

I think that it is because you are connecting off your connection, what happens if you try off dial-up or another person's connection?

[kmount]

If you try and do it from your pc you will see the router config page due to the way a router works (way around this is to add your domain to your hosts file).

If you try from someone elses connection it should work fine.

[KevCB226]

OK, I'm back again.

I just got someone to try to access my server, and they said that it just came up with the msn search page "cannot find the following site...." etc. So what haven't I done?

I've created a DNS on the server using the nameservers from 123-Reg.
I've gone onto 123-Reg and used my ip address as the domain dns.
I've allowed all access to port 80, inbound and outbound on my router.
I've assigned my ip address under the webservers properties in the IIS.

Am I missing anything?

[AndyB]

Originally Posted by KevCB226

I've created a DNS on the server using the nameservers from 123-Reg.
I've gone onto 123-Reg and used my ip address as the domain dns.
I've allowed all access to port 80, inbound and outbound on my router.
I've assigned my ip address under the webservers properties in the IIS.

Am I missing anything?

Have you enabled port forwarding/nat on the router to send all incoming port 80 requests to the internal IP of your server? alternatively have you put the server in the DMZ

[KevCB226]

OK, still having problems, found out that I had my IP address set to the routers IP address, so of course it wouldn't forward to the server, but I've corrected that now, and I've also added the internal IP address to the DMZ, and still it isn't working.

Any other suggestions, if it helps I'm using the Netgear DG834 router.

[aos101]

Originally Posted by KevCB226

OK, still having problems, found out that I had my IP address set to the routers IP address, so of course it wouldn't forward to the server, but I've corrected that now, and I've also added the internal IP address to the DMZ, and still it isn't working.

Any other suggestions, if it helps I'm using the Netgear DG834 router.

I've just tried accessing the webserver running on your IP now and thats working fine. But avoid using DMZ if at all possible as that looses you a lot of protection the router gives you. Just forwarding port 80 to your internal IP should work fine. I think the problem is that at 123-reg you've entered your internal IP of 192.168.0.2 rather than your public IP address. Change this in the 123-reg control panel to your public IP address (something like 83.67.x.x), wait for the DNS to update and it should work.

One thing to watch out for though is that accessing your website using its address from behind your router will not work because the DG834 doesn't support loopback connections. To test if its working you'll have to try the site from another Internet connection or a proxy server or a service like The Cloak which accesses the site from a different Internet connection that isn't behind your router.

[KevCB226]

OK, I have used 192.168.0.2 as you said rather than my public IP, used the ipconfig command to get the information but obviously that's wrong, so is there anyway of getting my public IP address, e.g. is it in the members area on f2s, or will I have to get it another way?

Thanks for the reply

[aos101]

Yes its in the members area under "Your ADSL Details" where its says "WAN IP Address", or you could just visit http://www.whatismyip.com/ from your connection and it will tell you.

[Justin]

If you don't like the ads, you can use:
http://www.youripis.co.uk/

Sorry, had to say that!

[Nippoo]

Okie.

Go to http://localhost/ on your computer. See the webpage? Good.

Find out your LAN IP by going Start --> Run, CMD, then type "ipconfig". It will say somewhere something like 10.0.0.144 - you'll need that.

Then, go to http://10.0.0.138 (or whatever your router's IP is), and go to Firewall Rules, then click on "Add" under the Inbound Services table. Create a new one for Port 80 (HTTP) to forward to your LAN IP, in my case 10.0.0.144.

Now, when someone else goes to your IP, or to your domain name, they'll get the page. Bingo!

Originally Posted by KevCB226

I've assigned my ip address under the webservers properties in the IIS.

I'm not clear whether you've assigned your internal or external (87.*) address in here.

It needs to be your internal address.

If you are unsure, it will probably be fine to select "all unassigned" from the list in the IP address drop-down.