General discussion

Locked

2000 web server

By Eminent87 ·
Hi,

I recently registered my domain name and i want to set up my own webserver. Everything works fine is I use the IP address and if I type in the domain name without the www but if I include the www (www.mysite.com) then it wouldn't work. Can anybody point me in the right direction as to what to do? I've set up my zone file to point to the static IP of my webserver. My zone file looks like this:
webserver.domain.com A 67.113.xxx.123
www.domain.com A 67.113.xxx.123

I've also tried setting the host header to be www.domain.com but that didn't work either. I know this shouldn't be that difficult but for some reason I can't seem to figure it out. Please help!

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

2000 web server

by CG IT In reply to 2000 web server

what name servers are you using, your own, your ISP or the Registry's name servers? Does your FQDN resolve to your ISP IP address in WHOIS? Use any WHOIS to check to see what name servers are resolving your IP to FQDN and if their the right ones. Please note that it can take up to 72 hrs for the WHOIS A records to propogate throughout the WWW.

Collapse -

2000 web server

by Eminent87 In reply to 2000 web server

Poster rated this answer

Collapse -

2000 web server

by Eminent87 In reply to 2000 web server

Verio, the company where I registered my domain name is hosting my dns for me. I also host my own internal dns. If I ping the www.domain.com then it would back with the right ip address.

I believe it is a dns issue since I am able to get to via IP address and by the domain name only, without the www.

Collapse -

2000 web server

by CG IT In reply to 2000 web server

If your registry is hosting your name servers then your FQDN should resolve to your IP address [provided your using a static IP address] If your ISP assigns your a dynamic IP address, then you will need what is called a client utility [which they should have for you] which provides their name servers with your current IP address.

The URL http://www.mydomain.com or http://mydomain.com when typed into the address bar is in essence typing in http://<IP address><80>. If your registry should have created A records >mydomain.com & *.mydomain.com < and put them in their registered name server. That way when someone types in http://www.mydomain.com they are in essence asking the name servers around the world "hey any one know "WHO IS" mydomain.com. Your registry name servers respond "yep, that's <IP address thus and such> and the request is fowarded to your IP address.

Your own name servers don't enter into the mix.

Collapse -

2000 web server

by CG IT In reply to 2000 web server

Because other name servers don't recognize your name server as authoritative in providing name to IP address resolution.

So, once the authoritative name server for your domain name gives out your IP address, fullfilling that request for web content is all depended upon you have your inbound port 80 traffic routed. If it's routed to go to your internal web server [W2K based with IIS then IIS will handle http [port 80] requests and return the requested content.

In simple terms, that's how it works. If your not getting inbound http URL requests for web content then A). your registry screwed up on the A records [which usually is rare but it does happen. A,1). your registry name servers don't know what your IP address is therefore can't direct http content requests to your web server [see above: "getting a client program from your registry to provide their name server(s) with your IP address" B). The routed inbound http requests aren't getting to your web server [which goes with A,1 above] .

Collapse -

2000 web server

by Eminent87 In reply to 2000 web server

Poster rated this answer

Collapse -

2000 web server

by LordInfidel In reply to 2000 web server

This is fairly simple.

(In IIS) Where you set your host header, did you bind it to an IP address, or did you leave it all unassigned? Remember that you "have" to press the advanced button to set host header/additional host headers.

And did you leave your default website running or did you create a new site.

By saying that you can connect to it via IP, tells me host headers are not being used in IIS, or that you have 2 sites set up.

The short and skinny is, that once you use a host header, every site bound to that IP address must also use a host header.

So your default website can not be bound to 67.113.xxx.123 without a host header

and your real website bound to 67.113.xxx.123 with a host header.

It will not work. Both sites either need their own IP or they both need to use host headers using the same IP.

As long as you can do a nslookup, change your server to a different ISP, like att, and then query your address. If it comes back correctly then it is notDNS.

Collapse -

2000 web server

by Eminent87 In reply to 2000 web server

Poster rated this answer

Collapse -

2000 web server

by Eminent87 In reply to 2000 web server

This question was closed by the author

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums