User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 Iceweasel/41.0.1 Build ID: 20151005010732 Steps to reproduce: The DNS has NAPTR and SRV records for TURN associated with fedrtc.org My script (on a WebRTC page) sets the ICE server name to fedrtc.org Actual results: tcpdump shows Firefox making A and AAAA queries for fedrtc.org. tcpdump does not show it making any NAPTR or SRV queries Expected results: Firefox should have queried the NAPTR and then SRV records and discovered the correct TURN server name, port and transport tuple. The expected resolution mechanism is described in RFC 5928: https://tools.ietf.org/html/rfc5928
Also reported to Chrome: https://code.google.com/p/chromium/issues/detail?id=559115
Seems like a networking related issue. Move bug to WebRTC: Networking component. Please advise.
Component: Untriaged → WebRTC: Networking
Product: Firefox → Core
Chrome also considers it to be a spec-compliance issue, but low priority.
Status: UNCONFIRMED → NEW
backlog: --- → webrtc/webaudio+
Ever confirmed: true
Priority: -- → P3
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
You need to log in before you can comment on or make changes to this bug.