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='

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

Emacs TypeScript Development

Emacs Configuration for Typescript In order to comfortably develop on Node, React or Angular projects with Emacs, TIDE is a good solution. We have TypeScript code highlight (that is the minimum!) and code completion based on the codebase (not only on locally defined and builtins) In order to achieve that: Install Emacs (24+) Install Node Install Typescript (which will provide "tsserver") Install TIDE and some usefull dependencies Configure Emacs to use all those Node is then installed in " /home/mihamina/Apps/node-v12.18.0-linux-x64/bin ": you should add it to your PATH. Installing Typescript is done with: npm install --save typescript @types/browserify After that, "tsserver" will be in " /home/mihamina/node_modules/.bin " Then comes the installation of TIDE: With the Emacs package manager, M-x package-install , install "tide". Do the same for "web-mode", "flycheck", "company" "js2-mode" and "