Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
At Indiana University, UITS prohibits individuals and departments from setting up local DHCP servers on the IU network. Almost all wireless access points, many wired Ethernet routers, and computers running Internet Connection Sharing have built-in DHCP servers. While this makes configuration of a small network easier, it can cause problems when the DHCP servers are used in larger networks. Client computers configured to use DHCP for IP assignment do not need statically assigned IP addresses. In addition, they generally do not need to have addresses configured for DNS servers or WINS servers, as these are also set by the DHCP server. For more, see What are the DHCP operational policies at IU?
For the underlined sentence above, what problems can a
built-in DHCP server cause when used in a large network?
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
"nameserver 127.0.1.1" would mean DNS is 127.0.1.1, correct?
If so, why is DNS on local host?
It's really much the same thing that will happen if a "second" DHCP server is running anywhere, even in your own home or office network.
The problem is, simply, that when any newly-powered-on computer broadcasts, asking for an IP-address that it can use, it needs to hear from only one DHCP server, and from it receive the correct answer.
If more-than-one computer might "answer," it's unpredictable which one the new computer will hear from first, since that's the only reply that it will react to. If the answer comes from a computer that doesn't have the right answer ... that doesn't have a complete and accurate list of addresses that have been assigned and to whom they have been assigned ... very-unpredictable outcomes may occur including IP-address conflicts.
The University's policy is quite ordinary, and quite necessary for any (and every) TCP/IP subnet that offers DHCP.