...
In the previous article we enabled and checked IPv4 connectivity between all potential host within 192.168.128.0/17 and the outside Networks beyond ISP box. But, this is pretty useless as I can't imagine my kids typing IPv6 address (2001:8b0:0:30::666:102) in the browser in order to play a FUN puzzle. (Though for now we are suppose to have only IPv4 ) So we definitely need to provide name service resolution at the SOHO router itself.
...
Expand |
---|
title | Configure DNS into DHCP to propogate default "local" zone |
---|
|
Step -4-, configure DNS and DHCP to propagate default dummy zone local - Use local if you don't plan to propagate a domain name
- create local as dummy zone
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
title | Propagate "local" zone |
---|
| !
server dhcp4 dh4-inet
dns-server 192.168.254.1
domain-name local
exit
!
server dns ns-inet
zone local
exit
! |
|
Verification
Expand |
---|
title | step -1- and step -2- outcomes |
---|
|
When -1- and -2- are realised the router can resolve name Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
title | DNS resolution from CLI (DNS query originated by router) |
---|
| ping www.free.fr /vrf inet
pinging 212.27.48.10, src=null, vrf=inet, cnt=5, len=64, tim=1000, ttl=255, tos=0, sweep=false
!!!!!
result=100%, recv/sent/lost=5/5/0, rtt min/avg/max/total=3/3/4/16 |
|
Expand |
---|
title | step -3- and step -4- outcomes |
---|
|
This can be verified only using a host connected to SOHO router. Let's assume a laptop connected behind sdn6. Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
title | ping & ping6 hostname |
---|
| ...
╭─[10/31/20|3:01:19]loui@MacBook-Pro-de-Frederic.local ~
╰─➤ ping www.free.fr
PING www.free.fr (212.27.48.10): 56 data bytes
64 bytes from 212.27.48.10: icmp_seq=0 ttl=57 time=3.670 ms
64 bytes from 212.27.48.10: icmp_seq=1 ttl=57 time=6.666 ms
64 bytes from 212.27.48.10: icmp_seq=2 ttl=57 time=6.163 ms
64 bytes from 212.27.48.10: icmp_seq=3 ttl=57 time=6.118 ms
^C
--- www.free.fr ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 3.670/5.654/6.666/1.166 ms
╭─[10/31/20|3:40:12]loui@MacBook-Pro-de-Frederic.local ~
╰─➤ ping6 www.free.fr
PING6(56=40+8+8 bytes) 2a01:e0a:159:2857:b9d9:e9e0:ae30:88e5 --> 2a01:e0c:1::1
16 bytes from 2a01:e0c:1::1, icmp_seq=0 hlim=56 time=3.805 ms
16 bytes from 2a01:e0c:1::1, icmp_seq=1 hlim=56 time=6.898 ms
16 bytes from 2a01:e0c:1::1, icmp_seq=2 hlim=56 time=5.868 ms
16 bytes from 2a01:e0c:1::1, icmp_seq=3 hlim=56 time=5.729 ms
^C
--- www.free.fr ping6 statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 3.805/5.575/6.898/1.117 ms
...
|
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
title | IPv4 / IPv6 name resolution |
---|
| ...
╭─[10/31/20|3:42:11]loui@MacBook-Pro-de-Frederic.local ~
╰─➤ dig www.free.fr 127 ↵
; <<>> DiG 9.10.6 <<>> www.free.fr
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25030
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.free.fr. IN A
;; ANSWER SECTION:
www.free.fr. 20961 IN A 212.27.48.10
;; Query time: 21 msec
;; SERVER: 192.168.254.1#53(192.168.254.1)
;; WHEN: Sat Oct 31 15:42:18 CET 2020
;; MSG SIZE rcvd: 56
╭─[10/31/20|3:42:18]loui@MacBook-Pro-de-Frederic.local ~
╰─➤ dig AAAA www.free.fr
; <<>> DiG 9.10.6 <<>> AAAA www.free.fr
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21770
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.free.fr. IN AAAA
;; ANSWER SECTION:
www.free.fr. 21075 IN AAAA 2a01:e0c:1::1
;; Query time: 5 msec
;; SERVER: 192.168.254.1#53(192.168.254.1)
;; WHEN: Sat Oct 31 15:42:29 CET 2020
;; MSG SIZE rcvd: 68
...
|
Note |
---|
As said IPv6 verification are just FYI, as we are supposed to have deployed only IPv4 till now. The point to show off IPv6 verification is to verify DNS AAAA request are working properly. |
|
Conclusion
In this article DNS service has been enabled at:
...