Ah, it's ... a lot worse than I thought; here's the relevant node.js
bug:
https://github.com/joyent/node/issues/4168
I knew node.js was made by twelve year olds, but even so... Words
fail me.
-Robin
On Sat, Dec 29, 2012 at 12:53:51AM +, Phil Mayers wrote:
> [Grumble stupid mobile devices .
Here's the digging my ISP did:
[root@dvs-node01 ~]# node
> var dns = require('dns')
undefined
> dns.resolve('github.com', function(e, h) { console.log(JSON.stringify(h)) } )
{ oncomplete: [Function: onanswer] }
> ["207.97.227.239"]
undefined
> dns.resolve6('github.com', function(e, h) { console.l
[Grumble stupid mobile devices ...]
...I'm assuming you're deliberately engaging in a learning exercise and don't
want the rest of your experiments to be held up waiting for this one issue to
be fixed. But please do hassle the app vendor/devs to fix their broken stuff.
Tbh I'm still a bit dubio
Not hard - rpz zone with a single record will do it. I'm not typing on an ideal
device to give an example right now, I'm afraid ...
Mark is of course correct that v6-only is a struggle right now and that fixing
the apps is the proper solution. But I'm
Robin Lee Powell wrote:
>On Fri, Dec 28,
Truly, one should be fixing the applications not mucking with DNS responses.
DNS servers do not know the purpose of the A record lookup so changing it in
the server may break other applications. Additionally doing this will break
applications using DNSSEC.
There is no good reason to be IPv6 o
On Fri, Dec 28, 2012 at 07:57:24PM +, Phil Mayers wrote:
> Robin Lee Powell wrote:
>
> >
> >So I've got some IPv6-only VMs set up that need to talk to the
> >general internet for things like downloading packages. As you
> >can imagine, this requires that they have NAT64 and DNS64,
> >because
Just out of curiosity, what ended up being the problem?
On Fri, Dec 28, 2012 at 11:52 AM, Manson, John
wrote:
> I would like to retract this post after I had a long conversation with
> my co-worker who is just back from leave.
>
> Sorry for the bother.
>
> ** **
>
> *From:* Manson, John
Robin Lee Powell wrote:
>
>So I've got some IPv6-only VMs set up that need to talk to the
>general internet for things like downloading packages. As you can
>imagine, this requires that they have NAT64 and DNS64, because lots
>and lots of things are IPv4 only.
>
>The problem is that many things
I would like to retract this post after I had a long conversation with my
co-worker who is just back from leave.
Sorry for the bother.
From: Manson, John
Sent: Friday, December 28, 2012 10:54 AM
To: 'bind-users@lists.isc.org'
Subject: Named stopped loging?
Good Day
Running 9.9.2 for about a mon
So I've got some IPv6-only VMs set up that need to talk to the
general internet for things like downloading packages. As you can
imagine, this requires that they have NAT64 and DNS64, because lots
and lots of things are IPv4 only.
The problem is that many things do *stupid shit* when given both
Good Day
Running 9.9.2 for about a month now with no worries.
Today I noticed only the reload message in the namedlog and not the zone
messages that are usually there after stopping and restarting the named process.
Worked fine on the 26th but not today.
Logs sample:
Dec 26 15:01:52 local@mercu
11 matches
Mail list logo
