Hi, guys On 8 Aug 2007, at 05:23, Nathan Ward wrote:
various reasons some folks at TVC would appreciate it if you could flush the information you have in your recursive/caching nameservers for the zone images.tvnz.co.nz That would help clear up some TTL badness. For those that don't know, a better way to renumber is to run your
On 8/08/2007, at 4:14 PM, jamie baddeley wrote: public facing services on both the new /and/ old addresses simultaneously, for /at least/ the TTL that your DNS zone proposes.
The long tail is weeks and weeks following a renumbering. I used to work for a huge e-tailer in the UK. One of my major projects was to move them from their single-homed hosting to a new multi-homed network. Their webserver vips were therefore renumbered from their old providers' PA address space, to their new PA space. I put a transparent proxy that was configured to just proxy their site, on the old address, and then updated dns. As expected, before the ttl expiry there was a lot of traffic on the proxy. The next morning (12 hours after moving, 1hr ttl during the move) there was still a lot of traffic. This was because many ISPs in the UK were ignoring our 1h TTL, and enforced their own 24hr+ minimum TTLs. When I had to take the proxy out - a month after the renumber - because we were handing back the old datacentre space, there was still traffic going through the proxies. Much of it bots, some of it customer traffic. Only a request or two a minute, so it represented a tiny fraction of our traffic, but traffic still existed. I put this down to some users having a browser that did infinite cacheing ? Renumbering is an imprecise science. Proxy between your old and new infrastructure for at least a month is my advice. Best wishes, Andy