Hi,

Sorry for the lame response time.

* Konstantin Khomoutov <flatw...@users.sourceforge.net> [2009-07-31 
15:59:28+0400]:
> 
> I think the pattern here is that whenever you have "nameserver" set to  
> "::1", the Erlang inet code fails to parse it from /etc/resolv.conf, and  
> the Erlang DNS reslover ends up being left without a usable nameserver.
>
As Sergei Golovan has done the donkey work[1] of ipv6 enabling the 
inet_res module in Erlang I think this is solved...in part.

It's probably not worth testing what happens when my /etc/resolv.conf 
file is nameserver-less as it's only going to be interpreted by Erlang 
as a nameserver less box.

> > In the next posting[1] in the 'inet6' thread I see:
> > ----
> > inet_db:add_ns({A,B,C,D}).  %% Name server must be IPv4, there is a fixme 
> > in inet_db.
> > ----
> > Looking at inet_db.erl I see "Fix IPv6 nameservers" all over the place,  
> > so it's a bug in upstream erlang it seems?
>
> Yes, it seems like a bug upstream -- while the inets module itself seems  
> not to have any problems using ipv6 addresses, the DNS code seems
> to lag behind the rest in this respect.
> 
> Now we have to figure out whether it is fixed in Erlang R13B which is  
> already in Squeeze.
> 
>From Sergei's posting...I doubt it :)

> > It is interesting that an A record lookup is made by ejabberd though in  
> > this situation, is there some fallback code being involked?  Should it  
> > be?
>
> Yes and no: the fallback to the A-record resolution is specified in the  
> spec (see the fourth paragraph of [1]), but the spec seems to only talk  
> about the case of a failed SRV query, in the sense of the query returned  
> the NXDOMAIN (or a similar) error, as I understand this.
> So what's the correct behaviour in the presense of a misconfigured DNS  
> resolver is not clear to me.
> 
Well it probably should not work at all.  I'm confused why A record 
queries are being spat out though rather than SRV.  You would either 
expect this to work or not at all.

Any ideas how to go about working out under what situation 
(/etc/resolv.conf content relating, when it cannot be parsed) would 
cause ejabberd to make A record lookups rather than SRV ones?

Cheers

[1] 
http://www.erlang.org/cgi-bin/ezmlm-cgi?3:mss:446:200908:laipdnhholjemjkgbbgp

-- 
Alexander Clouter
.sigmonster says:   I can resist everything except temptation. -Oscar Wilde



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to