1) Is the IP listen in TCP/IP
2) Is the IP being referenced in the IIS settings
3) In the IIS settings do you have it listening for the domain and the www domain alias
4) In the IIS settings do you have the domain pointing to a directory
5) Is IIS running and is the specific site you setup running
Somewhat obvious stuff but it should be all that you need to worry about.
(After posting I noticed that I can't resolve the domain name at all, nor can I resolve ns1.novaback.net. Are you sure you have a DNS server running? I'm not familiar with windows DNS server personally, but would be the first place to start)
- Created a zone called ns1.novaback.net
- Opened the SOA record and set the primary server ns1.novaback.net
- Opened the NS file and added 188.8.131.52
- I then right clicked novaback.net in the forward lookup zone and selected new host
- For the name I put `novaback`
- For the IP address, 184.108.40.206
- I tried to check to create the PTR record, but it said that it could not be done probably because it was not created as a reverse look up (I have created no reverse look-ups at this point)
- I then went and created a reverse look up and configured it. For the network ID i used 192.168.0
I'm sure Im doing something wrong, I am not familiar with this stuff. I just don't know what...
The server is 15 feet behind me and is soley my responsibility. I'm sure that it's a breeze for anyone who has done it before. However, I'm needing to figure it out here myself. Ill play with the DNS zone more after i configure out new router. I'm preeeetty sure I had it going yesterday, then our network started acting up.