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.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
You don’t need to setup DNS at both Digitalocean and Route 53. One should do. But at either one of these there needs to be an A record defined to point at your droplet’s IP. Right now your domain’s whois info still shows AWS 53 as your name servers:
$ whois -f devparticle.com|grep Server
Registrar WHOIS Server: whois.registrar.amazon.com
Name Server: NS-1438.AWSDNS-51.ORG
Name Server: NS-1969.AWSDNS-54.CO.UK
Name Server: NS-464.AWSDNS-58.COM
Name Server: NS-652.AWSDNS-17.NET
But the above name servers refuse to answer basic DNS queries against devparticle.com:
$ dig devparticle.com @ns-652.awsdns-17.net +norec
; <<>> DiG 9.10.3-P4-Ubuntu <<>> devparticle.com @ns-652.awsdns-17.net +norec
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, **status: REFUSED**, id: 57295
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;devparticle.com. IN A
;; Query time: 37 msec
;; SERVER: 205.251.194.140#53(205.251.194.140)
;; WHEN: Tue Oct 02 18:28:57 CDT 2018
;; MSG SIZE rcvd: 33
This means there’s a misconfiguration at Route 53’s end. That’s where I’d check things.
@unixynet After following the information you provided, I was able to resolve my DNS. I greatly appreciate your input and thank you very much.