What steps will reproduce the problem?
when asking for SRV _xmpp-server._tcp.sipwise.net
Frame 2: 89 bytes on wire (712 bits), 89 bytes captured (712 bits)
Ethernet II, Src: 82:39:8a:f4:df:6d (82:39:8a:f4:df:6d), Dst: 32:31:30:33:38:31 (32:31:30:33:38:31)
Internet Protocol Version 4, Src: 192.168.51.101, Dst: 192.168.200.30
User Datagram Protocol, Src Port: 37559, Dst Port: 53
Domain Name System (query)
[Response In: 3]
Transaction ID: 0x2242
Flags: 0x0100 Standard query
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 0
Queries
_xmpp-server._tcp.sipwise.net: type SRV, class IN
Name: _xmpp-server._tcp.sipwise.net
[Name Length: 29]
[Label Count: 4]
Type: SRV (Server Selection) (33)
Class: IN (0x0001)
3 14:44:24.613564 192.168.200.30 192.168.51.101 DNS 351 Standard query response 0x2242 SRV _xmpp-server._tcp.sipwise.net DNAME sipwise.com CNAME _xmpp-server._tcp.sipwise.com SRV 10 0 5269 sip.sipwise.com NS dns2.sipwise.com NS dns1.sipwise.com A 92.42.136.100 AAAA 2a02:1b8:7:2::dead:c0de A 92.42.136.30 AAAA 2a02:1b8:7:2::f00:ba2 A 92.42.136.31 AAAA 2a02:1b8:7:2::b1a:b1a
We always get:
Jan 24 14:03:50 sp1 (debug) prosody[19041]: adns: Sending DNS query to 192.168.200.30
Jan 24 14:03:50 sp1 (debug) prosody[19041]: adns: Sending DNS query to 192.168.200.30
Jan 24 14:03:50 sp1 (debug) prosody[19041]: socket: new connection established. id: 16968a0
Jan 24 14:03:50 sp1 (crit) prosody[19041]: general: Top-level error, please report:#12/usr/lib/prosody/net/dns.lua:691: table index is nil
Jan 24 14:03:50 sp1 (crit) prosody[19041]: general: #012stack traceback:#12#011[C]: in function 'loop'#12#011/usr/lib/prosody/net/server_event.lua:797: in function </usr/lib/prosody/net/server_event.lua:796>#12#011[C]: in function 'xpcall'#12#011/usr/bin/prosody:376: in function 'loop'#12#011/usr/bin/prosody:407: in main chunk#012#011[C]: ?
Zash
on
There's currently no support at all for DNAME in our DNS library.
Changes
tags Status-Accepted
titledns error when resolving domain with DNAME info net.dns does not support DNAME
Zash
on
This is the same traceback as in #1056 / #976 which is about to be fixed.
I'll convert this into a feature request for DNAME support.
What steps will reproduce the problem? when asking for SRV _xmpp-server._tcp.sipwise.net Frame 2: 89 bytes on wire (712 bits), 89 bytes captured (712 bits) Ethernet II, Src: 82:39:8a:f4:df:6d (82:39:8a:f4:df:6d), Dst: 32:31:30:33:38:31 (32:31:30:33:38:31) Internet Protocol Version 4, Src: 192.168.51.101, Dst: 192.168.200.30 User Datagram Protocol, Src Port: 37559, Dst Port: 53 Domain Name System (query) [Response In: 3] Transaction ID: 0x2242 Flags: 0x0100 Standard query Questions: 1 Answer RRs: 0 Authority RRs: 0 Additional RRs: 0 Queries _xmpp-server._tcp.sipwise.net: type SRV, class IN Name: _xmpp-server._tcp.sipwise.net [Name Length: 29] [Label Count: 4] Type: SRV (Server Selection) (33) Class: IN (0x0001) 3 14:44:24.613564 192.168.200.30 192.168.51.101 DNS 351 Standard query response 0x2242 SRV _xmpp-server._tcp.sipwise.net DNAME sipwise.com CNAME _xmpp-server._tcp.sipwise.com SRV 10 0 5269 sip.sipwise.com NS dns2.sipwise.com NS dns1.sipwise.com A 92.42.136.100 AAAA 2a02:1b8:7:2::dead:c0de A 92.42.136.30 AAAA 2a02:1b8:7:2::f00:ba2 A 92.42.136.31 AAAA 2a02:1b8:7:2::b1a:b1a We always get: Jan 24 14:03:50 sp1 (debug) prosody[19041]: adns: Sending DNS query to 192.168.200.30 Jan 24 14:03:50 sp1 (debug) prosody[19041]: adns: Sending DNS query to 192.168.200.30 Jan 24 14:03:50 sp1 (debug) prosody[19041]: socket: new connection established. id: 16968a0 Jan 24 14:03:50 sp1 (crit) prosody[19041]: general: Top-level error, please report:#12/usr/lib/prosody/net/dns.lua:691: table index is nil Jan 24 14:03:50 sp1 (crit) prosody[19041]: general: #012stack traceback:#12#011[C]: in function 'loop'#12#011/usr/lib/prosody/net/server_event.lua:797: in function </usr/lib/prosody/net/server_event.lua:796>#12#011[C]: in function 'xpcall'#12#011/usr/bin/prosody:376: in function 'loop'#12#011/usr/bin/prosody:407: in main chunk#012#011[C]: ?
There's currently no support at all for DNAME in our DNS library.
Changesdns error when resolving domain with DNAME infonet.dns does not support DNAMEThis is the same traceback as in #1056 / #976 which is about to be fixed. I'll convert this into a feature request for DNAME support.
ChangesTraceback should be fixed by https://hg.prosody.im/0.10/rev/fcf42bd7d067