Hi there. Yeah the machine I'm testing from isn't caching anything, because up to now I get the host not found message. However using my nameserver everything works as it should. On Thu, Feb 05, 2004 at 12:19:44PM -0700, Joseph C. Lininger wrote: > Hello, > Actually, if you have bind configured properly and dig works right on your local machine, there really isn't anything you can do. It can take 24 to 48 hours for dns information to propogate, and sometimes even longer if values have been cached by the machine your testing from. > > -- > Joseph C. Lininger > jbahm at pcdesk.net > > On Thu, 5 Feb 2004, Igor Gueths wrote: > > > Hi all. Last night I got rndc working and now it seems the server is > > running as it should be. However, when I try resolving my domain from a > > machine other than mine, on a different network, it still isn't found. > > This means that I have still not been noticed by the root servers. I > > don't remember who said this, but what was mentioned was that the > > proppogation time had to do with the way your zone file was written. > > Would the MINTTL field of the SOA record by any chance have something to > > do with this? Currently, I have my serial number set to yyyymmdd format, > > refresh is 1H, retry is 2H, expire is 1W, and TTL is 1D. I assume that > > since TTL is set to 1 day that it can take up to 24 hours to proppogate, > > and that if I want to reduce this time I should reduce the TTL field? Am > > I still going wrong on something here? P.S: Thanks for all the replies > > so far! > > > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup
