I'd like to echo Chuck's statements. I ran into so many oddities when I put in my own email, web, game, ftp, etc servers here that I just ended up option for an intenal DNS server to handle everything instead of trying to manage things though hosts. It was just a lot easier. **OT**Perhaps FOSS DNS servers should be part of our lecture series!?!? Mike K. On Mon, Jan 18, 2010 at 10:02 PM, <cstickelman@xxxxxxxxxx> wrote: > I think this example can underscore a concept that we should all > appreciate: > If DNS (or name-resolution in general) ain't happy, your network ain't > happy. > > In many networks DNS is a linchpin service. So much can be done w/ it, and > it becomes central to so many services, that if it's broken *nothing* will > work as expected. > > Well done Rob! > Chuck > > ---- Rob Gibson <nosbig@xxxxxxxxx> wrote: > > To describe the answer to the solution, we needed a little more > > context that was not available in the original mail to the list. > > > > Ken was getting a different response to his browsing when trying to > > visit the site from the local machine and remote machines. > > > > This threw my instinct to worrying about DNS/vhosts... I asked Ken > > how he was browsing to the sites, as there would be a distinct > > difference to Apache of browsing to http://192.168.1.x versus > > http://127.0.0.1. He replied that he was browsing to kc8tdw.com on > > each machine; I asked what does that name resolve to on each machine. > > > > Ken then wrote that on the local machine for the webserver, kc8tdw.com > > was listed 3 times, as was in his /etc/hosts file: > > 127.0.0.1 kc8tdw.com localhost.localdomain localhost > > 127.0.0.1 kc8tdw.com kc8tdw > > 192.168.1.65 kc8tdw.com kc8tdw > > > > He asked if that looked correct... I let him know that there should > > only be one reference in his /etc/hosts, typically, to kc8tdw.com and > > to removew his domain name from the first line, remove the second, and > > leave the third line alone. > > > > He replied that the fix worked... As the vhost configuration was > > correct (since other machines could access the corect information), > > the name resolution on the local machine was point to localhost which > > was not configured to respond with the correct vhost. We could have > > also adjusted the Apache configu to present that vhost on the > > 127.0.0.1 request, but it was a better and cleaner solution to clean > > up the name resolution. > > > > Rob > > > > On Mon, Jan 18, 2010 at 2:58 AM, Ken Allen <kc8tdw@xxxxxxxxx> wrote: > > > fixed, thanks Rob! > > > > > > On Mon, Jan 18, 2010 at 12:13 AM, Ken Allen <kc8tdw@xxxxxxxxx> wrote: > > >> > > >> On my desktop/server, if I type in kc8tdw.com, I get "It Works!". > This is > > >> confusing me as this is in /var/www. In my kc8tdw.com.conf file in > > >> /ect/apache2/sites-available, the DocumentRoot line says > > >> /home/kc8tdw/public_html, which is correct. So, if that is correct, > how in > > >> the world is it getting to /var/www, instead of > /home/kc8tdw/public_html? > > >> > > >> Thanks, > > >> > > >> Ken > > >> > > >> Also, Virtualmin is up and running fine now, Horde is running but > doing > > >> some fine tuning on it. > > > > > > > > > > > > > > -- > > > > Joan Crawford - "I, Joan Crawford, I believe in the dollar. > > Everything I earn, I spend." - > > http://www.brainyquote.com/quotes/authors/j/joan_crawford.html > > > > To unsubscribe send to ncolug-request@xxxxxxxxxxxxx with 'unsubscribe' > in the Subject field. > > > > > To unsubscribe send to ncolug-request@xxxxxxxxxxxxx with 'unsubscribe' in > the Subject field. > >