BIND - named service for DNS

Configuring the Server side of DNS in CentOS 6. Using the named service (BIND). Provides and overview of how the service works and is configured.

[@Oswee]

This is so much goood!!! I like how you showcase how those pieces are tied together and what interacts with what.

[@jamesperez6964]

Love taking CS lessons from my hero Kenny Powers

[@PaperRaines]

I like this guy's style

[@louayalosh2402]

Thank you so much.... :D this video was super USEFUL

[@gerritweiermann79]

Thanks! Learned so much 👍

[@tweedle634]

you're a GOD!!!!!!!

[@ronwatkins5775]

Dumb question. I want to create a DNS server for my private network so I can resolve private IP's in my network, how is that done? This is not for external use, internal only.

[@osematouati4869]

awesome video. thnx man.

[@businesspromotion3167]

Little error I would like to correct: 86400 means 1 day not 60 days.

[@dennisaguilar4400]

what are the equivalent files on windows?

[@ranjithar9450]

Does it configure DNS root, authoritative and tld server?

[@Theborg72]

Hi this look easy
but after I installed my pi, it was not the same, tried your description. But couldn't make it work
You wouldn't be able to make one for raspberry and get it to work

[@alejandrosantacruz5379]

Awesome vid

[@SwapnilMantri]

helpfull video

[@SOGTULAKlamares]

Nice accent! Where are you from?

[@Akshay-xx7rg]

86400 seconds is just one day, not 60 days.

[@agenesis6761]

Great video thanks for the same
Frankly speaking I have seen lots and lots of videos on internet and community blogs for each service (Nginx, fail2ban, iptables , resolver , port forwarding etc, but not having that luck in accessing my website hosted on (DNS bought from service provider ClouDNS pointed “A” record to public IP address of my network) Raspberry Pi (which is on LAN) on WAN.
Will you be able to guide me?
-------------------------------------------------------------------------------------------------------------------------------------------- My setup (all are dummy ip addresses for illustration purpose).
-------------------------------------------------------------------------------------------------------------------------------1. my public IP - 777.333.111.222
2. my router WAN ip - 123.332.111.222
3. router gateway - 192.168.1.1 4. my raspberry pi Ubuntu 18.4 server ip - 192.168.1.222
5. my mac book from where I am using ssh to Raspberry pi - 192.168.1.111
6. My have dns (www.example.com) pointed to my Raspberry Pi web server 192.168.1.222 7. “A” record in DNS zone of www.example.com / example.com pointing to 777.333.111.222
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Raspberry Pi - Ubuntu setup - NGINX:
------------------------------------------------------------------------------------------------------------------------------- server { listen 61001;
listen [::]:61001;
server_name example.com www.example.com;
root /home/mastodon/live/public;
location /.well-known/acme-challenge/
{ allow all; } location / { return 301 $host$request_uri; } }
server { listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name example.com www.example.com; }
--------------------------------------------------------------------------------------------------------------------
Raspberry Pi - Ubuntu setup - UFW setup:
-------------------------------------------------------------------------------------------------------------------------------
ufw status Status: active To Action From -- ------ ----
10000 ALLOW Anywhere
Nginx Full ALLOW Anywhere
OpenSSH ALLOW Anywhere
61001 ALLOW Anywhere
10000 (v6) ALLOW Anywhere (v6)
Nginx Full (v6) ALLOW Anywhere (v6)
OpenSSH (v6) ALLOW Anywhere (v6)
61001 (v6) ALLOW Anywhere (v6)
-----------------------------------------------------------------------------------
Raspberry Pi - Ubuntu setup - Remote.it setup (This is to ensure that ports are opened and attached to the service
-----------------------------------------------------------------------------------
========================= Installed remote.it Services ======================
Service Name | Protocol | LAN Address | Port | Application -------------------------------------------------------------------------------
http-61001 | TCP | localhost | 61001 | OK: nginx: master
http-80 | HTTP | localhost | 80 | not detected
https-443 | Secure Web | localhost | 443 | OK: nginx: master
web-port-3000 | TCP | localhost | 3000 | OK
-------------------------------------------------------------------------------
BIND9 output for forward and reverse to my domain.
-------------------------------------------------
-checkconf -z /etc/bind/named.conf
zone example.com/IN: loaded serial 2
zone 1.168.192.in-addr.arpa/IN: loaded serial 2
zone localhost/IN: loaded serial 2
zone 127.in-addr.arpa/IN: loaded serial 1
zone 0.in-addr.arpa/IN: loaded serial 1
zone 255.in-addr.arpa/IN: loaded serial 1
-------------------------------------------------
-checkconf -z /etc/bind/named.conf.local
zone example.com/IN: loaded serial 2
zone 1.168.192.in-addr.arpa/IN: loaded serial 2
-------------------------------------------------------------
Check Forward ...........!
zone forward/IN: loaded serial 2
OK
-------------------------------------------------------------
Check Reverse ...........!
zone reverse/IN: loaded serial 2
OK
------------------
I have done setup in Linux on Raspberry Pi for my Nginx ports web-server port listen on port 80 and port 443. in No Ip its showing ports are actually listening on those ports with Ok status. Status check: I am able to access my raspberry Pi webpage from macbook which is in same LAN. Next objective: To able to access my webpage WAN - Public network/ 3g/4g mobile network
---------------------------
Router setup:
------------------------------------------------------------
in DNS I am using my no-ip setup in DDNS page and connection is successful In port fowarding page
I have entered following setup :
Service Name | External port. | Local IP | Local port | type
http | 80 | 192.168.1.222 | 80 | TCP/UDP
https | 443 | 192.168.1..222 | 443 |. TCP/UDP
https | 61001 | 192.168.1..222 | 61001 |. TCP/UDP
No success, I am unable to access my Raspberry Pi web-server on WAN /public network/outside of LAN network.
NOIP web configuration client check for port - showing port 80 /443 not open. does that mean its blocked by ISP or any other problem.
Thank you for reading through.
will you be able to guide where I am going wrong/ missing something.
Thanks in advance.
Thanks
AG

[@mishasawangwan6652]

mmm no.

[@varun3276]

86400 seconds is 24 hours not 60 days .

[@MagnificentImbecil]

Windows XP forever. >:D