Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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 have a webserver with a control panel that lets the user change there dns setting for there domain. To automate this to the other servers, do I make the webserver/dns server the primary and it updates the secondaries or how would you suggest this been done.
Yes, the changes are made only to the master DNS server, and they propagate out to the slaves. It doesn't matter if the webserver is the master or not, but the master should be the only one changed. When you update the domain, BIND will notify the slaves, or the slaves will check the master.
Yes, the changes are made only to the master DNS server, and they propagate out to the slaves. It doesn't matter if the webserver is the master or not, but the master should be the only one changed. When you update the domain, BIND will notify the slaves, or the slaves will check the master.
Peace,
JimBass
Can there be more than once master? Such as host1 host2 being dns servers and they would have to be primaries for users to update them in there control panel and then it gets sent out to some of the secondaries. Would this cause confusing between the two primaries or should there another way to set this up.
You only have one primary, and as many slaves as you want. You REALLY don't want two primaries, as it will cause major problems. Say you change an IP on one primary, but not the other. Some slaves will get the update, some will look to the one that isn't updated, and it becomes a mess. Then a legitimate query to your nameservers will be answered differently based on which one it queries.
Simply set things up so that whatever change the user makes goes only to the primary. It then is replicated to the slaves.
You only have one primary, and as many slaves as you want. You REALLY don't want two primaries, as it will cause major problems. Say you change an IP on one primary, but not the other. Some slaves will get the update, some will look to the one that isn't updated, and it becomes a mess. Then a legitimate query to your nameservers will be answered differently based on which one it queries.
Simply set things up so that whatever change the user makes goes only to the primary. It then is replicated to the slaves.
Peace,
JimBass
when making mutiple hosting computers on a rack which each has its own dns configuration that can be changed by the users. Is there a way to make the host computers say 3 webhost computers update the users changes on a single/seperate dns server so then it can replicate.
I'm sorry, I'm not quite understanding what you're asking here. Whatever server is the primary needs to have its individual domain (a.k.a. zone) file modified by the control panel, then updated by rndc in BIND, which is very very likely to be your DNS program.
I don't use control panel on any of my servers, so I can't give you concrete steps to follow, but in theory it is as simple as giving this control panel the tools to modify the correct zone file, and it is done. Once the master gets the new info, it will quickly replicate on the slaves.
I'm sorry, I'm not quite understanding what you're asking here. Whatever server is the primary needs to have its individual domain (a.k.a. zone) file modified by the control panel, then updated by rndc in BIND, which is very very likely to be your DNS program.
I don't use control panel on any of my servers, so I can't give you concrete steps to follow, but in theory it is as simple as giving this control panel the tools to modify the correct zone file, and it is done. Once the master gets the new info, it will quickly replicate on the slaves.
Peace,
JimBass
So I should be able to somehoe have the control pannel use the dns file on a remote server which would be the primary.
It doesn't matter if the DNS server is remote or the same machine, the use of rndc keys allow for secure updates from the same machine or across the net. Just configure the control panel to use the rndc key for the zone, and it will update.
If they are the same machine or not doesn't matter, it still will take rndc keys to change the zone file, and reload it with the new info.
It doesn't matter if the DNS server is remote or the same machine, the use of rndc keys allow for secure updates from the same machine or across the net. Just configure the control panel to use the rndc key for the zone, and it will update.
If they are the same machine or not doesn't matter, it still will take rndc keys to change the zone file, and reload it with the new info.
Peace,
JimBass
With my current DNS setup I have 3 windows servers. When adding a zone to the primary I had to add secondary zones on the scondaries. Is there NE to automate that system too.
Not a straightforward one. Some people play with rsyncing the master named.conf to the slave, and then write a shell script to modify the named.conf from showing master to showing slave, and adding the master {i.p.add.ress;}; clause.
Also, they wouldn't be called secondary zones, secondary is usually used as a name for subdomains, which are like sub.domain.com, and go.domain.com. The proper term would be slave zones, as they follow the master. Unless you have thousands of zones, I would say do it by hand.
Not a straightforward one. Some people play with rsyncing the master named.conf to the slave, and then write a shell script to modify the named.conf from showing master to showing slave, and adding the master {i.p.add.ress;}; clause.
Also, they wouldn't be called secondary zones, secondary is usually used as a name for subdomains, which are like sub.domain.com, and go.domain.com. The proper term would be slave zones, as they follow the master. Unless you have thousands of zones, I would say do it by hand.
Peace,
JimBass
I would like to have two webhosting machines update what they would think is the slave but really is the primary. Of course once it updates that server it sends it out to the slaves. Otherwise I will not know what my hosting customers are doing so that I could update the dns.
Ok, something you are writing here is not making sense. The only thing that has to go in the named.conf is the full zone, which won't be a surprise to anyone. If their domain is host1.com, then you need only to mention host1.com in the master named.conf as a master, and host1.com as a slave on the slave's named.conf. Then anything they do with subdomains, mail exchangers, etc is all done within the existing zone. The only thing that would require an entry to named.conf after that would be if they purchase a new domain, host3.com.
I am getting the strong impression you're either trying to hide something from us, or you don't really have an understanding of how DNS works. I'm not saying that to attack or diminish what you are trying to do, but it just doesn't make sense. Please get a better understanding of DNS, this in particular makes no sense -
Quote:
two webhosting machines update what they would think is the slave but really is the primary
There is NO difference whatsoever to the outside world between a master and a slave DNS server. Both are authoritative for a given domain, their answer is valid. Master/slave only matters within the nameservers that are authoritative for a given domain, to see which gets the updates and which copies the updates. Some people even do hidden masters, where the master just sits off in space, and propagates the answers to the slaves, which are authoritative to the outside world, while the master isn't.
You also don't really need to know what your clients are doing with DNS, as it doesn't help our hurt in any way, but to resolve their domains. You can of course look and see what they are doing, but what on earth could they do that is bad? Oh look, search.host1.com points to google! How horrible!
Please post back if you have questions, I'm glad to help, but this is making less and less sense as it drags on.
Ok, something you are writing here is not making sense. The only thing that has to go in the named.conf is the full zone, which won't be a surprise to anyone. If their domain is host1.com, then you need only to mention host1.com in the master named.conf as a master, and host1.com as a slave on the slave's named.conf. Then anything they do with subdomains, mail exchangers, etc is all done within the existing zone. The only thing that would require an entry to named.conf after that would be if they purchase a new domain, host3.com.
I am getting the strong impression you're either trying to hide something from us, or you don't really have an understanding of how DNS works. I'm not saying that to attack or diminish what you are trying to do, but it just doesn't make sense. Please get a better understanding of DNS, this in particular makes no sense -
There is NO difference whatsoever to the outside world between a master and a slave DNS server. Both are authoritative for a given domain, their answer is valid. Master/slave only matters within the nameservers that are authoritative for a given domain, to see which gets the updates and which copies the updates. Some people even do hidden masters, where the master just sits off in space, and propagates the answers to the slaves, which are authoritative to the outside world, while the master isn't.
You also don't really need to know what your clients are doing with DNS, as it doesn't help our hurt in any way, but to resolve their domains. You can of course look and see what they are doing, but what on earth could they do that is bad? Oh look, search.host1.com points to google! How horrible!
Please post back if you have questions, I'm glad to help, but this is making less and less sense as it drags on.
Peace,
JimBass
Im sorry JimBass I will just tell you my setup and what I want to achieve. I have 2 webservers with BlueQuartz Cpanels on it. Od frouce these servers have dns on them and allows the users to change there dns records. However, I dont want to use these hosting computers as primary DNS server. How can I get there updates from these hosting servers to update my primary dns of there changes? There for it will update the 2 secondaries/.
the use of rndc keys allow for secure updates from the same machine or across the net. Just configure the control panel to use the rndc key for the zone, and it will update.
If the cpanel has its own DNS program built into it, then you could use that as a hidden master. Set up all three nameservers to be slaves to the DNS on the webservers, but don't make those public. On the registrars webpage, set the authoritative nameservers as the 3 you want people to query.
Or else, use rndc to update the remote nameservers directly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
