Skip to main content

utiliser les vues de BIND

Resolution variable de "smtp.rktmb.org"

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

Prérequis

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/rktmb.org-hosts:
 smtp IN NS ns1.rktmb.org. smtp IN NS ns2.rktmb.org. 
Penser à supprimer les enregistrements A!
"smtp.rktmb.org" n'est plus un simple enregistrement, mais maintenant une zone.

Créer la zone

sur NS1

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

sur NS2

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

Dans les fchiers de "vues"

/etc/bind/hosts/masters/smtp.rktmb.org-1

 $ttl 38400 smtp.rktmb.org.      IN      SOA     ns1.rktmb.org. postmaster.rktmb.org. (                         2010041501                         10800                         3600                         604800                         38400 ) @ IN NS ns1.rktmb.org. @ IN NS ns2.rktmb.org. @ 1 IN A 111.222.333.444 

/etc/bind/hosts/masters/smtp.rktmb.org-2

 $ttl 38400 smtp.rktmb.org.      IN      SOA     ns1.rktmb.org. postmaster.rktmb.org. (                         2010041501                         10800                         3600                         604800                         38400 ) @ IN NS ns1.rktmb.org. @ IN NS ns2.rktmb.org. @ 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='https://ngx.rktmb.org/foo' 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='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 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='https://ngx.rktmb.org/foo&

Emacs Pulumi LSP

Install Pulumi Emacs Mode The source code is on https://github.com/pulumi/pulumi-lsp. At the very bottom of the page are the instructions on how to install. You Need to have make installed. $ make install emacs-client mkdir -p ./bin go build -ldflags "-X github.com/pulumi/pulumi-lsp/sdk/version.Version=v0.2.3-6-gec49054" -o ./bin -p 10 ./cmd/... go: downloading github.com/pulumi/pulumi/sdk/v3 v3.53.1 ... ... ... go install -ldflags "-X github.com/pulumi/pulumi-lsp/sdk/version.Version=v0.2.3-6-gec49054" ./cmd/... mkdir -p editors/emacs/bin cd editors/emacs && emacs -Q --batch --eval "(progn (setq package-user-dir \"$(pwd)/bin\" \ package-archives '((\"melpa\" . \"https://melpa.org/packages/\") \

emacs29 intelephense

Emacs 29 and PHP Intelephense I use to use Emacs and PHP Intelephense for PHP development. I recently upgraded to Emacs 29 and PHP Intelephense stopped working. I found a solution on Reddit Based on that, I rewrote my .emacs file to use eglot instead of lsp-mode, and this is the result. (use-package eglot :ensure t) (add-hook 'php-mode-hook 'eglot-ensure) (use-package php-mode :ensure t :mode ("\\.php\\'" . php-mode)) (add-to-list 'auto-mode-alist '("\\.php$" . php-mode)) (provide 'lang-php) (use-package company :ensure t :config (setq company-idle-delay 0.3) (global-company-mode 1) (global-set-key (kbd "M- ") 'company-complete)) (require 'eglot) (add-to-list 'eglot-server-programs '((php-mode :language-id "php") . ("intelephense" "--stdio" :initializationOptions (:licenseKey "98989898989898989898"