It was setup to do "round robin" load balancing [presumably passing out an address to the least loaded server ... not sure if it had any intelligence to know which servers could handle more load than others]. I remember the message about it pointing to central. I haven't seen it on the site recently though, so I assumed it was back to doing what it should be. Either way, Central has always been the best for me anyway.
He turned it off because it couldnt handle the connections.
Right, but WHY couldn't it? Was it because each pool server could handle different loads than others and the DNS round robin was very simple so that the weaker servers were getting overloaded? Or was it because the DNS balancer itself couldn't handle it [that seems unlikely]. That is why I made a post within the last hour about load balancing. Deepbit manages it pretty well [but doesn't suffer the limitations of push pool forcing restarts when server changes occur].