MrPorcupine

For those who (unlike me) don't read every Apple-related rumor ever posted: Apple Integrating Yelp Check-Ins Directly into iOS 6 Maps In related news, Apple is rumored to be introducing another feature in iOS 6 where your iOS device will hold someone down while the local bully kicks them in the head.

Excellent suggestions - thanks everyone!

Hi. A coworker of mine just went through surgery, and is on a diet described by his doctor as a "splat" diet: if it goes splat when you throw it on the floor, he can eat it. (We will assume that it should go splat without undue force, as presumably anything will go splat given sufficiently high initial velocity...) As such, I'm wondering: what's the peak of gastronomy for one on a nearly-liquid-food diet? Have any of you been on such a diet and care to share any clever ideas? Right now he's probably too drugged up to care much but I'm guessing by Week Two he's gonna be desperate for something different!

Meadowlands, somewhere around the 50-yard line...

I'm in.

Has anyone been to Teocalli Tamale recently? The place seems to have changed a fair amount: the tables and floor are the same, but there are lots of pictures of different types of food above the old food-service counter. While there are exceptions, I take the whole pictures-of-the-food thing as a sign that caution may be required. So, is it the same, or has something major changed? (And more importantly is it still tasty?) (me, making a rare food-related post, who knew?!?)

I think that the ipsink-versus-ipslink confusion was still there, off in some corner somewhere, either in the mail-server config on the Invision side or on the part of the DNS that turns IP addresses back into hostnames. My home "show me whose email I've rejected today for not being from a real domain" report was showing failures for a while from server42.ipsink.com. I didn't have time to track this down, but the last occurrence I see of this in my mail logs was on Jan 21, and the email notification for a test PM I sent myself made it to me, so I think this has been fixed. I now see server42.ipslink.com in the mail headers on the "you have a PM" notification. (I was reminded of this yesterday while talking with another dr.com member, and finally had a few minutes to check into it...)

Thanks! And glad I could be of help. I think it'll take a while longer for some of the "bad" nameserver records to work their way out of people's caches; the time-to-live on the broken records was one day, so an ever-decreasing amount of stuff will stay broken until up to 24 hours after the fix was installed. I know I had to restart the nameserver in my house to force the bad NS records to be flushed. But a DNS lookup by hand now shows that things are in good shape (and the serial number was incremented, in a way that makes it likely that they did this before midnight (-: ). ; <<>> DiG 9.3.3 <<>> @ns1.ipslink.com soa donrockwell.com. ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54115 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;donrockwell.com. IN SOA ;; ANSWER SECTION: donrockwell.com. 86400 IN SOA ns1.ipslink.com. servnotify.invisionpower.com. 2008011102 86400 7200 3600000 86400 ;; AUTHORITY SECTION: donrockwell.com. 86400 IN NS ns2.ipslink.com. donrockwell.com. 86400 IN NS ns1.ipslink.com. ;; ADDITIONAL SECTION: ns1.ipslink.com. 3600 IN A 67.15.107.31 ns2.ipslink.com. 3600 IN A 67.15.107.32 ;; Query time: 47 msec ;; SERVER: 67.15.107.31#53(67.15.107.31)

I think they're just thinking "oh, gotta recreate this", and not realizing that they've fumble-fingered their idea of what should go in the zone... If the serial number doesn't change from 2008011101 in the next few hours, the update's already happened; if it does change but there's no 'l' yet, they definitely don't recognize the typo. We shall see.

I think Invision thinks they've fixed something, but they don't know about the typo, because they're not paying attention. The serial number on the SOA has changed, which indicates that they've changed something, and they're following a convention that leads me to think they've changed something today. But they still don't have the l in ipslink.com. Argh. If it'd help, I'd be happy to talk to them directly. Dave, do you have a static IP address? We could just ask Don if he could change nameservers through his registrar, to something we control... ; <<>> DiG 9.3.3 <<>> @ns2.ipslink.com soa donrockwell.com. ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33774 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;donrockwell.com. IN SOA ;; ANSWER SECTION: donrockwell.com. 86400 IN SOA ns1.ipsink.com. servnotify.invisionpower.com. 2008011101 86400 7200 3600000 86400 ;; AUTHORITY SECTION: donrockwell.com. 86400 IN NS ns1.ipsink.com. donrockwell.com. 86400 IN NS ns2.ipsink.com. ;; Query time: 47 msec ;; SERVER: 67.15.107.32#53(67.15.107.32) ;; WHEN: Fri Jan 11 19:05:29 2008 ;; MSG SIZE rcvd: 137

Yeah, at this point, "wrong" is clearly, um, right: the DNS is still messed up at Invision, as we've described.

While it's possible that the Invision people are correct, there is at least some reason to think they're wrong, as it's been more than 3-4 hours, and the DNS for donrockwell.com is still botched (see below). Perhaps they could elaborate on the DNS problem they had, because maybe they had more than one DNS problem... ; <<>> DiG 9.3.3 <<>> @ns1.ipslink.com soa donrockwell.com. ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63145 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;donrockwell.com. IN SOA ;; ANSWER SECTION: donrockwell.com. 14440 IN SOA ns1.ipsink.com. servnotify.invisionpower.com. 2008010901 14400 7200 3600000 86400 ;; AUTHORITY SECTION: donrockwell.com. 86400 IN NS ns2.ipsink.com. donrockwell.com. 86400 IN NS ns1.ipsink.com. ;; Query time: 63 msec ;; SERVER: 67.15.107.31#53(67.15.107.31) ;; WHEN: Thu Jan 10 20:41:48 2008 ;; MSG SIZE rcvd: 137 ; <<>> DiG 9.3.3 <<>> @ns2.ipslink.com soa donrockwell.com. ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63834 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;donrockwell.com. IN SOA ;; ANSWER SECTION: donrockwell.com. 14440 IN SOA ns1.ipsink.com. servnotify.invisionpower.com. 2008010901 14400 7200 3600000 86400 ;; AUTHORITY SECTION: donrockwell.com. 86400 IN NS ns2.ipsink.com. donrockwell.com. 86400 IN NS ns1.ipsink.com. ;; Query time: 49 msec ;; SERVER: 67.15.107.32#53(67.15.107.32) ;; WHEN: Thu Jan 10 20:43:19 2008 ;; MSG SIZE rcvd: 137 [steve@newbie steve]$ whois ipsink.com Whois Server Version 2.0 Domain names in the .com and .net domains can now be registered with many different competing registrars. Go to http://www.internic.net for detailed information. No match for "IPSINK.COM".

I spoke too soon -- it's still horked up. What my nameserver here said before I reloaded: [steve@newbie steve]$ dig ns donrockwell.com. ; <<>> DiG 9.3.3 <<>> ns donrockwell.com. ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32883 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;donrockwell.com. IN NS ;; ANSWER SECTION: donrockwell.com. 69884 IN NS ns2.ipsink.com. donrockwell.com. 69884 IN NS ns1.ipsink.com. so again I'm pointed at the bogus "ipsink" nameservers. The com servers say: ; <<>> DiG 9.3.3 <<>> @a.gtld-servers.net a www.donrockwell.com. ; (2 servers found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26853 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;www.donrockwell.com. IN A ;; AUTHORITY SECTION: donrockwell.com. 172800 IN NS ns1.ipslink.com. donrockwell.com. 172800 IN NS ns2.ipslink.com. ;; ADDITIONAL SECTION: ns1.ipslink.com. 172800 IN A 67.15.107.31 ns2.ipslink.com. 172800 IN A 67.15.107.32 and the nameservers at ipslink.com both say: ; <<>> DiG 9.3.1 <<>> @ns2.ipslink.com soa donrockwell.com ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 469 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;donrockwell.com. IN SOA ;; ANSWER SECTION: donrockwell.com. 14440 IN SOA ns1.ipsink.com. servnotify.invisionpower.com. 2008010901 14400 7200 3600000 86400 ;; AUTHORITY SECTION: donrockwell.com. 86400 IN NS ns1.ipsink.com. donrockwell.com. 86400 IN NS ns2.ipsink.com. so they're definitely the ones handing out the bad information (or ipsink.com is a domain that's supposed to exist, but I think whois would behave slightly differently if that was indeed the case). So if you don't already have NS or A records for donrockwell.com, you'll ask the com servers, who'll point you temporarily at the right ones, until your nameserver tosses the glue that the com server provides and gets the "real" answer from the authoritative servers. Or something much like that. But the people who manage the donrockwell.com domain need to fix their freakin' typo!

I think that what happened was that the donrockwell.com zone got fat-fingered... The nameservers for donrockwell.com -- as given in the donrockwell.com zone -- seem to have been set for a while to ns1.ipsink.com and ns2.ipsink.com. Unfortunately, that domain doesn't exist. However, the delegation in the com servers seems to have been correct. So things would kinda-sorta work, sometimes, for a while: you'd look up www.donrockwell.com, and your nameserver wouldn't know jack about it, so it'd ask the com nameservers "gimme the address for www.donrockwell.com", and it'd get back "I don't know, go ask ns1.ipslink.com and ns2.ipslink.com, here's the IP addresses". So (as a mild oversimplication), that'd get cached in the nameserver, and you'd go ask ns1.ipslink.com or ns2.ipslink.com, and you'd get an answer, which you'd also cache for a while. In that process, you'd end up getting the "official" nameservers from the donrockwell.com zone, which are the ones that were misspelled. But eventually your cached address record for donrockwell.com would time out. So you'd have to go ask the nameservers for donrockwell.com for the answer again. But the only nameservers you now know about don't exist (because of that missing 'l'). So you can't get an answer. I think this has been fixed in the donrockwell.com zone, so my guess is that as the botched nameserver records for donrockwell.com time out, people should regain access. Here at Maison Miller, I restarted the nameserver to force that to happen, but most people don't run nameservers at home... That's the quick (and not so clear) version -- I should go back to listening to my work conference call. I guess.

We should have gotten four of the hot-chili sauces, but got two of those and two others. The chili sauce is quite the tasty accompaniment. And when the iPod played a-ha's Take On Me, you could hear the wave of spontaneous humming sweep across the restaurant. This was our only chance to make it to a Lickety-Split Lunch for the last few weeks and in the next couple of weeks, so it was a serious bummer that they weren't open. Ah, well, these things happen. Must... learn... to... call... always...