On Fri, 2006-07-28 at 15:32 -0500, Gregory P. Ennis wrote: > We have one of our PC's set up as an internal (local network) web > server. The PC is listed in each of the other linux machines /etc/hosts > file with a local network ip address. When squid is turned off it is > easy for the network PC's to access the internal web pages by putting in > the name of the server in the address bar. When squid is turned on each > user gets the message that it can not be found. > > Since the machine functioning as the apache server is inside the local > network it is not listed in the dns servers. When squid is function the > query fails. Is there a way to put an entry in the squid.conf file so > that named queries can point back to the local network even though a dns > record does not exist? Alternate approach: Install a local DNS server, populate it with local machine entries, use it for local and internet name resolution. I first did this because of the same problem you mention. I haven't looked back, it provided other benefits as well. Even on a network with just a few PCs, messing around with hosts files can be a pain. But having a proper DNS server means you can avoid that, and have local mail running properly (a hosts file cannot provide MX records, for instance). -- (Currently running FC4, occasionally trying FC5.) Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
