New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 752573 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue webrtc:8102
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

WebRTC resolves TURN/TURNS/STUN servers with a trailing dot

Reported by g...@fig.org, Aug 4 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. Add a STUN server in /etc/hosts, say "12.34.56.78 turns.example.com"
2. Go to https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/
3. Fill out the details, stun:turns.example.com:3478
4. Hit "Gather candidates".

What is the expected behavior?
I expect to see the srflx candidates, as I do on Firefox 54.0.1.

What went wrong?
No candidates are gathered from the STUN server, and no connection attempts are seen in the server logs.  On investigation, chrome://net-internals/#dns shows:

turns.example.com.  IPV4  error:-105 (ERR_NAME_NOT_RESOLVED)

Did this work before? N/A 

Chrome version: 60.0.3112.78  Channel: beta
OS Version: CentOS 7
Flash Version: 

If I add "turns.example.com." to /etc/hosts, it works as expected.  Is there a reason for appending the dot, other than to break creative uses of /etc/hosts?

Thanks,
Michael.
 

Comment 1 Deleted

Comment 2 by g...@fig.org, Aug 4 2017

Works for me under Windows, Chrome/59.  Adding the entry without a trailing dot in C:\Windows\System32\Drivers\etc\hosts resolves the STUN server correctly when gathering ICE candidates, but doesn't show up in the #dns tab.
Labels: TE-NeedsTriageHelp
@Requesting triage help , as this issue seems to be out of TE-scope.

Thanks!
Components: Blink>WebRTC>Network
Mergedinto: webrtc:8102
Status: Duplicate (was: Unconfirmed)
Not sure why the trailing dot makes a difference, but the root cause should be fixed. See linked issue.

Sign in to add a comment