Patrick Nelson wrote: ----------------->>>> I'm just not sure what is the best way to name systems on the private side of our LAN. We tried using just single names but some programs seem to have problems with it. Like NIS and SendMail. What is the best way to name systems on a LAN behind a firewall that don't have internet names? ----------------->>>> So it seems that I call my systems a. <hostname>.localdomain but I'm not sure if that would work across my private network b. <hostname>.<privatedomain> w/ DNS server which is more of a total TCPIP solution
OK hmm... Well I'm of course not doing a DNS now, but think that that sounds intriguing! I'm guessing here but what would I need to do and what would it look like. 1. Get Bind and install it. 2. Edit the bind so that I have a local private domain as well as my public one (split DNS?) 3. Edit the nameservers on the private network to point to this new DNS server rather than the ISPs nameservers that they currently point to. 4. Test! Does that about map out the process? So is it hard to set that up (should I be afraid...very afraid)? Any suggestions or comments from the trenches of Bind Gurus! _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
