Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I have created self managed kubernetes cluster in Digital Ocean. But the core DNS failed to resolve the FQDN of any components. While going through the blog , I found out that there is an issue in Digital Ocean private ip routing. Can anyone please help me resolve this issue.
root@kubernetes-master:~# kubectl run -i --tty --rm dns-test --image=busybox --restart=Never -- sh
If you don't see a command prompt, try pressing enter.
/ # nslookup kubernetes.deault
;; connection timed out; no servers could be reached
/ # nslookup kubernetes.deault
;; connection timed out; no servers could be reached
/ # ^C
/ # exit
pod "dns-test" deleted
pod default/dns-test terminated (Error)
root@kubernetes-master:~# kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
default myapplication-74ff95cf4f-mjqmz 0/1 CrashLoopBackOff 9 (4m41s ago) 40m
default postgres-0 1/1 Running 0 119m
kube-flannel kube-flannel-ds-6tw5c 1/1 Running 2 (24h ago) 24h
kube-flannel kube-flannel-ds-k9g6t 1/1 Running 2 (24h ago) 24h
kube-system coredns-55cb58b774-4t7d6 1/1 Running 2 (24h ago) 24h
kube-system coredns-55cb58b774-qdmgb 1/1 Running 2 (24h ago) 24h
kube-system etcd-kubernetes-master 1/1 Running 2 (24h ago) 24h
kube-system kube-apiserver-kubernetes-master 1/1 Running 2 (24h ago) 24h
kube-system kube-controller-manager-kubernetes-master 1/1 Running 2 (24h ago) 24h
kube-system kube-proxy-5lrdr 1/1 Running 2 (24h ago) 24h
kube-system kube-proxy-vbnhx 1/1 Running 2 (24h ago) 24h
kube-system kube-scheduler-kubernetes-master 1/1 Running 2 (24h ago) 24h
root@kubernetes-master:~#
72e571841e7f4a6881090a2f3e93c0
1txm05v1txm05v
jazzybruno
jazzybruno
1c73a43cf7ab4e9cb7f9e551f34a5e
Server Enthusiast
Sean DesPortes
Robin van der Knaap
4a0d624689d3431099e1b568c03569
Tomy Hsieh
Marek
BIdhan Bastola