Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
How do I configure the private-network "DNS names" associated with DHCP connected devices? It is important that any solution work within my home-office, small-business LAN without causing the device trouble when on some other LAN.
Is there some way to configure DHCP-clients to ask for a specific name string, or does the following describe the only process?
When a workstation asks to connect, I can configure DCHP server to use its MAC address to cause it to always get the same private-network IP address.
I can create my own private-network zone file that uses that IP address.
I can configure so that my private-network DNS server will enable using those names for interactions between and among my workstations.
I can configure so that my workstations will reference my private-network DNS server
NOTE -- All of this happens on the in-house side of my gateway-router. This ISP-supplied box provides some sort of DNS for the in-house LAN. I have more questions about configuring the interactions between my home-office, small-business DNS server and this ISP-supplied box.
Having an inhouse DNS server creates issues. Why not use /etc/hosts? That takes names. Your workstations should not need a private dns server to communicate. /etc/hosts handled the entire internet at one stage. (I have seen a 200k /etc/hosts from the 70s).
Having an inhouse DNS server creates issues. Why not use /etc/hosts? That takes names. Your workstations should not need a private dns server to communicate. /etc/hosts handled the entire internet at one stage. (I have seen a 200k /etc/hosts from the 70s).
I also want to run an in-house email server with IMAP support:
gathers family and small-business email from all over the net onto local server
locally scrub email and attachments for scum-ware
home-office, small-business LAN clients interact with local email server
to read messages
local server processing would help manage local IMAP folders
local IMAP server would sync with online IMAP servers (where email most likely came from to begin with)
You want to run a regular network in house with a cheap internet connection. Fine. Do it. Designate a box as firewall/server (and it doesn't have to be big or powerful for a small network) and go to it.
The firewall/server would have the internet connection, block spam/other crap, and act as server. Security is less than top class this way, but you should be ok. The modem would only see one box, and all should work nicely.
This simplifies because only one box sees the modem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
