@atdigit

Ah, I believe I see what’s wrong :-).

It appears as if you’re trying to setup custom DNS from the looks of it, however, there’s no routing in place for the custom DNS at DigitalOcean.

If we take a look here, you’ve setup A entries for ns1, ns2 and ns3.yourdomain.com and then set ns1 and ns2 up as NS entries here.

Even though it’s not really a good idea to set all your NS records to the same IP (as it’s a single point of failure), the above would work, though you need to register the IP(’s) for your NS records, otherwise they’re just entries on your server.

–

Since you seem to be using DigitalOceans’s DNS (that’s what your domain reports when doing a WhoIs lookup), you need to create the same A entries that are shown here through DigitalOcean via the Networking -> Domains section. You would then need to change all three of the NS entries here to match your custom DNS.

So your DigitalOcean DNS Zone file should look something like:

A                @                188.166.96.114
A                ns1              188.166.96.114
A                ns2              188.166.96.114
A                ns3              188.166.96.114
NS                                ns1.dumdar.com.
NS                                ns2.dumdar.com.
NS                                ns3.dumdar.com.

Unless you’re using www as an actual sub-domain, I’d drop that A entry and replace it with a CNAME, thus resulting in:

CNAME            www              dumdar.com.
A                @                188.166.96.114
A                ns1              188.166.96.114
A                ns2              188.166.96.114
A                ns3              188.166.96.114
NS                                ns1.dumdar.com.
NS                                ns2.dumdar.com.
NS                                ns3.dumdar.com.

Bare in mind, DNS changes can take anywhere from 12-24 hours to resolve, so if this doesn’t immediately resolve, give it a little time and check back.