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!
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.
I want to configure DNS server in 172.16.81.6. After the complete installation and configuration of DNS server, I want all my users to browse the internet by giving DNS IP 172.16.81.6 in their systems. Without giving the DNS IP 172.16.81.6 n their system, the users should not be able to browse the internet. For this, should I need to map 172.16.81.6 with the DNS IP given by ISP or just configuring DNS server in 172.16.81.6 will work?? Please help.
I want to configure DNS server in 172.16.81.6. After the complete installation and configuration of DNS server, I want all my users to browse the internet by giving DNS IP 172.16.81.6 in their systems. Without giving the DNS IP 172.16.81.6 n their system, the users should not be able to browse the internet. For this, should I need to map 172.16.81.6 with the DNS IP given by ISP or just configuring DNS server in 172.16.81.6 will work?? Please help.
Not alot to help WITH. Use your internal DHCP server to set the DNS configuration on your clients...that's one thing DHCP does by itself.
However, you do realize that if you don't do anything else but that, your users can still access the internet, right?? All they have to do is use Google's DNS servers (entering them manually), or just put IP addresses of sites in their browsers, and off they go. Aside from modifying your DHCP server to point to your own internal DNS server, put a proxy server in place to prevent folks from getting straight out to the internet.
As per your advice, if I use my internal DHCP server to set the DNS configuration on the clients, then the client system will take my internal DNS IP 172.16.81.6 automatically from DHCP and finally they will be able to access the internet only through my internal DNS IP right???????
and the second option, as you said, I can use the proxy server also.
Hi,
As per your advice, if I use my internal DHCP server to set the DNS configuration on the clients, then the client system will take my internal DNS IP 172.16.81.6 automatically from DHCP and finally they will be able to access the internet only through my internal DNS IP right???????
No, that's NOT what I said. I said that you can use your DHCP server to SET your clients DNS server, that's all. Again, all that's going to do is make name resolution not work, but they can STILL manually use Google's DNS servers, or put in IP addresses instead of names, and get right out.
Quote:
and the second option, as you said, I can use the proxy server also.
It's not an option. If you want to prevent users from getting to the Internet, filter websites, etc., you NEED a proxy of some sort. Just using internal DNS to restrict web traffic is very futile, and is just doing work for no real result.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.