Cara mengatasi ping: namadomain.com: Temporary failure in name resolution

Suatu ketika saya sewa domian kemudian set ns domain ke IP. NS ( Name Server ). Setup ns domain di sebuah domain tujuan nya adalah menghubungkan nama domian ke IP atau ns domain lain . Saya buka pada firefox alamat web belum berhasil membuka / menampilkan web. Padahal seting ns domain sudah tepat.

Saya coba ping deh diterminal.  ping: namadomain.com: Temporary failure in name resolution , ternyata tidak ada balasan dari ping. Dan saya pakai OS KDE NEON ( Ubuntu based / Debian based )

ping: namadomain.com: Temporary failure in name resolution

 Masalah Di Laptop Saya Belum Ada DNS Google

Setelah saya googling ternyata masalah ada di file /run/systemd/resolve/stub-resolv.conf , tidak ada DNS google

nah berikut cara nya , masih diterminal  ketik perintah berikut , yang arti nya buka nano di  /run/systemd/resolve/stub-resolv.conf

sudo nano /run/systemd/resolve/stub-resolv.conf

Maka akan terbuka nano

# 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
options edns0

Silahkan coment pada name server bawaan beri tanda pagar di depan yang mebuat skrip pasif  dan buat baru nameserver 8.8.8.8. Sehingga menjadi sperti ini

# 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
nameserver 8.8.8.8
options edns0

Untuk menutup nano dan menyimpan tekan bersama tombol CTRL dan bersama X kemudian tekan Y . Setelah itu coba ping ke domain yang tadi ditest, misal seperti berikut

ping namadomain.com
PING namadomain.com (103.28.52.13) 56(84) bytes of data.
64 bytes from hostingtung.com (103.28.52.13): icmp_seq=1 ttl=52 time=433 ms
64 bytes from hostingtung.com (103.28.52.13): icmp_seq=2 ttl=52 time=402 ms
64 bytes from hostingtung.com (103.28.52.13): icmp_seq=3 ttl=52 time=311 ms
64 bytes from hostingtung.com (103.28.52.13): icmp_seq=4 ttl=52 time=340 ms
64 bytes from hostingtung.com (103.28.52.13): icmp_seq=5 ttl=52 time=309 ms
64 bytes from hostingtung.com (103.28.52.13): icmp_seq=6 ttl=52 time=328 ms
64 bytes from hostingtung.com (103.28.52.13): icmp_seq=7 ttl=52 time=817 ms
64 bytes from hostingtung.com (103.28.52.13): icmp_seq=8 ttl=52 time=426 ms
64 bytes from hostingtung.com (103.28.52.13): icmp_seq=9 ttl=52 time=335 ms

Referensi yang saya baca : https://stackoverflow.com/questions/53687051/ping-google-com-temporary-failure-in-name-resolution