1 1 1 1 dns

IPv6Provider: 2.dnscrypt-cert.quad9.netIP: [2620:fe::fe:9]:8443Quad9 Secured w/ECS: Malware blocking, DNSSEC Validation, ECS enabledPreferred IPv4 DNS server 9.9.9.11Alternate IPv4 DNS server 149.112.112.11Preferred IPv6 DNS server 2620:fe::11Alternate IPv6 DNS server 2620:fe::fe:11DNS over TLS (DoT) tls://dns11.quad9.netDNS over HTTPS (DoH) Unsecured: No Malware blocking, no DNSSEC validation (for experts only!)Preferred IPv4 DNS server 9.9.9.10Alternate IPv4 DNS server 149.112.112.10Preferred IPv6 DNS server 2620:fe::10Alternate IPv6 DNS server 2620:fe::fe:10DNS over TLS (DoT) tls://dns10.quad9.netDNS over HTTPS (DoH) [AS36692]:Cisco OpenDNSPreferred IPv4 DNS server 208.67.222.222Alternate IPv4 DNS server 208.67.220.220 Preferred IPv6 DNS server 2620:119:35::35Alternate IPv6 DNS server 2620:119:53::53 DNSCrypt IPv4 Provider: 2.dnscrypt-cert.opendns.com IP: 208.67.220.220 DNSCrypt IPv6 Provider: 2.dnscrypt-cert.opendns.com IP: [2620:0:ccc::2]DNS over HTTPS (DoH) OpenDNS (FamilyShield)Preferred IPv4 DNS server 208.67.222.123Alternate IPv4 DNS server 208.67.220.123DNSCrypt IPv4Provider: 2.dnscrypt-cert.opendns.com IP: 208.67.220.123DNS over HTTPS (DoH) [AS205157]:CleanBrowsing (Family filter)Preferred IPv4 DNS server 185.228.168.168:853Alternate IPv4 DNS server 185.228.169.168:853Preferred IPv6 DNS server [2a0d:2a00:1::]:853Alternate IPv6 DNS server [2a0d:2a00:2::]:853DNS over TLS (DoT) tls://family-filter-dns.cleanbrowsing.orgDNS over HTTPS (DoH) (Adult filter)Preferred IPv4 DNS server 185.228.168.10:853Alternate IPv4 DNS server 185.228.169.11:853Preferred IPv6 DNS server [2a0d:2a00:1::1]:853Alternate IPv6 DNS server [2a0d:2a00:2::1]:853DNS over TLS (DoT) tls://adult-filter-dns.cleanbrowsing.orgDNS over HTTPS (DoH) (Security Filter)Preferred IPv4 DNS server 185.228.168.9:853Alternate IPv4 DNS server 185.228.169.9:853Preferred IPv6 DNS server [2a0d:2a00:1::2]:853Alternate IPv6 DNS server [2a0d:2a00:2::2]:853DNS over TLS (DoT) tls://security-filter-dns.cleanbrowsing.orgDNS over HTTPS (DoH) [AS13238]:Yandex.DNS (Basic)Preferred IPv4 DNS server 77.88.8.8Alternate IPv4 DNS server 77.88.8.1Preferred IPv6 DNS server 2a02:6b8::feed:0ffAlternate IPv6 DNS server 2a02:6b8:0:1::feed:0ffYandex.DNS (Safe)Preferred IPv4 DNS server 77.88.8.88Alternate IPv4 DNS server 77.88.8.2Preferred IPv6 DNS server 2a02:6b8::feed:badAlternate IPv6 DNS server 2a02:6b8:0:1::feed:badYandex.DNS (Family)Preferred IPv4 DNS server 77.88.8.7Alternate IPv4 DNS server 77.88.8.3Preferred IPv6 DNS server 2a02:6b8::feed:a11Alternate IPv6 DNS server 2a02:6b8:0:1::feed:a11Adguard [AS212772]:Adguard (Default)Preferred IPv4 DNS server 94.140.14.14Alternate IPv4 DNS server 94.140.15.15Preferred IPv6 DNS server 2a10:50c0::ad1:ffAlternate IPv6 DNS server 2a10:50c0::ad2:ffDNS over TLS (DoT) tls://dns.adguard.comDNS over HTTPS (DoH) quic://dns.adguard-dns.comAdguard (Family protection)Preferred IPv4 DNS server 94.140.14.15Alternate IPv4 DNS server 94.140.15.16Preferred IPv6 DNS server 2a10:50c0::bad1:ffAlternate IPv6 DNS server 2a10:50c0::bad2:ffDNS over TLS (DoT) tls://dns-family.adguard.comDNS over HTTPS (DoH) quic://family.adguard-dns.comAdguard (Non-filtering)Preferred IPv4

DNS Publico en GNU/LinuxConfigurar un DNS publico o mejor conocido como autoritativo. servidores DNS autoritativos son los servidores que dan respuestas a los servidores DNS recursivos. La respuesta que dan es la información de DNS esencial para cada sitio web (direcciones IP correspondientes, una lista de servidores de correo y otros registros DNS necesarios). En resumen, los servidores DNS autoritativos son los servidores que dan a los servidores DNS recursivos las respuestas correctas.En este laboratorio debe tener un dominio preferiblemente obtenido en la NIC (solo queremos el dominio, no un web hosting), en la NIC vamos a indicarle cual es el servidor(es) DNS autoritativos (nuestro servidor) para que este informado el TLD (Top level Domain). Nuestro servidor DNS autoritativo estara escuchando las peticiones TCP (transferencias de zonas) y UDP (consulta de registros) por el puerto 53, el router gama hogar lo configuramosComo estará configurado el laboratorioUn dominio adquirido en la NICUn router LINKSYS , puede ser cualquiera...!!192.168.1.10 -- Ubuntu 14.04.4, dns-01 -- bind9192.168.1.20 -- Ubuntu 14.04.4, dns-02 -- bind9Configuración del servidor DNS autoritativoConfiguremos la interfaz de red, (Importante que este como adaptador puente):# vi /etc/network/interfaces# The loopback network interfaceauto loiface lo inet loopback# The primary network interfaceauto eth0iface eth0 inet staticaddress 192.168.1.10netmask 255.255.255.0gateway 192.168.1.1dns-nameserver 192.168.1.1Cambiar el nombre del servidor.:# vi /etc/hostname dns-01Instalamos los paquetes.:# apt-get update && apt-get install openssh-server bind9 bind9-doc -yMás información, consulte la documentación /usr/share/doc/bind9/ , el man de named.conf (5) named (8).Despues de instalar.:# ls -ltotal 52-rw-r--r-- 1 root root 2389 Mar 8 10:24 bind.keys-rw-r--r-- 1 root root 237 Mar 8 10:24 db.0-rw-r--r-- 1 root root 271 Mar 8 10:24 db.127-rw-r--r-- 1 root root 237 Mar 8 10:24 db.255-rw-r--r-- 1 root root 353 Mar 8 10:24 db.empty-rw-r--r-- 1 root root 270 Mar 8 10:24 db.local-rw-r--r-- 1 root root 3048 Mar 8 10:24 db.root-rw-r--r-- 1 root bind 463 Mar 8 10:24 named.conf-rw-r--r-- 1 root bind 490 Mar 8 10:24 named.conf.default-zones-rw-r--r-- 1 root bind 165 Mar 8 10:24 named.conf.local-rw-r--r-- 1 root bind 890 Apr 20 18:56 named.conf.options-rw-r----- 1 bind bind 77 Apr 20 18:56 rndc.key-rw-r--r-- 1 root root 1317 Mar 8 10:24 zones.rfc1918Empezamos con el archivo principal.:# vi

Slowdns : fast tunneling tool : vpn over dns [ ] ( powered by tunnelguru)===============================*** delete "dnshelp.txt" file from inside /tg/misc folder if you dont want to see it everytime ****help: how to find the best working dns settings for your network:======================= tools ======================================free downloader tool: download file: modes =========================================mode 1> payloadlength = 150 - encoded dns name - txt with encoded response - select keep changing source port.mode 2> payloadlength = 250 - encoded dns name - txt without encoded response - select keep changing source port.mode 3> payloadlength = 250 - encoded dns name - null record - select keep changing source port.================================================================how?======select 1st dns server from the 2nd dropdown .it is your local isp dns server. to get better speed you should find out secondary dns server and append it with existing.[pls see below - how to find local isp secondary dns server]apart from your local isp dns server you can try other popular public dns server if those are working for you like - 8.8.8.8,8.8.4.4============step 1:=============set mode-1 and connect vpn. see if you can download above file using dap ( for 1 minutes )( note download speed )>if mode-1 worksset mode-2 and reconnect vpn. see if you can download above file using dap ( for 1 minutes )( note download speed )>if mode-2 works consider it as the best settings for you.>if mode-2 does not workset mode-3 and connect vpn. see if you can download ( for 1 minutes )( note download speed )>if mode-3 works

Con esta herramienta que le ayuda a entonar los valores de su DNS , si lo corren tal cual como esta esta configuración podrán ver que los warning se trata por convención que debe existir otro DNS autoritativo.NOTA: la zona inversa de su IP usted no pude controlarla, su ISP tiene que crearla. (Esto es muy importante si va tener correo con este su dominio por esta IP)Hasta aquí tenemos un DNS autoritativo funcional...!!!Ahora vamos a crear otro servidor DNS autoritativo pero que sea esclavo de nuestro primer DNS autoritativo. De ahora en adelante llamaremos Master al primer DNS autoritativo instalado y al siguiente Esclavo.Lo primero que vamos hacer es ir a la NIC y al dominio adquirido agregar otro servidor DNS. NICEn el servidor DNS EsclavoConfiguremos la interfaz de red, (Importante que este como adaptador puente):# vi /etc/network/interfaces# The loopback network interfaceauto loiface lo inet loopback# The primary network interfaceauto eth0iface eth0 inet staticaddress 192.168.1.20netmask 255.255.255.0gateway 192.168.1.1dns-nameserver 192.168.1.1Cambiar el nombre del servidor.:# vi /etc/hostname dns-02Instalamos los paquetes.:# apt-get update && apt-get install openssh-server bind9 bind9-doc -yMás información, consulte la documentación /usr/share/doc/bind9/ , el man de named.conf (5) named (8).Despues de instalar.:# ls -ltotal 52-rw-r--r-- 1 root root 2389 Mar 8 10:24 bind.keys-rw-r--r-- 1 root root 237 Mar 8 10:24 db.0-rw-r--r-- 1 root root 271 Mar 8 10:24 db.127-rw-r--r-- 1 root root 237 Mar 8 10:24 db.255-rw-r--r-- 1 root root 353 Mar 8 10:24 db.empty-rw-r--r-- 1 root root 270 Mar 8 10:24 db.local-rw-r--r-- 1 root root 3048 Mar 8 10:24 db.root-rw-r--r-- 1 root bind 463 Mar 8 10:24 named.conf-rw-r--r-- 1 root bind 490 Mar 8 10:24 named.conf.default-zones-rw-r--r-- 1 root bind 165 Mar 8 10:24 named.conf.local-rw-r--r-- 1 root bind 890 Apr 20 18:56 named.conf.options-rw-r----- 1 bind bind 77 Apr 20 18:56 rndc.key-rw-r--r-- 1 root root 1317 Mar 8 10:24 zones.rfc1918Ahora nos vamos al servidor Master y editamos el archivo "named.conf".:# vi /etc/bind/named.conf//// Do any local configuration here//// Consider adding the 1918 zones here, if they are not used in your// organization//include "/etc/bind/zones.rfc1918";root@dns-01:/etc/bind# cat named.conf// This is the primary configuration file for the BIND DNS server named.//// Please read /usr/share/doc/bind9/README.Debian.gz for information

SSL VPN SSL VPN configurations consist of one section, followed by one or more VPN sections: 1 0 1 1 1 0 0 0 0 1 SSLVPN_Name Optional_Description ssldemo.fortinet.com:10443 Encrypted/NonEncrypted_UsernameString 0 0 1 1 1 1 0 Encrypted/NonEncrypted_PasswordString 1 0 0 0 1 windows windows 1 2 %LOCALAPPDATA%\Microsoft\Teams\Current\Teams.exe %appdata%\Zoom\bin\Zoom.exe C:\Program Files (x86)\Microsoft\Skype for Desktop\skype.exe %LOCALAPPDATA%\GoToMeeting\18068\g2mcomm.exe %LOCALAPPDATA%\GoToMeeting\18068\g2mlauncher.exe %LOCALAPPDATA%\GoToMeeting\18068\g2mstart.exe webex.com gotomeeting.com youtube.com The following table provides the SSL VPN XML tags, as well as the descriptions and default values where applicable. XML tag Description Default value elements Enable SSL VPN. Boolean value: [0 | 1] 1 FortiClient disables Windows OS DNS cache when an SSL VPN tunnel is established. The DNS cache is restored after SSL VPN tunnel is disconnected. If you observe that FSSO clients do not function correctly when an SSL VPN tunnel is up, use to control the DNS cache. 0 When this setting is 0, the custom DNS server from SSL VPN is not added to the physical interface. When this setting is 1, the custom DNS server from SSL VPN is prepended to the physical interface. Boolean value: [0 | 1] 0 When this setting is 0, FortiClient uses the new SSL driver. When this setting is 1, FortiClient uses the legacy SSL driver. Boolean value: [0 | 1] 1 DTLS supported only by FortiClient (Windows). When this setting is 0, FortiClient uses TLS, even if dtls-tunnel is enabled on the FortiGate. When this setting is 1, FortiClient uses DTLS, if it is enabled on the FortiGate, and tunnel establishment is successful. If dtls-tunnel is disabled on the FortiGate, or tunnel establishment is not successful, FortiClient uses TLS. DTLS tunnel uses UDP instead of TCP and can increase throughput over VPN. Boolean value: [0 | 1] When this setting is 0, FortiClient allows IPv6 connection. When this setting is 1, FortiClient blocks IPv6 connection. FortiClient uses only IPv4 connectivity when the SSL VPN tunnel is up. Boolean value: [0 | 1] 0 When this setting is 0, FortiClient creates the DHCP public server route upon tunnel establishment. When this setting is 1, FortiClient does not create the DHCP public server route upon tunnel establishment. Boolean value: [0 | 1] 0 When this setting is 0, FortiClient registers the SSL VPN adapter's address in the Active Directory (AD) DNS server. When this setting is 1, FortiClient does not register the SSL VPN adapter's address in the AD DNS server. When this setting is 2, FortiClient registers only its own tunnel interface IP address in the AD DNS server. 0 When this setting is 0 and an invalid server certificate is used, FortiClient displays a popup that allows the user to continue with the invalid certificate. When this setting is 1 and an invalid server certificate is used, FortiClient does not display a popup and stops the connection. Boolean value: [0 | 1] 0 Retry restoring an active VPN session connection. Boolean value: [0 | 1] The XML tag may contain one or more elements. Each has the following: