Re: Public DNS64

On 2014-08-15 18:08, Larry Sheldon wrote: On 8/15/2014 6:39 PM, Mark Andrews wrote: >I can see a transfer request being made to TEXAS-WESLEYAN-UNIVERSITY >for 64.64.64.0/24. May be no. You need a memerable IPv6 addresses. "memerable"? Yeah, how do you expect anyone to make a meme out of 6

Re: Public DNS64

On 8/15/2014 6:39 PM, Mark Andrews wrote: >I can see a transfer request being made to TEXAS-WESLEYAN-UNIVERSITY >for 64.64.64.0/24. May be no. You need a memerable IPv6 addresses. "memerable"? -- The unique Characteristics of System Administrators: The fact that they are infallible; and, Th

Re: Public DNS64

Mark Andrews writes: > > In message <53ee8a4b.9000...@jima.us>, Jima writes: > > On 2014-08-15 16:11, Mark Andrews wrote: > > > For a public DNS64 service you also need a public NAT64. > > > > Not necessarily. If the public DNS64 server is using the well-known > > prefix 64:ff9b::/96 (from R

Re: Public DNS64

In message <53ee8a4b.9000...@jima.us>, Jima writes: > On 2014-08-15 16:11, Mark Andrews wrote: > > For a public DNS64 service you also need a public NAT64. > > Not necessarily. If the public DNS64 server is using the well-known > prefix 64:ff9b::/96 (from RFC6052), then all an eyeball network

Re: Public DNS64

On 2014-08-15 16:11, Mark Andrews wrote: For a public DNS64 service you also need a public NAT64. Not necessarily. If the public DNS64 server is using the well-known prefix 64:ff9b::/96 (from RFC6052), then all an eyeball network needs to do is route that /96 toward their own NAT64 environm

RE: peeringdb contact help

Replying off list -Original Message- From: "Bryan King" Sent: ‎8/‎15/‎2014 15:08 To: "'nanog@nanog.org'" Subject: peeringdb contact help I've been trying for 3 days now to get a response from supp...@peeringdb.com. Someone from peeringdb please respond o

Re: Public DNS64

For a public DNS64 service you also need a public NAT64. I suppose anyone willing to run a Tor exit node might be also willing to run such a service but it would be a traffic source anonymiser and likely would be abused. That said I could see it as a commercial service where only certain sets of

peeringdb contact help

I've been trying for 3 days now to get a response from supp...@peeringdb.com. Someone from peeringdb please respond off list please...

BGP Update Report

BGP Update Report Interval: 07-Aug-14 -to- 14-Aug-14 (7 days) Observation Point: BGP Peering with AS131072 TOP 20 Unstable Origin AS Rank ASNUpds % Upds/PfxAS-Name 1 - AS23752 208709 4.2%1630.5 -- NPTELECOM-NP-AS Nepal Telecommunications Corporation, Intern

The Cidr Report

This report has been generated at Fri Aug 15 21:14:03 2014 AEST. The report analyses the BGP Routing Table of AS2.0 router and generates a report on aggregation potential within the table. Check http://www.cidr-report.org/2.0 for a current version of this report. Recent Table History Date

[NANOG-announce] NANOG Reminders

NANOGers: As we wrap up summer vacation and look toward to fall, let me share a few NANOG reminders with you. ARIN+NOTR - Madison - September 9, 2014. The agenda has been published. This is a one day free m

Re: Public DNS64

Yeah, sort of agree, except I'm allergic to running services that aren't straight bit shoveling. NAT64 is pushing it, but at least that is just announcing a prefix. On Fri, Aug 15, 2014 at 2:33 PM, Rubens Kuhl wrote: > > > > On Fri, Aug 15, 2014 at 3:29 PM, Tim Durack wrote: > >> Anyone know o

Re: Public DNS64

On Fri, Aug 15, 2014 at 3:29 PM, Tim Durack wrote: > Anyone know of a reliable public DNS64 service? > > Would be cool if Google added a Public DNS64 service, then I could point > the NAT64 prefix at appropriately placed boxes in my network. > > Why? Other people are better than me at running DNS

Public DNS64

Anyone know of a reliable public DNS64 service? Would be cool if Google added a Public DNS64 service, then I could point the NAT64 prefix at appropriately placed boxes in my network. Why? Other people are better than me at running DNS resolvers :-) -- Tim:>

Weekly Routing Table Report

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, AusNOG, SANOG, PacNOG, LacNOG, TRNOG, CaribNOG and the RIPE Routing Working Group. Daily listings are sent to bgp-st...@lists.ap

RE: So Philip Smith / Geoff Huston's CIDR report becomes worth a good hard look today

It looks great though I would not want to troubleshoot the RIB to FIB programing errors unless there's a note somewhere saying what abbreviation to search for in FIB. The other think that comes to mind is that the more specifics could have different backup next-hops programed. adam > From: NAN