The recommended way to cope with DNS on a LAN using private addressing that is connected to the internet somehow eg via NAT is to use a thing called "splt primary DNS".
Basically what you do is this. 1. Have a DNS server on the publically addressed side that lists the stuff that the internet should be able to see (ie your mail server web server etc) but nothing that has a private address. This is setup as a primary DNS server. 2. Have another DNS server on the private LAN that lists only the stuff on the private LAN. This is setup as a slave to the first server. Thus anyone on the internet gets a resolution of your domain via 1) and those on the private LAN get resolution from 2) which if it does not have a name cached forwards the request to 1). Usually on a big LAN these two DNS servers are separate machines but it is possible (though I have never done it) to run them as two logical servers on the same physical server so long as the server is I guess dual homed into both the private and public LAN. Try looking here for example configs etc :- http://www.dns.net/dnsrd/ Have fun Pat
