Rather odd problem...
Our network is all Static IP's in the 10.10.xx.xx range. The other day a problem was arrising with one of our domains.
When pinging MNBlah domain, we'd get replies from some 169.254. address (i forget last 2 octects). I'm no Microsoft Admin, but the SA went in and deleted some entry in the DNS control screen (sorry I'm not more descriptive) that should not have been there, and which he didn't think anyone added manually.
Instantly upon deleting this, pinging MNBlah domain returned the correct 10.10.xx.xx address and clients were able to login once again.
My question is: How in the world does this happen? I always thought that the dreaded 169.254 address was not routable, something like that 127. range, but I guess I'm completely off. And how would this rogue computer become the highest authority in the MNBlah domain?!
Is there something I can do Layer3 wise that would put a halt to any 169.254 traffic?