I got that part. My point is that it looks like the first DNS for the SOA is pointing to the DNS in your Portland DC.
Is this the old OSLab DC that is having the power issues? Or the one we are considering using for cross project stuff? Ed On Tue, May 23, 2017 at 8:27 AM, Andrew Grimberg via RT < fdio-helpd...@rt.linuxfoundation.org> wrote: > On Tue May 23 11:03:18 2017, hagbard wrote: > > OK... why is it listed first in the public SOA then? > > > > Ed > > Ed, > > I think you're missing what is happening here. > > Our _internal_ DNS is run out of Portland. The _external_ DNS for FD.io is > run out of a third party DNS provider. > > The cause of the intermittent 500 errors that Gerrit was getting is > because of connectivity issues affecting Portland itself, apparently > there's a massive power outage and our DC has been on generators since > yesterday but that doesn't mean the power problems aren't causing issues > for the DC nail-ups themselves. The connectivity issues have been causing > Gerrit to not be able to find the backend database server when it's > re-opening a connection. As such we've forcibly added the IP resolution to > the hosts file, which is something we don't normally do. > > -Andy- > > -- > Andrew Grimberg > The Linux Foundation > _______________________________________________ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev > _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
