|
||||||||
From: "Chris Buechler" <cbuechler at gmail dot com> On 10/5/05, Manuel Kasper <mk at neon1 dot net> wrote: >> On 05.10.05 15:49 +0100, Charlie Barker wrote: >> > I can't reach the monowall website, can anyone else? >> Maybe your DNS server still has an old IP address in its cache? The >> new cable router finally arrived today, so the IP address changed >> (but this time it's for good). The new address is 62.2.215.148. The >> DNS entry's TTL was only 5 minutes > A number of ISP's DNS servers unfortunately don't honor TTL's as they > should, so this could be an ongoing issue for some people for the next > few hours at least. If your ISP's DNS is still resolving the old > address, you should ask that they fix their DNS servers to play > nicely. The UUnet caching DNS pool (198.6.1.1) will not resolve it at this time. As a lot of ISPs pull from UUnet, this could be a major problem. Of course telling UUnet anything is like spitting in the wind. -Chris --------------------------------------------------------------------- To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch |