Constraints on TTLs
Chris Hastie <[email protected]>
| Newsgroups | gmane.network.dns.bind9.dlz |
|---|---|
| Message-ID | <[email protected]> |
After making some changes to my DNS this afternoon one host started being reported as NXDOMAIN, despite the fact that the records clearly remained. Logs indicated "dns_sdlz_putrr returned error. Error code was: bad ttl" After staring for hours at the data and being unable to spot the problem I removed all RRs for the host (there were four of them) and began reinserting them. The errors reappeared when I inserted an MX record with TTL of 86400. Reducing this to 3600 solved the problem. The TTL of the target of the MX record is 3600, as is the TTL of the host's other MX record. Is there some constraint on the TTLs of MX records? -- Chris Hastie ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone