- mice-discuss - lists.micemn.net

Fwd: [JPTECHS] Fwd: [MICE-DISCUSS] State of MN DNS Issues

by David Farmer

I forwarded this off to the guys at the state, here is a response. Thanks ---------- Forwarded message ---------- From: Reilly, Russ (MNIT) <russ.reilly(a)state.mn.us> Date: Tue, Jul 19, 2016 at 9:19 AM Subject: Re: Fwd: [MICE-DISCUSS] State of MN DNS Issues Thanks, we are aware of some complaints and working the issue. Something possibly related to how IPv6 was enable on the Infoblox and the various addresses. Comcast was broke Saturday and we got that fixed so it seems there are just oddities in various resolvers we are working through this with Infoblox. *Russ Reilly* | Network Support, network Support Manager MN.IT Services, State of Minnesota 651-201-1022 (w) *| * russ.reilly(a)state.mn.us *[image: Title: MN.IT Services logo - Description: MN.IT Services logo]* <http://www.mn.gov/oet> Information Technology for Minnesota Government *|* mn.gov/mnit <http://www.mn.gov/oet> Begin forwarded message: *From:* Doug McIntyre <merlyn(a)IPHOUSE.NET <merlyn(a)iphouse.net>> *Date:* July 19, 2016 at 08:51:27 CDT *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET <MICE-DISCUSS(a)lists.iphouse.net> *Subject:* *Re: [MICE-DISCUSS] State of MN DNS Issues* *Reply-To:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET <MICE-DISCUSS(a)lists.iphouse.net>> On Tue, Jul 19, 2016 at 03:42:13AM -0500, Richard Laager wrote: FYI: state.mn.us DNS has broken DNSSEC and broken IPv6. I called yesterday, and they were aware of the DNSSEC issue. I had to push out the early beta BIND 9.11 out to production so I could use the new Negative Trust anchor option for them on my frontline resolvers. rndc nta state.mn.us [view] I think only BIND based resolvers thought it was an error though. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================

July 19, 2016

Re: State of MN DNS Issues

by Doug McIntyre

On Tue, Jul 19, 2016 at 03:42:13AM -0500, Richard Laager wrote: > FYI: state.mn.us DNS has broken DNSSEC and broken IPv6. I called > yesterday, and they were aware of the DNSSEC issue. I had to push out the early beta BIND 9.11 out to production so I could use the new Negative Trust anchor option for them on my frontline resolvers. rndc nta state.mn.us [view] I think only BIND based resolvers thought it was an error though. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

July 19, 2016

State of MN DNS Issues

by Richard Laager

FYI: state.mn.us DNS has broken DNSSEC and broken IPv6. I called yesterday, and they were aware of the DNSSEC issue. http://dnsviz.net/d/state.mn.us/dnssec/ -- Richard

July 19, 2016

Re: Good news from Akamai (Finally)

by DeLong, Owen

Quite a bit more likely, too. Owen > On Jul 12, 2016, at 14:32 , Hannigan, Martin <marty(a)AKAMAI.COM> wrote: > > This is better than Boston trouncing the Mets in a World Series! > > Thanks all. > > Best, > > -M< > > > >> On Jul 12, 2016, at 17:22, DeLong, Owen <owen(a)AKAMAI.COM> wrote: >> >> We have resolved the router issue and we are now delivering almost 8 Gbps to MICE. >> >> I expect this will continue to increase as things stabilize over the coming days. >> >> Please let me know if you have any questions. >> >> Also, in case you missed the first few memos… >> >> WE NO LONGER PEER WITH ROUTE SERVERS at MICE. >> >> If you want Akamai Traffic, you must set up bilateral peering with us. >> >> Send email to peering(a)akamai.com >> >> If you send email to peering(a)akamai.com and do not receive a response within 48 hours, please resend your email and CC owen(a)akamai.com. >> >> We will respond to peering requests on a timely basis and we have an open peering policy. >> >> Owen >>

July 13, 2016

Re: Good news from Akamai (Finally)

by Hannigan, Martin

This is better than Boston trouncing the Mets in a World Series! Thanks all. Best, -M< > On Jul 12, 2016, at 17:22, DeLong, Owen <owen(a)AKAMAI.COM> wrote: > > We have resolved the router issue and we are now delivering almost 8 Gbps to MICE. > > I expect this will continue to increase as things stabilize over the coming days. > > Please let me know if you have any questions. > > Also, in case you missed the first few memos… > > WE NO LONGER PEER WITH ROUTE SERVERS at MICE. > > If you want Akamai Traffic, you must set up bilateral peering with us. > > Send email to peering(a)akamai.com > > If you send email to peering(a)akamai.com and do not receive a response within 48 hours, please resend your email and CC owen(a)akamai.com. > > We will respond to peering requests on a timely basis and we have an open peering policy. > > Owen >

July 12, 2016

Good news from Akamai (Finally)

by DeLong, Owen

We have resolved the router issue and we are now delivering almost 8 Gbps to MICE. I expect this will continue to increase as things stabilize over the coming days. Please let me know if you have any questions. Also, in case you missed the first few memos… WE NO LONGER PEER WITH ROUTE SERVERS at MICE. If you want Akamai Traffic, you must set up bilateral peering with us. Send email to peering(a)akamai.com If you send email to peering(a)akamai.com and do not receive a response within 48 hours, please resend your email and CC owen(a)akamai.com. We will respond to peering requests on a timely basis and we have an open peering policy. Owen

July 12, 2016

Akamai @ MICE

by DeLong, Owen

Among the multitude of problems that have plagued this process, we have discovered yet another one. This time, it’s not actually our fault. It seems that the nifty new Juniper we deployed there is suffering from a hardware failure in the form of a memory failure which is causing a number of odd behaviors (such as forwarding packets in ways that don’t agree with the forwarding table). We are working to resolve this latest issue as quickly as possible and will continue to work to bring this site back up to full capacity as soon as possible. We apologize (again) for any inconvenience. Owen

July 12, 2016

Re: Slack

by Mike Horwath

On Fri, Jul 01, 2016 at 11:10:29AM -0500, Chris Wopat wrote: > On 07/01/2016 11:05 AM, Mike Horwath wrote: > > > I dunno - what is there to talk about in realtime? > > It's just basically IRC, which is usually just a competition to see > who can idle the longest :) I'd take that challenge.. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

July 1, 2016

Re: Slack

by Mike Horwath

On Fri, Jul 01, 2016 at 11:07:40AM -0500, Jason Hanke wrote: > circuit turn up, troubleshooting sounds like something that could be helpful. > We could also argue about port fees. :P Probably the most helpful of all! -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

July 1, 2016

Re: Slack

by Chris Wopat

On 07/01/2016 11:05 AM, Mike Horwath wrote: > I dunno - what is there to talk about in realtime? It's just basically IRC, which is usually just a competition to see who can idle the longest :) -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965

July 1, 2016