Yes. That is how the pool URL works. It does some sort of load-balancing via
> DNS resolution. That's why it has so many addresses. I am well aware of the /etc/hosts hack, but it's an ugly work-around. I'd > rather be able to configure portage itself to use a different pool or a > specific > server, rather than mess around with DNS resolutions. And I haven't been > having any luck in searching for how to configure the keyserver used by > Portage. > > Yes, there is an email address I could message to notify them that there > is a > problematic server, but because Portage tells me nothing about which > server > it's using other than the pool URL, I have nothing helpful to tell them. > Since you know the server IPs, and there's only a small number so you could try connection to each of them and see which one(s) fail. Or tcpdump, or netstat etc.
