Skip to main content

utiliser les vues de BIND

Resolution variable de ""

Le but est de faire en sorte que
  • Depuis, "" resolve vers 111.222.333.444
  • Depuis, "" resolve vers 555.666.777.888
Globalement il s'agit d'utiliser les "view" de BIND.
Actuellement "" est une enregistrement de type A dans la zone "".


Il y a deja 2 serveurs BIND en production, que nous appellerons "NS1" et "NS2"
Les vues ne seront opérationelles que sur "NS2", si le client fait directement sa requete sur "NS2".

Déléguer les DNS

Dans NS1, /etc/bind/hosts/masters/
 smtp IN NS smtp IN NS 
Penser à supprimer les enregistrements A!
"" n'est plus un simple enregistrement, mais maintenant une zone.

Créer la zone

sur NS1

Dans /etc/bind/named.conf.local:
 zone "" {  type master;  file "/etc/bind/hosts/masters/";  allow-query { any; };  }; 
Dans /etc/bind/hosts/masters/
 $ttl 38400      IN      SOA (                        2010041501                        10800                        3600                        604800                        38400 ) @   IN NS @   IN NS @ 1 IN  A 111.222.333.444 

sur NS2

Dans /etc/bind/named.conf.local, créer la zone slave "":
 zone "" {         type slave;         file "";         masters {       ;                 };         allow-query { any; };         }; 
Dans /etc/bind/named.conf.options, dans chaque vue existante, créer des zones master:
 view "les-1" {         match-clients { ; }; [...]         zone "" {                 type master;                 file "/etc/bind/hosts/masters/";                 allow-query { any; };         }; }; 
 view "les-2" {         match-clients { ; }; [...]         zone "" {                 type master;                 file "/etc/bind/hosts/masters/";                 allow-query { any; };         }; }; 

Dans les fchiers de "vues"


 $ttl 38400      IN      SOA (                         2010041501                         10800                         3600                         604800                         38400 ) @ IN NS @ IN NS @ 1 IN A 111.222.333.444 


 $ttl 38400      IN      SOA (                         2010041501                         10800                         3600                         604800                         38400 ) @ IN NS @ IN NS @ 1 IN A 555.666.777.888 


Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href=''" parameter. npm run build --base-href=' did not set the base href in indext.html After looking for a while, I found where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='

dockerfile multiline to file

Outputing a multiline string from Dockerfile I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian. But I also have a local mirror and would like to use it for packages installation. Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file. Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write. Here you are: RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl= " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 &quo

Gnome VNC Grey Checkboxes

When setting up VNC server in Gnome, I get a grey screen (or a black one) and the checkboxes to "Accept clipboard from viewers", "Send clipboard to viewers", "Send primary selection to viewers". I'm setting up a VNC server on a Debian 10 machine that has Gnome environment. A zillion articles can be found on Internet, they have the same global path: Install Gnome and GDM Install TigerVNC Setup the VNC Server: password + startup Run the server Connect from the client One of them is this TeknoTut how-to I took inspiration from. The tutorial is good, but I needed to complete it with extra steps in order to make it work: If the current user has already a running Gnome session, I just get the "grey screen with the checkboxes". It is good to know that: The "grey screen" is due to the "xsetroot" command that can be seen in some howtos The checkboxes are due to the "vncconfig -iconic &" command