dns /var/named/rp.zone

[root@localhost ~]# cat /var/named/rp.zone
$TTL 1D
@   IN SOA          rp. root (
                                        1       ; serial
                                        1D      ; refresh
                                        1H      ; retry
                                        1W      ; expire
                                        0 )     ; minimum

        IN      NS      rp.
        IN      A       10.75.49.248
vcsa    IN      A       10.75.49.246
esx1    IN      A       10.75.49.253
esx2    IN      A       10.75.49.252
dns     IN      A       10.75.49.248

DNS /var/named/10.75.49.zone

[root@localhost ~]# cat /var/named/10.75.49.zone
$TTL 1D
@       IN SOA  dns.rp. dns.rp. (
                                        20171224      ; serial
                                        1D      ; refresh
                                        1H      ; retry
                                        1W      ; expire
                                        3H )    ; minimum
@                     NS       rp.
248             IN      PTR        dns.rp.
246             IN      PTR        vcsa.rp.
253             IN      PTR        esx1.rp.
252             IN      PTR        esx2.rp.

DNS /etc/named.rfc1912.zones

zone "rp" IN {
        type master;
        file "rp.zone";
        allow-update { none; };
};

zone "49.75.10.in-addr.arpa" IN {
        type master;
        file "10.75.49.zone";
        allow-update { none; };
};

DNS named.conf

[root@localhost ~]# cat /etc/named.conf
//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
// See the BIND Administrator's Reference Manual (ARM) for details about the
// configuration located in /usr/share/doc/bind-{version}/Bv9ARM.html

options {
        listen-on port 53 { any; };
        listen-on-v6 port 53 { ::1; };
        directory       "/var/named";
        dump-file       "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
        memstatistics-file "/var/named/data/named_mem_stats.txt";
        recursing-file  "/var/named/data/named.recursing";
        secroots-file   "/var/named/data/named.secroots";
        allow-query     { any; };
        forwarders      { 64.104.123.245; };

        /*
         - If you are building an AUTHORITATIVE DNS server, do NOT enable recursion.
         - If you are building a RECURSIVE (caching) DNS server, you need to enable
           recursion.
         - If your recursive DNS server has a public IP address, you MUST enable access
           control to limit queries to your legitimate users. Failing to do so will
           cause your server to become part of large scale DNS amplification
           attacks. Implementing BCP38 within your network would greatly
           reduce such attack surface
        */
        recursion yes;

        dnssec-enable no;
        dnssec-validation no;

        /* Path to ISC DLV key */
        bindkeys-file "/etc/named.iscdlv.key";

        managed-keys-directory "/var/named/dynamic";

        pid-file "/run/named/named.pid";
        session-keyfile "/run/named/session.key";
};

logging {
        channel default_debug {
                file "data/named.run";
                severity dynamic;
        };
};

zone "." IN {
        type hint;
        file "named.ca";
};

include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";

log time no sysc to system time

Add the [localtime] option to the service timestamps log command. For example, if the current configuration is service timestamps log datetime, issue this global configuration command:

router(config)#service timestamps log datetime localtime
router(config)#^Z (ctrl z to exit)
router#write mem

The times should now be synchronized between the system clock and the log message timestamps.

ASR1001-X enter shell

ASR1001X-A#request platform software system shell
% Error: Shell access is not available

ASR1001X-A#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
ASR1001X-A(config)#pla
ASR1001X-A(config)#platform sh
ASR1001X-A(config)#platform shell ?
  <cr>

ASR1001X-A(config)#platform shell
ASR1001X-A(config)#exit
ASR1001X-A#request platform software system shell

*Jun 26 00:29:04.564: %SYS-5-CONFIG_I: Configured from console by consoleActivity within this shell can jeopardize the functioning of the system.
Are you sure you want to continue? [y/n] y

2019/06/26 00:29:07 : Shell access was granted to user <anon>; Trace file: , /harddisk/tracelogs/system_shell_R0.log.20190626002907
**********************************************************************
Activity within this shell can jeopardize the functioning
of the system.
Use this functionality only under supervision of Cisco Support.
Only RP shell access is available for this platform.

Session will be logged to:
  harddisk:tracelogs/system_shell_R0.log.20190626002907
**********************************************************************
Terminal type 'network' unknown.  Assuming vt100
[ASR1001X-A_RP_0:/]$
*Jun 26 00:29:08.658: %SYSTEM-3-SYSTEM_SHELL_LOG: SIP0:  Shell started: con 0
*Jun 26 00:29:08.659: %SYSTEM-3-SYSTEM_SHELL_LOG: SIP0:  2019/06/26 00:29:07 : Shell access was granted to user <anon>; Trace file: , /harddisk/tracelogs/system_shell_R0.log.20190626002907
*Jun 26 00:29:09.054: %LICENSE-1-EXPIRING: License for feature internal_service 1.0 will expire in 1 day . UDI=ASR1001-X:JAE184503JH
[ASR1001X-A_RP_0:/]$
[ASR1001X-A_RP_0:/]$
[ASR1001X-A_RP_0:/]$
[ASR1001X-A_RP_0:/]$ exitSession log harddisk:tracelogs/system_shell_R0.log.20190626002907 closed.

i will be appreciate if you can summarize the webex meeting by the email