Anyone good with DNS domain propagation shit?
 

Got my first dedicated server and had to set up nameservers etc...

no fucking clue why its taking so long to propagate, like 12 hours now already...

yes yes, it could take 24 hours but ive never had that happen before, usually its like 30 minutes.

Any ideas? I am worried I set it up wrong. Please let me know if any of these are serious errors. Thanks!

intodns.com posted back these errors:

Mismatched NS records WARNING: One or more of your nameservers did not return any of your NS records.

DNS servers responded ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
***IP REMOVED***

Multiple Nameservers ERROR: Looks like you have less than 2 nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.

Missing nameservers reported by your nameservers You should already know that your NS records at your nameservers are missing, so here it is again: ns1.xxxxxxx.com ns2.xxxxxx.com

SOA record No valid SOA record came back!

MX Records Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!

WWW A Record ERROR: I could not get any A records for ***domain!
(I only do a cache request, if you recently added a WWW A record, it might not show up here.)

First off did you register your nameservers as nameservers with your registrar?

I did in fact, then i entered ns1.dkjfkjsdfklsdj.com ns2.dkfjlsdklfjd.com (with my domain name of course there)

Using namecheap btw

Ok so you added them at the registrar.

Now on your server do you have NS records for both nameservers?

Less then 2 nameservers should mean at least one is still responding, which should not cause your domain to be unreachable. When you look at the whois at namecheap, does it display your new nameservers yet?

No SOA records mean that the nameservers are not correctly setup though, so you might wanna double check that.

You can verify by doing a dig domain.com SOA or dig domain.com A @nameserver at the command line

PM me your SSH login and I'll have you up and resolving within 30mins.

lol :helpme

Namecheap usually have them up and running in a few mins so I doubt it is a propagation delay and is something more complicated.

I guess you had realised that already though :)...

errr......

Thanks! But I think I will have my host company fuck around with it.

Thanks all for the input!!!!!

Since you removed the useful information from your post, like the name of the site, we can't tell you what's wrong. We can only guess and tell you what some common errors are. The most common error is that you have to list the name servers TWICE, in two different places in the registrar. You probably already know where to list the DNS servers that are authoritative for a.domain. What most most people don't know until they've done it is that first you have to create those servers elsewhere in the registrar, with IP addresses. Otherwise you have a chicken.and egg problem - you have to talk to ns1.domain.com to get the IP for any name within domain.com, but ns1.domain.com is part of domain.com, so you need to have the IP of ns1.domain.com to get the IP of ns1.domain.com.