djbdns timing out

I set up djbdns with tinydns and dnscache on two machines. ns1.leadasp.com (69.13.26.2) and ns2.leadasp.com (69.13.26.2). Both machines have dnscache on 127.0.0.1.

I thought I had everything working but I can not figure out why it says the name servers are timing out when I try a domain at dnsreport.com. The domains are also no longer replying to pings by there domain names (ip addresses still work). Pinging the names ns1.leadasp.com and ns2.leadasp.com still seem to work though.

I must have changed some setting and not realized I did it because the domains were all working (someone could see them up in NZ, I am in the US). I ran through all of the dnsq troubleshooting scripts on the machines, but it looks like everything is ok to me. Here is everything that I think is relevant. I really appreciate any help, I have tried for 5 hours already and I really do not want to start from scratch on this machine. Thanks!!!

www1# dnsq ns debt-consolidation-financing.com ns1.leadasp.com
2 debt-consolidation-financing.com:
92 bytes, 1+1+0+1 records, response, authoritative, noerror
query: 2 debt-consolidation-financing.com
answer: debt-consolidation-financing.com 259200 NS ns1.leadasp.com
additional: ns1.leadasp.com 86400 A 69.13.26.2


www1# dnsqr ns debt-consolidation-financing.com
2 debt-consolidation-financing.com:
76 bytes, 1+1+0+0 records, response, noerror
query: 2 debt-consolidation-financing.com
answer: debt-consolidation-financing.com 257634 NS ns1.leadasp.com


My resolv.conf only lists 127.0.0.1
My tinydns current log is listing this

@400000003e9a839d2ed9acdc 450d1a64:0406:ad7c + 001c www3.leadasp.com
@400000003e9a839d2ee95894 450d1a64:0407:ad7d + 001c www3.leadasp.com.leadasp.com
@400000003e9a839e06126ba4 450d1a64:0408:fe7d + 001c www3.leadasp.com
@400000003e9a839e0621540c 450d1a64:0409:fe7e + 001c www3.leadasp.com.leadasp.com
@400000003e9a839e06e36f74 450d1a64:040a:438d + 001c www3.leadasp.com
@400000003e9a839e06f71e84 450d1a64:040b:438e + 0001 www3.leadasp.com
@400000003e9a839e07a52934 450d1a64:040c:438d + 001c www3.leadasp.com
@400000003e9a839e07b077bc 450d1a64:040d:438e + 0001 www3.leadasp.com

My /usr/local/tinydns/env/IP lists 69.13.26.2




.leadasp.com::ns1.leadasp.com
.leadasp.com::ns2.leadasp.com
@leadasp.com::mail.leadasp.com
+www1.leadasp.com:69.13.26.2
+www2.leadasp.com:69.13.26.3
+www3.leadasp.com:69.13.26.100
+www4.leadasp.com:69.13.26.101
+ns1.leadasp.com:69.13.26.2
+ns2.leadasp.com:69.13.26.3
+mail.leadasp.com:69.13.26.2

.debt-consolidation-credit-assistance.com::ns1.leadasp.com
@debt-consolidation-credit-assistance.com::mail.leadasp.com
=www.debt-consolidation-credit-assistance.com:69.13.26.5
=debt-consolidation-credit-assistance.com:69.13.26.5

I have similar setups for the following domain names just like this one for debt-consolidation-credit-assistance.com

URL
URL
URL
URL
URL
URL
URL
URL
URL

In your data file try not to use . and = lines. Those are for people who are authoritative for their IP (69.13.26.2,3,4,5,100... in your case). Currently your ISP propagation.net still has DNS authority for any of your assigned IPs.

So I should just be using + for each domain? Is there a good sample file somewhere that I can see?

I am curious what the damage is of the current setup because now it is working as far as I can tell.

The intelligence of my hosting provider shined through as they firewalled port 53 from the colocation facility where my rack is.

>> So I should just be using + for each domain?

Not just +. What I normally use (even for default domain) are Z&+@.

>> Is there a good sample file somewhere that I can see?

Search this forum under my username. There are a dozen.