Private in-house domain

[Tech Writer]

This is not a work environment.  All of the machines here are used for 
testing (demos, samples, lab exercise, etc.).  They actually assume the 
machines will be messed around with and rebuilt on a regular basis.

The fact that I will take two, and make one a DNS server, and another its 
client isn't beyond what might be expected in this lab.  As I think I 
mentioned, my only issue (valid, or not) is that once I made my two-machine 
world, I still wanted access to the gateway so that I could browse the web. 
That isn't really necessary....  just convenient for looking things up. 
That's where I got stuck.  In my own little world, my browser wouldn't 
browse.  That's why I added the alias to give my first machine it's original 
IP address back.  Once I did that, it was able to access the gateway and I 
could browse again.

Peg

----- Original Message ----- 
From: "Thomas Charron" <twaffle at gmail.com>
To: "Tech Writer" <TechWtr at handspun.com>
Cc: <gnhlug-discuss at mail.gnhlug.org>
Sent: Thursday, May 17, 2007 4:58 PM
Subject: Re: Private in-house domain


> On 5/17/07, Tech Writer <TechWtr at handspun.com> wrote:
>> I did this in my own home network environment.  But when it's working, I
>> will be duplicating it on a couple of machines in the training lab.  If
>> someone can think of a better way that this could have been implemented, 
>> I'm
>> always open to suggestions.
>
>  Use another cheapo linksys box.
>
>  What you're doing could potentially cause headaches up the whazoo.
> And if you did something like that on a network I had anything to do
> with in a work environment, I'd very quickly show your machines the
> door.  :-)
>
>  Do their network admins know what you're intending on doing?
>
> -- 
> -- Thomas