DNS issues with tmomail.net

Sam Wilson Sam.Wilson at ed.ac.uk
Thu Dec 11 14:18:10 UTC 2008

In article <ghotm6$20bh$1 at sf1.isc.org>,
 David Ford <david at blue-labs.org> wrote:

> Sam Wilson wrote:
> > I hadn't noticed it but all the records in the response to a request for 
> > the MX for tmomail.net have a TTL of 60 seconds, that's the MX record, 
> > the NS authority record and the additional A record.  The names in the 
> > delegation NS records for for tmomail.net are different from the 
> > authoritative ones, though they seem to be the same servers.  There's 
> > considerable opportunity there for things to go wrong, though it all 
> > seems to work fine from here.
> >   
> It will work for hours, sometimes a day before bind is unable to fetch 
> records for it again.  But immediately upon restarting bind, bind is able to 
> go fetch records for it.  I understand that the records for tmomail.net are 
> problematic but what makes the difference in bind from running a while vs. a 
> fresh restart when it comes to fetching records?  Why would it be 100% 
> successful on restart?

Dunno, but when you poke around in that area there are a whole lot more 
duelling TTLs.  But as Jinmei-san points out you may be being bitten by 
a bug.


More information about the bind-users mailing list