DNS problem: not resolving correctly; dig response includes "status: REFUSED"

October 31, 2013 7.9k views
I've got four domains, all of which I would like to point to a placeholder page (running on a LAMP droplet) while I develop my site. Two of the domains are resolving properly, and two are not. I've followed the steps in your DNS Tips and Tricks article ( 1) whois confirms that ns1, ns2, & ns3 at digital ocean are the name servers for all four domains 2) but dig shows that the two non-resolving domains are having some kind of issue, which I can't decipher. the GOOD domain includes this in the dig response: ;; ->>HEADER<>HEADER<
6 Answers
Whoops appending the dig response in a way that doesn't break the html formatting of the post…

The GOOD ones...

;; HEADER opcode: QUERY, status: NOERROR, id: 22718
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

The BAD ones…

;; HEADER opcode: QUERY, status: REFUSED, id: 22254
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
And since the end of the post got eaten :) what I had said was that all four domains are configured identically in the DO DNS control panel, so any leads on why the status: REFUSED shows up in the dig response?

How much time has passed? Remember that DNS records can take up to 48 hours to propagate throughout the Internet.
Thanks -- it's been about 24 hours, though I will note that the two "good" domains began resolving within just a couple of hours.

Also, does the propagation time affect the whois data and the dig data equally?
What are the domain names?
Actually all four are resolving properly now. I was thrown off by the fact that two took much longer to resolve.

Thank you both for your assistance.
Have another answer? Share your knowledge.