Private in-house domain

[Tech Writer]

Reading some of the replies, I wanted to clarify my initial problem just a 
little...  I realize this isn't a setup anyone would put together in the 
"real" world, but it seemed to fit the environment I needed.  Let me try to 
explain just a little bit...

My task (as a technical writer) was to take a DNS and mailserver sample, and 
implement it on some test machines.  If this were in a closed environment, 
I'd just pick any address range, and set it up without any concern for the 
machines around me.  But, when I'm done, I need to temporarily set this up 
in a larger lab, used for training, at the customer site.

The problem is that the customer's lab has a "real" DNS server, IP 
addresses, etc.  The machines I will be allocated are currently in the lab, 
and have pre-defined addresses in the 192.168.1.0/24 range.  I can not mess 
around with these addresses, nor can I allocate new ones, etc.  However, I 
DO need to set up a DNS server.  So, since I can't control the addresses 
that are already there, the simplest thing seemed to be to just grab my own 
set of addresses (that aren't being used in that lab) and have my DNS server 
control this alternate set of addresses.

So, I gave my DNS server, and its client addresses in the 10.25.1.0/24 
range.  That was fine, except that they couldn't get out to the rest of the 
world.  When I added the alias for eth0 (so it could also use 192.168.1.30) 
and set the gateway to 192.168.1.1, then everything seemed to work fine.

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.

Peg