web server

[AccessXP]

Question?

The users on the network cannot type the domain name

http://www.******.com

and see the web page. Instead they must type the ip 192.168.0.252. Could someone tell me what I need to change to fix this please.


Thank you know for any help.

 

[franklin97355]

You need to have a DNS entry on a DNS server on the network to resolve the name to an IP.

 

[AccessXP]

So do I make one of the DNS entries the servers ip?

Where in linux is this accomplished?

 

[unixfreak]

Depending on how your network is designed you should really run a caching or forwarding name server and then point your clients to that.

Google for "BIND caching name server"

Cheers

 

[RhythmAce]

We're assuming that this is NOT a fully qualified domain name. If it is an FQDN then the problem may be that your router is not forwarding http traffic (port 80) to 192.168.0.252.

 

[nawlej]

Well, you dont really need to configure DNS locally....If I didnt have more than one device to configure for use with DNS, I wouldnt bother with setting up DNS and a zone file. I would just set my .com dns entry to the WAN address of your router, and then forward port 80, as suggested to the webserver. Even apache is smart enough to figure out which vhost you are trying to query without dns.

Hope this helps.

___________________________________
[morse]--... ...--[/morse], Eric.

 

[smah]

I'm thinking along the same lines as RhythmAce. But I'm assuming that it is a FQDN and that the local router just doesn't support loopback to it's own WAN IP.

 

[gbaughma]

196.168.x.x is a non-routable IP... if you're trying to access your web page from the outside world, that isn't going to work.

Meanwhile, if you just want to be able to see it from inside, the previous posts are correct. You either need a DNS entry pointing at the IP address of the server.

*** OR ***
... if you're on a relatively small network (say, less than 10 machines), you *could* do a LMHOSTS lookup on each PC.... (assuming the workstations are running Windows).

... I wouldn't do the LMHOSTS on an installation of more than a few machines, because it's a pain to maintain.



Just my $.02

"In order to start solving a problem, one must first identify it's owner." --Me
--Greg