Networking and Computer Name Question
Posted: Sat Aug 18, 2007 6:01 pm
This will be an easy question for you sys-admins, but I'm hoping that you could give me some direction. Also if you have some great sources for further reading I would appreciate those also.
After reading Linc's blog post a few days back, I realized that I need to do something about my small network and communicating between computers.
Problem: I'm tired of having to use the ip address for samba shares, ssh, ftp, and rdesktop.
I have the following 8 computers on my peer to peer network:
Office Workstation--Fedora 7 (on sometimes)
Home Workstation--Ubuntu LTS (on sometimes)
File Server--FreeNAS (using because supposed to be easy to set up and administer)
Web Server--DSL (using because a very low powered machine, needs a light distro) Also this computer is in a DMZ.
Fun Workstation--DSL (on only when learning something new on it)
Laptop--WindowsXP (on for work necessary items at times)
Secretary Workstation--Windows98 (on once or twice a week for minor secretarial work)
Audio Workstation--WindowsXP (on only for work related recording, once or twice a week)
From what I understand I have two options:
1. Set up DNS on a computer running all of the time like Linc did. Advantages: everything Linc mentioned and more. Disadvantages: I don't think I can add it to FreeNAS. I don't know if it is wise to put it on a computer that is a webserver, and in a DMZ.
2. Set up the hosts files on every computer. Disadvantage: One change needs to be made 8 times. I have to give static ip addresses to all the computers, I don't know if that is a security disadvantage if you are basically shutting off DHCP on a NAT firewall. Advantages: Can use OpenDNS service and their auto blocking of phishing and porn sites. Can have names for all of the computers.
I'm leaning towards option 2 mostly because of the OpenDNS stuff.
If I go with option 2 are there other disadvantages that I'm not considering?
If I go with option 2 how do you go about naming a local domain like Linc did with $blankname.linc.lan?
Thanks for any guidance, and resources that would be helpful to a hobbyist sysadmin.
After reading Linc's blog post a few days back, I realized that I need to do something about my small network and communicating between computers.
Problem: I'm tired of having to use the ip address for samba shares, ssh, ftp, and rdesktop.
I have the following 8 computers on my peer to peer network:
Office Workstation--Fedora 7 (on sometimes)
Home Workstation--Ubuntu LTS (on sometimes)
File Server--FreeNAS (using because supposed to be easy to set up and administer)
Web Server--DSL (using because a very low powered machine, needs a light distro) Also this computer is in a DMZ.
Fun Workstation--DSL (on only when learning something new on it)
Laptop--WindowsXP (on for work necessary items at times)
Secretary Workstation--Windows98 (on once or twice a week for minor secretarial work)
Audio Workstation--WindowsXP (on only for work related recording, once or twice a week)
From what I understand I have two options:
1. Set up DNS on a computer running all of the time like Linc did. Advantages: everything Linc mentioned and more. Disadvantages: I don't think I can add it to FreeNAS. I don't know if it is wise to put it on a computer that is a webserver, and in a DMZ.
2. Set up the hosts files on every computer. Disadvantage: One change needs to be made 8 times. I have to give static ip addresses to all the computers, I don't know if that is a security disadvantage if you are basically shutting off DHCP on a NAT firewall. Advantages: Can use OpenDNS service and their auto blocking of phishing and porn sites. Can have names for all of the computers.
I'm leaning towards option 2 mostly because of the OpenDNS stuff.
If I go with option 2 are there other disadvantages that I'm not considering?
If I go with option 2 how do you go about naming a local domain like Linc did with $blankname.linc.lan?
Thanks for any guidance, and resources that would be helpful to a hobbyist sysadmin.