how to configure bind when using dynamic dns for webserver
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 to configure bind when using dynamic dns for webserver
Hi everyone,
I am trying to configure a BIND DNS server to handle three websites on my home network, (my site, my sons site and our test site). Since my ISP uses dynamic DNS, we are using DNS2GO to redirect our traffic, 9EACH SERVER HAS IT'S OWN VERSION OF dns2go running).
My problem is that I can't figure out how to configure BIND since I don't have a static IP to enter into the named.conf or reslov.conf configuration files.
Don't use bind.
Assuming you have one router gateway to the net, point all port 80 requests at your "server" and use apache to forward requests for the other websites to the other machines. You can do that using entries in /etc/hosts if you want to use domain names.
eg in the root directory of your web server make an .htaccess file containing
Obviously amend the domain names and ip addresses as necessary.
BTW, running the update client on each machine is unnecessary and will get you warned about abusive updating. They all share the same public ip so only run the client on one machine.
Ok, this is what I am understanding form your reply;
Build another machine, (I am using Virtualbox to create virtual servers), then configure Apache to route the traffic to the other servers. The question I have is do I configure it as a proxy server or just the Apache server part?
I have no experience with Virtualbox, so I can't answer your question. In theory it should work exactly the same but in practice ...
I don't see the need for a proxy server anywhere.
As long as the name is pointed to the site then it should work. All requests coming through port 80 will go to the machine that the router forwards port 80 to. How you direct those requests from there is up to you. Assuming the virtualbox machines have routeable ip addresses then it should be no different.
It is only a couple of lines in an .htaccess file and a line in /etc/hosts to test it anyway ...
Sorry for the delay in responding to your post, been a little busy for the last day.
I am about to try what you have suggested, however, <i have a question before I get started.
Is it possible to use this method to redirect smtp and pop3 traffic, (along with any other services that I am running)? My servers have qmail running, along with http and ftp.
Googling for more info now, but if you had any suggestion, please let me know.
I don't think that will work with smtp and pop traffic. In that case you really need a gateway server to redirect traffic. If you go the bind route, you need to use something to rewrite your bind config when your public ip changes. Maybe there is a facility in your router you can query to get the new address ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.