DNS & cache

[Sergejs Svitnevs]

Usually with some domains, I obtain a SERVFAIL when I make queries. To resolve it, I have to flush the cache (rndc flush). During 5-6 min., after flushing the cache, the server answers correctly.

Example:

before "rndc flush":
---named_dump.db
XXX.com 86310 IN NS ns1.XXX.com.

after "rndc flush" and "dig host.XXX.com":
---named_dump.db
XXX.com 85964 IN NS ns1.XXX.com.
ns1.XXX.com. 164 IN A

What should be the problem?
XXX.com is served by ns1.XXX.com. Where is A record for the name server?

Thanks,
Sergejs

[Sachin Patel]

Try changing refrace value to smaller may be two hour or so.

I have set for 6 hour.
21601 ; Refresh every 6 hours

It is third line is SOA record.

Sachin

[harry d brown jr]

Sergejs,

The real problem is with the sites that have servers that aren't available often, in which those DNS Admins should be changing the TTL to a smaller value!

In your case add the $TTL directive to the beginning of your zone files.

In this thread I compiled the info to build a DNS Caching Server.
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xdb005fe8b250d71190080090279cd0f9,00.html

live free or die

[Sergejs Svitnevs]

I have found the solution.
This often indicates that the glue record in the XXX.com domain doesn't match the record on the authoritative server. For instance, maybe on the authoritative server, ns1.XXX.com is an alias instead of an A record.

Sergejs