Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
This isn't strictly a Linux question per se, but I expect Linux will be the solution, so this seems the place for it.
We have two servers. One local, one remote. All our domains resolve to the remote one. I want to synchronize these servers as much as possible. Since the configuration of the remote one relies on name based hosting, I would like to attempt to do the same locally.
Right now, all local DNS resolution is done through a cheapo linksys router. It doesn't seem to have the capability to manipulate DNS resolution. However, it can set what DNS server is used by computers it provides DHCP for.
On that note, I believe there must be some way to set up the local server as our primary DNS server, and have a switch somewhere on that server that will set all of our domains to resolve to itself. We would then use this switch when we were in the final stage of testing, to ensure there would be no problems with the domain. I'm certain this, or something approximating it, is possible.
My question is what is the best, simplest way to go about it?
I'm not sure I fully understood: you want to instruct your dns to resolve to a fixed host number of addresses, right?
This should be pretty simple: just change your /etc/hosts file or the listing file for named daemon. You may have to kill/respawn named
You can change your hosts file, but the machines on your network will not use this file restarting named will make no difference. If named is running on your system, then you already have bind installed. Install webmin for easy configuration.
It is also possible to use a firewall configuration to redirect clients to the local machine without them knowing it and without using a local DNS server.
I hope this info helps you solve your problem,
I want to be able to control DNS resolution on the local network. By default, I want to forward requests to a standard external server. But I would like to be able to also, when convenient for me, force DNS resolution on the local network to be done through my local server, which would contain alternate information for some of the domains owned by us.
So for DNS resolution on our local network 192.168.23.x
switch off: passive.com resolves to 184.108.40.206
switch on: passive.com resolves to 192.168.23.05
I would prefer to do this at the domain level, something my firewall cannot accomplish. If necessary, the firewill can do it at the ip level, but that would cut off a number of services that really on our external server.
What I want is a way to have enable/disable a set of zone files on my DNS server, in a very quick simple way.
I know this kind of rambled on a little, so thanks for reading.
I think you can solve your problem using two named servers, more exactly using two configurations for the named server. One assigning passive.com to the local server and the other to the remote server.
Then you can switch your DNS assignment restarting the server using the configuration file that suites your purpose. Or maybe by running a simple script that "see" if the remote server in reachable or not.