Re: junos config commit question
rollback 0 Op 11-02-22 om 23:18 schreef Lyndon Nerenberg (VE7TFX/VE6BBM): On an EX4300 switch running JunOS 14.1 let's imagine I typed config delete interfaces before coming to my senses. How am I supposed to back out of that mess? For the life of me, after a week of reading the 3000 page reference manual, and endless DuckDuckGoing, I cannot see a simple way of just abandoning the commit. I've got to be missing something stunningly obvious here because it's unthinkable that this functionality doesn't exist. Help?!? The only way out I can see is to drop into the shell, make an uncompressed copy of juniper.conf.gz, then pop back into the config editor and load that over top of the editor's config view. Surely there's a saner way of dealing with this. --lyndon -- Marco Davids
Re: IPv6 and CDN's
Hi again, Op 22-10-21 om 17:13 schreef Job Snijders: Tl;DR Not at all. This was a very interesting read! Thank you. While pondering over it, I noticed that the ns[1234].fastly.net servers are nicely anycasted throughout the globe. If anyone could turn on IPv6 on their authoritatives without therisk of loosing too much performance, I reckon it would be them... our Cloudflare. But they already did it. ;-). > work in progress! I have good hopes. Rumour has it that Fastly employs some very smart people. I'm sure we'll see nice things happening when the time is right. -- Marco
Re: IPv6 and CDN's
On second thoughts... I seem to have been confused by the 'no records for fastly.net' (as a DNS-purist: that should have said "ns[1234].fastly.net" instead, to make it relevant). ;-) I ran into this some time ago with deb.debian.org Right. So please ignore: Just for the record; your issue is slightly different: You wrote: "deb.debian.org is a CNAME for debian.map.fastly.net. There are no records for fastly.net so any DNS querys from an IPv6 only resolver will not work." -- Marco
Re: IPv6 and CDN's
Hi Jens, Op 22-10-21 om 14:03 schreef Jens Link: I ran into this some time ago with deb.debian.org on an IPv6 only Debian VM with a locally installed resolver. I opened a ticket which was closed in record time: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961296 Just for the record; your issue is slightly different: You wrote: "deb.debian.org is a CNAME for debian.map.fastly.net. There are no records for fastly.net so any DNS querys from an IPv6 only resolver will not work." At the moment debian.map.fastly.net has an -record though. The thing is; the authoritative name servers of fastly.net are only willing to hand out that -record via IPv4. So it still doesn't work with the (locally installed) IPv6-only resolver ;-) Cheers, -- Marco
IPv6 and CDN's
Hi! We currently live in times where is actually fun to go IPv6-only. In my case, as in: running a FreeBSD kernel compiled without the IPv4-stack. A few years back doing such thing was mostly disappointing, but nowadays is actually quite doable and entertaining. So, the other day I decided to take this experiment to the next level by disconnecting my local resolver from IPv4 as well. Then things started to break. LinkedIn, Bing, Openstreetmap... Although they all work great on IPv6-only, now they no longer did. It turns out that there underlying CDN's with domain names such as ‘l-msedge.net’ and ‘trafficmanager.net’ (Microsoft) or 'fastly.net', that reside on authoritative name servers that *only* have an IPv4 address. I guess my question is simple: Why? Are there good architectural reason for this? Or is it just something that is overlooked and forgotten about? I would love to find out! Thank you. -- Marco This is also fun by the way. Look at that nice banner on https://clintonwhitehouse2.archives.gov/ :-)
Re: cloud automation BGP
Op 29-09-20 om 00:08 schreef Randy Bush: > have folk looked at https://github.com/nttgin/BGPalerter Yes. It does the job. And it's easy to install and run. -- Marco
Re: any interesting/useful resources available to IPv6 only?
Op 03-05-19 om 17:14 schreef Brian J. Murrell: I wonder if anyone has any references to interesting/useful/otherwise resources on are only available to IPv6 users that they can forward to me. Most of my personals websites are IPv6-only, but they are neither interesting nor useful. Although, perhaps https://dnslabs.nl/ is of any use, because I made every attempt to make it entirely IPv6-only, including it's authoritative name servers. That sometimes leads to interesting results. And furthermore I'd like to recommend a site that is not mine, but that I appreciate a lot: https://42.be/ -- Marco
Re: NTP question
Op 02-05-19 om 02:00 schreef Ask Bjørn Hansen: Though, on the topic of unusual requirements there are a bunch of contributors to the NTP Pool using this curious device It continues to surprise me that there is still hardware being sold that doesn't even support IPv6. -- Marco
Re: Purchasing IPv4 space - due diligence homework
Op 04-04-19 om 01:14 schreef Mike Hammett: Do you have sources for the ~90% T-Mobile IPv6? Not arguing, but to use that as a source myself when spreading the IPv6 good word. https://www.worldipv6launch.org/apps/ipv6week/measurement/images/graphs/T-MobileUSA.png https://stats.labs.apnic.net/ipv6/US (a bit slow, but informative) -- Marco
Re: Spectrum residential IPv6 rDNS - thank you !
Op 10-10-18 om 00:42 schreef Brandon Applegate: I’m guessing synthesized. There are a couple of dns servers out there that can do this. An interesting one I just found: https://all-knowing-dns.zekjur.net Or, if you prefer DNSSEC capable alternatives, try: https://github.com/cmouse/pdns-v6-autorev https://www.knot-dns.cz/docs/2.4/html/modules.html -- Marco signature.asc Description: OpenPGP digital signature
Re: Buying IPv4 blocks
Op 04-10-18 om 22:07 schreef John Levine: Even if you do have v6, some things like DNSSEC don't work very well if you can't do them over v4. Is that so? -- Marco signature.asc Description: OpenPGP digital signature
