Microsoft - Technet

Installing Apache, root@th-ubuntu2:/home/taehee# apt update root@th-ubuntu2:/home/taehee# apt install apache2 root@th-ubuntu2:/home/taehee# ufw allow 'Apache' root@th-ubuntu2:/home/taehee# service apache2 status ● apache2.service - The Apache HTTP Server    Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset:   Drop-In: /lib/systemd/system/apache2.service.d            └─apache2-systemd.conf    Active: active (running) since Mon 2019-04-15 09:19:48 UTC; 1min 31s ago  Main PID: 19093 (apache2)     Tasks: 55 (limit: 4708)    CGroup: /system.slice/apache2.service            ├─19093 /usr/sbin/apache2 -k start            ├─19094 /usr/sbin/apache2 -k start            └─19095 /usr/sbin/apache2 -k start Apr 15 09:19:48 th-ubuntu2 systemd[1]: Starting The Apache HTTP Server... Apr 15 09:19:48 th-ubuntu2 apachectl[19068]: AH00558: apache2: Could not reliabl Apr 15 09:19:48 th-ubuntu2 systemd[1]: Started The Apache HTTP Server. Enable http

1. root@linux:/# cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "systemd-resolve --status" to see details about the uplink DNS servers # currently in use. # # Third party programs must not access this file directly, but only through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way, # replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 search 6e857bc1-b353-4193-8cc6-d8be8f7b24d1.internal.lnv4.azurestack.local 2. root@linux:/# nslookup -debug google.com Server:         127.0.0.53 Address:        127.0.0.53#53 Non-authoritative answer: Name:   google.com Addr