Yea, sorry. DNS -- I was hammering that out before running out the door. DNS is the issue -- as far as I know, it's still an issue. ________________________________________ From: NANOG <nanog-bounces@nanog.org> on behalf of Chuck Church <chuckchurch@gmail.com> Sent: Monday, March 9, 2015 12:36 PM To: nanog@nanog.org Subject: RE: NDS Resolution Problems between Charter Communications and OpenDNS NDS? My first suggestion would be run DSREPAIR. Wow, that brings back memories. But since you probably mean DNS, I'll stop right there. Chuck -----Original Message----- From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Christopher Dye Sent: Monday, March 09, 2015 1:20 PM To: nanog@nanog.org Subject: NDS Resolution Problems between Charter Communications and OpenDNS If anyone from Charter Communications NetOps or OpenDNS NetOps is monitoring, could you please contact me off-list? It would seem AS36692 (OpenDNS) and AS23028 (Charter Communications) are having some issues playing together. Thanks Much, Chris Dye Chief Technical Officer Paragon Solutions Group, Inc.