Dig results timed out no servers reached

[optimised]

Thought I had my system configured
When I run dig for my site domain.com
I get connection timed out server could not be found.
What would cause this?

[jdvilla]

Did you ever find a solution for this? (I would hope so by now ) I'm in the same boat right now?

[BeDe]

try using "dig +vc +trace domain.com" and see if there is
any usefull output.
also, you can try to direct the query to the primary DNS server for your domain

[jdvilla]

hmmm...

ok, there is correct output...

e37.net. 86400 IN A 66.180.175.6
e37.net. 86400 IN NS ns1.iscdev.com.
e37.net. 86400 IN NS ns2.iscdev.com.

but why when I use

dig e37.net do I get

; <<>> DiG 9.2.2-P3 <<>> e37.net
;; global options: printcmd
;; connection timed out; no servers could be reached

very confusing...

if I do

dig iscdev.com

I get a response. iscdev.com is the domain where my nameservers are as well.

[BeDe]

It looks like all the changes are not propagated yet
I assume that ns1.iscdev.com is your primary name server.
Here are some thing you can try on you primary nameserver.
Lower the TTL value drastically. As i see now it's 86400.
Use 36000, this means 10 hours and increase the serial.
After that restart the DNS server.
You will have to wait some time until all the changes are propagated. To test ans see if everything is ok, try diggining from a computer outside your network.
If this will solution will work, after all is ok go back to the original value for TTL.