Find CNAME target with DNS library?
Kurt
versions on the node.js DNS module? I see references to cname being a
parameter of the resolve callback in earlier versions, but that
appears to be gone now.
I need to somehow take an address with a CNAME record and check to see
where the CNAME is pointed.
Ben Noordhuis
CNAME lookup isn't supported (anymore? not sure if it ever worked).
I'll see if I can come up with a patch.
Kurt Mackey
through and see if I'm smart enough to patch it. :)
> --
> You received this message because you are subscribed to the Google Groups "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com.
> To unsubscribe from this group, send email to nodejs+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
>
>
Kurt Mackey
to do with the underlying c-ares lib. The query used for all the
other types doesn't actually work for cnames, so a patch for node
isn't as simple as it maybe should be.
Jérémy Lal
> After digging, it seems like this is something that's not really easy
> to do with the underlying c-ares lib. The query used for all the
> other types doesn't actually work for cnames, so a patch for node
> isn't as simple as it maybe should be.
To which other query CNAME would be closest to ?
There's a scheduled release for c-ares soon,
so it might be the right time to propose a patch.
Ben Noordhuis
> After digging, it seems like this is something that's not really easy
> to do with the underlying c-ares lib. The query used for all the
> other types doesn't actually work for cnames, so a patch for node
> isn't as simple as it maybe should be.
I just submitted the pull request. :)
https://github.com/ry/node/pull/424
Wasn't the easy fix I thought it would be, though. Turns out there is
a buglet in c-ares that stops it from parsing CNAME query replies.