DNS issue

[kalpana]

Hi,

I'm running into some DNS issues on Ubuntu 22.04.3 LTS. I tried to set up a static IP and ran into these DNS issues, but then i thought I solved them by setting up the IP on my router instead of the machine. I'm new to linux so any help is appreciated.

Code:

Code Select Expand

$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=60 time=18.4 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=60 time=9.16 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=60 time=8.38 ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 8.376/11.979/18.399/4.550 ms
$ ping google.com
ping: google.com: Temporary failure in name resolution
This is the contents of `/etc/resolv.conf`

Code:

Code Select Expand

$ cat /etc/resolv.conf
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8)
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#                                                                                                                   
# 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 "resolvectl status" to see details about the uplink DNS servers                                               
# currently in use.                                                                                                 
#                                                                                                                   
# Third party programs should typically 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                                                                                               
options edns0 trust-ad                                                                                               
search .