{"id":21140203,"url":"https://github.com/kurosaki1976/bind9-views","last_synced_at":"2025-09-08T03:39:17.029Z","repository":{"id":197242433,"uuid":"218537233","full_name":"kurosaki1976/bind9-views","owner":"kurosaki1976","description":"Servidor DNS Bind9 con vistas","archived":false,"fork":false,"pushed_at":"2024-01-26T01:46:48.000Z","size":95,"stargazers_count":5,"open_issues_count":0,"forks_count":2,"subscribers_count":4,"default_branch":"master","last_synced_at":"2025-07-09T04:38:03.093Z","etag":null,"topics":["bind","bind9","bind9-views","debian","dns","dns-views","forward-lookup-zone","forward-zone","reverse-lookup","reverse-lookup-zone","reverse-zone","vistas-dns","zona-directa","zona-inversa"],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/kurosaki1976.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null}},"created_at":"2019-10-30T13:44:13.000Z","updated_at":"2024-03-26T18:28:45.000Z","dependencies_parsed_at":null,"dependency_job_id":"85ed235a-430c-484f-9a87-3df861aa104d","html_url":"https://github.com/kurosaki1976/bind9-views","commit_stats":null,"previous_names":["kurosaki1976/bind9-views"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/kurosaki1976/bind9-views","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kurosaki1976%2Fbind9-views","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kurosaki1976%2Fbind9-views/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kurosaki1976%2Fbind9-views/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kurosaki1976%2Fbind9-views/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/kurosaki1976","download_url":"https://codeload.github.com/kurosaki1976/bind9-views/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kurosaki1976%2Fbind9-views/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":274129672,"owners_count":25227264,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-09-08T02:00:09.813Z","response_time":121,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["bind","bind9","bind9-views","debian","dns","dns-views","forward-lookup-zone","forward-zone","reverse-lookup","reverse-lookup-zone","reverse-zone","vistas-dns","zona-directa","zona-inversa"],"created_at":"2024-11-20T07:08:46.364Z","updated_at":"2025-09-08T03:39:16.984Z","avatar_url":"https://github.com/kurosaki1976.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# Configuración de un servidor DNS Bind9 con vistas en Debian 12\r\n\r\n## Autor\r\n\r\n- [Ixen Rodríguez Pérez - kurosaki1976](ixenrp1976@gmail.com)\r\n\r\n## Resumen\r\n\r\nEl objetivo de esta guía es mostrar cómo configurar un servidor `DNS Bind9` que brinde información distinta tanto a redes privadas como públicas, mediante el uso de la funcionalidad de vistas (`views`). Como tutorial en sí, se le guiará a través de todo el proceso de configuración, pero se requieren conocimientos iniciales de `DNS` y `Bind9`. En las [referencias](#referencias), encontrará enlaces a sitios de `Internet` que le pueden ayudar.\r\n\r\n\u003e **NOTA**: La implementación de esta configuración ayuda a los administradores de red cubanos a mitigar la vulnerabilidad `DDoS por Amplificación de DNS`, notificada por la OSRI, como consecuencia de la recursividad en servidores DNS.\r\n\r\n## Escenario\r\n\r\nEs común encontrarnos entornos de red, donde se necesite que un mismo servidor de nombres `DNS` devuelva registros tanto de tipo canónico como direcciones `IP`, dependiendo de la red desde donde se originen las consultas. Por ejemplo:\r\n\r\nExistencia de un servidor `DNS` dentro del direccionamiento `TCP/IP` de la subred de servicios, o cómo se le conoce comúnmente red `DMZ`, que da servicio a redes públicas (`Internet`, la red externa del provedor `ISP` o la `VPN` externa de una organización) y redes privadas (`Intranet` o red `LAN`, una `DMZ`, una `VPN` interna, o a todas ellas). Si se realiza la consulta desde el exterior, deben devolverse los registros públicos; sin embargo, si se hace la misma consulta desde cualquiera de las subredes internas, la resolución deberá ser a un registro privado. Esto es posible lograrlo, gracias a la funcionalidad de vistas (`views`) en `Bind9`.\r\n\r\n## Administración del servidor\r\n\r\nEl servidor `DNS` de ejemplo utilizá los siguientes parámetros de configuración de red:\r\n\r\n* Dirección `IP` del servidor: `192.168.0.1`\r\n* Dominio `DNS`: `example.tld`\r\n* `FQDN` del servidor: `ns.example.tld`\r\n* Subred interna de la zona de servicios: `192.168.0.0/24`\r\n* Subred externa para registros públicos: `172.16.0.0/29`\r\n\r\n### Ajustes de los parámetros de red\r\n\r\n```bash\r\nnano /etc/network/interfaces\r\n\r\nauto lo\r\niface lo inet loopback\r\n\r\nauto eth0\r\niface eth0 inet static\r\n    address 192.168.0.1/24\r\n    gateway 192.168.0.254\r\n    dns-nameservers 127.0.0.1\r\n```\r\n\r\n```bash\r\nnano /etc/resolv.conf\r\n\r\ndomain example.tld\r\nnameserver 127.0.0.1\r\n```\r\n\r\n```bash\r\nnano /etc/hosts\r\n\r\n127.0.0.1     localhost.localdomain   localhost\r\n192.168.0.1   ns.example.tld          ns\r\n```\r\n\r\n### Instalación\r\n\r\n```bash\r\napt install bind9 dnsutils\r\n```\r\n\r\nPara disponer de la documentación `off-line`, instalar además `bind9-doc`.\r\n\r\n### Configuración\r\n\r\nEn las distribuciones `Debian GNU/Linux`, los ficheros de configuración del paquete `bind9`, se encuentran en `/etc/bind`. Ellos son: `named.conf` (fichero de configuración principal), `named.conf.default-zones` (contiene las zonas predefinidas de reenvío (`forward`), inversa (`reverse`) y difusión (`broadcast`) para el `localhost`), `named.conf.options` (contiene todos los parámetros para la operación del servicio), y `named.conf.local` (contiene las opciones de configuración y las declaraciones de zonas del servidor `DNS` local).\r\n\r\n\u003e **NOTA**: Es importante leer el archivo **`/usr/share/doc/bind9/README.Debian.gz`**, para obtener información sobre la estructura de los archivos de configuración del servicio `BIND` en `Debian`. De igual forma es una buena práctica realizar copias de seguridad de los ficheros mencionados en el párrafo anterior en su estado por defecto, **ANTES** de realizar modificaciones.\r\n\r\n1. Editar fichero de configuración principal.\r\n\r\n```bash\r\ncp /etc/bind/named.conf{,.org}\r\nnano /etc/bind/named.conf\r\n```\r\n```bash\r\ninclude \"/etc/bind/named.conf.options\";\r\ninclude \"/etc/bind/named.conf.local\";\r\ninclude \"/etc/bind/named.conf.log\";\r\ninclude \"/etc/bind/rndc.key\";\r\n```\r\n\r\n2. Editar parámetros para la operación del servicio.\r\n\r\n```bash\r\ncp /etc/bind/named.conf.options{,.org}\r\nnano /etc/bind/named.conf.options\r\n```\r\n```bash\r\noptions {\r\n\tversion none;\r\n\tdirectory \"/var/cache/bind\";\r\n\tdnssec-validation auto;\r\n\tauth-nxdomain no;\r\n\tinterface-interval 0;\r\n\tlisten-on { 127.0.0.1; 192.168.0.1; };\r\n\tlisten-on-v6 { none; };\r\n\tallow-query { any; };\r\n\tempty-zones-enable no;\r\n\tforwarders { 8.8.8.8; 8.8.4.4; };\r\n\tforward first;\r\n\trecursion no;\r\n\tprefetch 0;\r\n\tpid-file \"/var/run/named/named.pid\";\r\n\tsession-keyfile \"/var/run/named/session.key\";\r\n\tminimal-responses yes;\r\n\tmax-cache-size 128m;\r\n    \trate-limit {\r\n        \tresponses-per-second 15;\r\n        \tlog-only no;\r\n    \t};\r\n\tmax-cache-ttl 60;\r\n\tmax-ncache-ttl 60;\r\n\tflush-zones-on-shutdown yes;\r\n};\r\ncontrols {\r\n\tinet 127.0.0.1 port 953\r\n\t   allow { localhost; 192.168.0.1; } keys { rndc-key; };\r\n};\r\n```\r\n\r\n3. Definir opciones de configuración y declaraciones de zonas del servidor `DNS`.\r\n\r\n```bash\r\ncp /etc/bind/named.conf.local{,.org}\r\nnano /etc/bind/named.conf.local\r\n```\r\n```bash\r\nacl \"INTRANET\"  { 192.168.0.0/24; };\r\nview \"private\" {\r\n\tmatch-clients { localhost; INTRANET; };\r\n\trecursion yes;\r\n\tallow-recursion { localhost; INTRANET; };\r\n\tallow-recursion-on { localhost; 192.168.0.1; };\r\n\tinclude \"/etc/bind/named.conf.default-zones\";\r\n\tzone \"example.tld\" {\r\n\t\ttype master;\r\n\t\tfile \"/etc/bind/db.example.tld_private\";\r\n\t\tallow-query { localhost; INTRANET; };\r\n\t\tallow-update { none; };\r\n\t\tnotify no;\r\n\t};\r\n\tzone \"0.168.192.IN-ADDR.ARPA\" {\r\n\t\ttype master;\r\n\t\tfile \"/etc/bind/db.0.168.192.in-addr.arpa\";\r\n\t\tallow-query { localhost; INTRANET; };\r\n\t\tallow-update { none; };\r\n\t\tnotify no;\r\n\t};\r\n};\r\nview \"public\" {\r\n\tmatch-clients { !INTRANET; any; };\r\n\trecursion no;\r\n\tinclude \"/etc/bind/named.conf.default-zones\";\r\n\tzone \"example.tld\" {\r\n\t\ttype master;\r\n\t\tfile \"/etc/bind/db.example.tld_public\";\r\n\t\tallow-query { any; };\r\n\t\tallow-update { none; };\r\n\t\tnotify no;\r\n\t};\r\n\tzone \"0.16.172.IN-ADDR.ARPA\" {\r\n\t\ttype master;\r\n\t\tfile \"/etc/bind/db.0.16.172.in-addr.arpa\";\r\n\t\tallow-query { any; };\r\n\t\tallow-update { none; };\r\n\t\tnotify no;\r\n\t};\r\n};\r\n```\r\n\r\n\u003e **NOTA**: Cuando se utiliza las funcionalidad de vistas, todas las definiciones de zonas **TIENEN** que estar contenidas dentro de éstas, de lo contrario el servicio no iniciará y generará códigos de error. Es por ello que el fichero **`/etc/bind/named.conf.default-zones`** fue incluido en cada definición de vista y no en el fichero de configuración principal.\r\n\r\n4. Crear ficheros de zonas.\r\n\r\nEl sistema `DNS` está compuesto por varios registros, conocidos como Registros de Recursos (`Resource Records` o `RR`, en Inglés), que definen la información en el sistema de nombres de dominio, tanto para resolución de nombre -conocida también como directa o canónica (conversión de nombre a dirección `IP`)-, como para resolución de nombre inversa (conversión de dirección `IP` a nombre).\r\n\r\n- Zona directa para consultas públicas\r\n\r\n```bash\r\nnano /etc/bind/db.example.tld_public\r\n```\r\n```bash\r\n;\r\n; example.tld Public Forward Zone\r\n;\r\n$ORIGIN .\r\n$TTL 1W\r\nexample.tld  IN  SOA ns.example.tld.  postmaster.example.tld. (\r\n                2019103101 ; serial\r\n                1H         ; refresh\r\n                10M        ; retry\r\n                2W         ; expire\r\n                1H         ; negative cache ttl\r\n                )\r\n;\r\n        NS  ns.example.tld.\r\n        A   172.16.0.2\r\n        MX  10  mail.example.tld.\r\n        TXT \"v=spf1 ip4:172.16.0.3 a:mail.example.tld ~all\"\r\n;\r\n$ORIGIN example.tld.\r\n$TTL 5M\r\nns    IN  A   172.16.0.2\r\nmail  IN  A   172.16.0.3\r\nwww   IN  A   172.16.0.4\r\njb    IN  A   172.16.0.5\r\n;\r\nsmtp        IN  CNAME   mail\r\nimap        IN  CNAME   mail\r\npop3        IN  CNAME   mail\r\nwebmail     IN  CNAME   mail\r\nconference  IN  CNAME   jb\r\n;\r\n$ORIGIN _udp.example.tld.\r\n$TTL 5M\r\n_domain   IN  SRV    5 0 53 ns.example.tld.\r\n;\r\n$ORIGIN _tcp.example.tld.\r\n$TTL 5M\r\n_domain IN    SRV    5 0 53 ns.example.tld.\r\n_http   IN    SRV    5 0 80 www.example.tld.\r\n_https  IN    SRV    5 0 443 www.example.tld.\r\n_smtp   IN    SRV   10 0 25 smtp.example.tld.\r\n_smtps  IN    SRV   10 0 465 smtp.example.tld.\r\n_imap   IN    SRV   10 0 143 imap.example.tld.\r\n_imaps  IN    SRV   10 0 993 imap.example.tld.\r\n_pop3   IN    SRV   10 0 110 pop3.example.tld.\r\n_pop3s  IN    SRV   10 0 995 pop3.example.tld.\r\n_submission  IN\tSRV    10 0 587 pop3.example.tld.\r\n_xmpp-client IN\tSRV\t5 0 5222 jb.example.tld.\r\n_xmpps-client IN SRV\t5 0 5223 jb.example.tld.\r\n_xmpp-server IN\tSRV     5 0 5269 jb.example.tld.\r\n;\r\n$ORIGIN _tcp.conference.example.tld.\r\n$TTL 5M\r\n_xmpp-server IN\tSRV     5 0 5269 jb.example.tld.\r\n```\r\n\r\n- Zona inversa para consultas públicas\r\n\r\n```bash\r\nnano /etc/bind/db.0.16.172.in-addr.arpa\r\n```\r\n```bash\r\n;\r\n; 0.16.172.in-addr.arpa Public Reverse Zone\r\n;\r\n$ORIGIN .\r\n$TTL 1W\r\n0.16.172.IN-ADDR.ARPA   IN  SOA ns.example.tld.  postmaster.example.tld. (\r\n                2019103101 ; serial\r\n                1H         ; refresh\r\n                10M        ; retry\r\n                2W         ; expire\r\n                1H         ; negative cache ttl\r\n                )\r\n;\r\n        IN  NS  ns.example.tld.\r\n;\r\n$ORIGIN 0.16.172.IN-ADDR.ARPA.\r\n$TTL 5M\r\n2   IN  PTR ns.example.tld.\r\n3   IN  PTR mail.example.tld.\r\n        PTR smtp.example.tld.\r\n        PTR imap.example.tld.\r\n        PTR pop3.example.tld.\r\n        PTR webmail.example.tld.\r\n4   IN  PTR www.example.tld.\r\n5   IN  PTR jb.example.tld.\r\n```\r\n\r\n- Zona directa para consultas privadas\r\n\r\n```bash\r\nnano /etc/bind/db.example.tld_private\r\n```\r\n```bash\r\n;\r\n; example.tld Public Forward Zone\r\n;\r\n$ORIGIN .\r\n$TTL 1W\r\nexample.tld  IN  SOA ns.example.tld.  postmaster.example.tld. (\r\n                2019103101 ; serial\r\n                1H         ; refresh\r\n                10M        ; retry\r\n                2W         ; expire\r\n                1H         ; negative cache ttl\r\n                )\r\n;\r\n        NS  ns.example.tld.\r\n        A   192.168.0.1\r\n        MX  10  mail.example.tld.\r\n        TXT \"v=spf1 ip4:192.168.0.2 a:mail.example.tld ~all\"\r\n;\r\n$ORIGIN example.tld.\r\n$TTL 5M\r\nns    IN  A   192.168.0.1\r\nmail  IN  A   192.168.0.2\r\nwww   IN  A   192.168.0.3\r\njb    IN  A   192.168.0.4\r\n;\r\nsmtp        IN  CNAME   mail\r\nimap        IN  CNAME   mail\r\npop3        IN  CNAME   mail\r\nwebmail     IN  CNAME   mail\r\nconference  IN  CNAME   jb\r\n;\r\n$ORIGIN _udp.example.tld.\r\n$TTL 5M\r\n_domain   IN  SRV    5 0 53 ns.example.tld.\r\n;\r\n$ORIGIN _tcp.example.tld.\r\n$TTL 5M\r\n_domain IN    SRV    5 0 53 ns.example.tld.\r\n_http   IN    SRV    5 0 80 www.example.tld.\r\n_https  IN    SRV    5 0 443 www.example.tld.\r\n_smtp   IN    SRV   10 0 25 smtp.example.tld.\r\n_smtps  IN    SRV   10 0 465 smtp.example.tld.\r\n_imap   IN    SRV   10 0 143 imap.example.tld.\r\n_imaps  IN    SRV   10 0 993 imap.example.tld.\r\n_pop3   IN    SRV   10 0 110 pop3.example.tld.\r\n_pop3s  IN    SRV   10 0 995 pop3.example.tld.\r\n_submission  IN    SRV   10 0 587 pop3.example.tld.\r\n_xmpp-client IN     SRV     5 0 5222 jb.example.tld.\r\n_xmpps-client IN     SRV     5 0 5223 jb.example.tld.\r\n_xmpp-server IN     SRV     5 0 5269 jb.example.tld.\r\n;\r\n$ORIGIN _tcp.conference.example.tld.\r\n$TTL 5M\r\n_xmpp-server IN  SRV     5 0 5269 jb.example.tld.\r\n```\r\n\r\n- Zona inversa para consultas privadas\r\n\r\n```bash\r\nnano /etc/bind/db.0.168.192.in-addr.arpa\r\n```\r\n```bash\r\n;\r\n; 0.168.192.in-addr.arpa Public Reverse Zone\r\n;\r\n$ORIGIN .\r\n$TTL 1W\r\n0.168.192.IN-ADDR.ARPA   IN  SOA ns.example.tld.  postmaster.example.tld. (\r\n                2019103101 ; serial\r\n                1H         ; refresh\r\n                10M        ; retry\r\n                2W         ; expire\r\n                1H         ; negative cache ttl\r\n                )\r\n;\r\n        IN  NS  ns.example.tld.\r\n;\r\n$ORIGIN 0.168.192.IN-ADDR.ARPA.\r\n$TTL 5M\r\n1   IN  PTR ns.example.tld.\r\n2   IN  PTR mail.example.tld.\r\n        PTR smtp.example.tld.\r\n        PTR imap.example.tld.\r\n        PTR pop3.example.tld.\r\n        PTR webmail.example.tld.\r\n3   IN  PTR www.example.tld.\r\n4   IN  PTR jb.example.tld.\r\n```\r\n\r\n5. Crear estructura para almacenamiento de trazas, bitácora de eventos.\r\n\r\n```bash\r\nmkdir -p /var/log/named/\r\nchown -R bind /var/log/named/\r\nchmod u+rw /var/log/named/\r\nnano /etc/bind/named.conf.log\r\n```\r\n```bash\r\nlogging {\r\n     channel default_syslog {\r\n             syslog local2;\r\n     };\r\n     channel audit_log {\r\n             file \"/var/log/named/audit.log\" size 10m;\r\n             severity debug;\r\n             print-category yes;\r\n             print-severity yes;\r\n             print-time yes;\r\n     };\r\n     channel requests_log {\r\n             // DNS requests logging\r\n             file \"/var/log/named/requests.log\" size 10m;\r\n             severity debug;\r\n             print-time yes;\r\n             print-category yes;\r\n             print-severity yes;\r\n     };\r\n     channel null {\r\n             null;\r\n     };\r\n     category default { default_syslog; };\r\n     category general { audit_log; };\r\n     category security { audit_log; };\r\n     category config { audit_log; };\r\n     category resolver { audit_log; };\r\n     category xfer-in { audit_log; };\r\n     category xfer-out { audit_log; };\r\n     category notify { audit_log; };\r\n     category client { audit_log; };\r\n     category network { audit_log; };\r\n     category update { audit_log; };\r\n     category queries { requests_log; audit_log; };\r\n     category lame-servers { null; };\r\n};\r\n```\r\n\r\n- Definir rotación de los archivos de bitácora.\r\n\r\n```bash\r\nnano /etc/logrotate.d/named\r\n```\r\n```bash\r\n/var/log/named/audit.log {\r\n    daily\r\n    missingok\r\n    rotate 7\r\n    compress\r\n    delaycompress\r\n    notifempty\r\n    create 644 bind bind\r\n    postrotate\r\n        systemctl reload named \u003e /dev/null\r\n    endscript\r\n}\r\n\r\n/var/log/named/requests.log {\r\n    daily\r\n    missingok\r\n    rotate 7\r\n    compress\r\n    delaycompress\r\n    notifempty\r\n    create 644 bind bind\r\n    postrotate\r\n        systemctl reload named \u003e /dev/null\r\n    endscript\r\n}\r\n```\r\n\r\n6. Comprobar la existencia de errores tanto en la configuración como en los ficheros de zonas.\r\n\r\n```bash\r\nnamed-checkconf -z\r\nnamed-checkzone example.tld /etc/bind/db.example.tld_public\r\nnamed-checkzone 0.16.172.in-addr.arpa /etc/bind/db.0.16.172.in-addr.arpa\r\nnamed-checkzone example.tld /etc/bind/db.example.tld_private\r\nnamed-checkzone 0.168.192.in-addr.arpa /etc/bind/db.0.168.192.in-addr.arpa\r\n```\r\n\r\n7. Reiniciar servicios y realizar comprobaciones.\r\n\r\n```bash\r\nsystemctl restart logrotate named\r\ntail -fn100 /var/log/syslog\r\n```\r\n\r\n- Comprobar correcta ejecución del servidor\r\n\r\n```bash\r\nnetstat -tapn | grep 53\r\nnetstat -lptun\r\n```\r\n\r\n- Desde una red pública\r\n\r\n```bash\r\ndig example.tld\r\nnslookup -q=any example.tld\r\nhost 172.16.0.2\r\ndig -t SRV @example.tld _xmpp-server._tcp.example.tld\r\nhost -t SRV _imaps._tcp.example.tld\r\nhost -t MX example.tld\r\ntail -fn100 /var/log/named_query.log\r\ntail -fn100 /var/log/named.log\r\n```\r\n\r\n- Desde una red privada\r\n\r\n```bash\r\nnslookup example.tld\r\nhost ns.example.tld\r\ndig @127.0.0.1 -x 192.168.0.1\r\ndig -t SRV @example.tld _xmpp-client._tcp.example.tld\r\nhost -t SRV _domain._udp.example.tld\r\nhost -t NS example.tld\r\ntail -fn100 /var/log/named_query.log\r\ntail -fn100 /var/log/named.log\r\n```\r\n\r\n## Conclusiones\r\n\r\nCon la introducción en `Bind9` de la funcionalidad de vistas, otro mecanismo muy útil en entornos de red que brindan servicios detrás de cortafuegos, es posible presentar una configuración del servidor `DNS` distinta a varios dispositivos. Algo particularmente provechoso si se ejecuta un servidor que recibe consultas desde redes privadas y públicas como es el caso de `Internet`.\r\n\r\n## Referencias\r\n\r\n* [Bind9 - Debian Wiki](https://wiki.debian.org/Bind9)\r\n* [Understanding views in BIND 9, by example](https://kb.isc.org/docs/aa-00851)\r\n* [Internet Systems Consortium](https://www.youtube.com/user/ISCdotorg/videos)\r\n* [Two-in-one DNS server with BIND9](https://www.howtoforge.com/two_in_one_dns_bind9_views)\r\n* [Vistas (views) en el servidor DNS Bind9 ](https://www.josedomingo.org/pledin/2017/12/vistas-views-en-el-servidor-dns-bind9/)\r\n* [Limiting the Memory a Name Server Uses](https://flylib.com/books/en/2.684.1/limiting_the_memory_a_name_server_uses.html)\r\n* [SRV record](https://en.wikipedia.org/wiki/SRV_record)\r\n* [Services Record (SRV)](http://www.zytrax.com/books/dns/ch8/srv.html)\r\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkurosaki1976%2Fbind9-views","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fkurosaki1976%2Fbind9-views","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkurosaki1976%2Fbind9-views/lists"}