Hello :)

Thank you and Marco, Scott and Nick :)

So, Primary server is a caching server for our internal network with multiple zones (and websites and services) and secondary one is meant to automaticaly replace the primary DNS server in case of it is not able to fullfil its job so all can continue to work.

there is only one internal network here, so the two of it are on at different ips.

the secondary dns server is just that, a dns nothing more.

most of the websites and services are distributed on multiple servers.

all this is in house with 'secondary copy servers' somewhere else to assure service in case of their primary servers downtime :)

I am just curious, as the correct config for the secondary DNS, as if the main one is down and the secondary have not the complete config itself how can it take on the job of the primary one for the time of its repair ?

Regards,
Jeff

 18/11/2024 à 20:06, Ondřej Surý a écrit :
I think the good starting point is exactly the question that Marco asked - we have no idea what Jean-François is trying to achieve.

Ondrej
--
Ondřej Surý — ISC (He/Him)

My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours.

On 18. 11. 2024, at 19:59, Nick Tait via bind-users <bind- us...@lists.isc.org> wrote:


Hi Jeff.

This is a good starting point for setting up primary and secondary servers: https://bind9.readthedocs.io/en/stable/ chapter3.html#authoritative-name-servers <https:// bind9.readthedocs.io/en/stable/chapter3.html#authoritative-name-servers>
Nick.

On 19 Nov 2024, at 7:44 AM, Marco Moock <m...@dorfdsl.de> wrote:

Am Mon, 18 Nov 2024 19:03:55 +0100
schrieb Jean-François Bachelet <jfbache...@free.fr>:

just to be sure, in case we have two (internals) dns servers on the
same network (for the case of one is unavaillable), if I understand
well the docs, the two servers should have the exact same
configurations, appart that the secondary is stated as 'secondary'
and the first 'master'.

that for both confs and zones and etc...

It depends on what you want.
A DNS server can do different tasks.
One is serving authoritative information.

For one zone (e.g. example.org), there exists a master and there can
exist slaves (also called secondary).

If you have multiple zones, a server can be master for one zone and
slave for another.

Other settings like recursive resolving for your clients can have
completely independent setting, depending on your needs.

You need to tell us more what you want to accomplish.
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Reply via email to