Edge browser does not utilize IPv6

Question

Hello

I am using edge chromium 86 and have a valid IPv6 assigned to my computer. However, edge browser does not resolve domain names to ipv6 addresses and will only attempt connecting using ipv4

Testing with ipv6-test.com on a fresh profile on edge, shows ipv6 connectivity as "not supported", however the same test works flawlessly on Firefox browser.

I found out that I can't open urls like (ipv6.google.com) on edge (works on firefox), but typing the ipv6 address [2a00:1450:400e:80e::200e] directly works fine, so I'm concluding there is a problem with dns, but I couldn't resolve it by switching to other dns providers.

Any help would be appreciated

Thank you

Answer 1

4745/5000

Hi, how are you ?!

We are happy with your contact!

IPv6 and Microsoft Edge or Internet Explorer

To be certain that the IPv6 protocol is being used to access the website, substitute an IPv6 literal address surrounded by square brackets in the URL in place of a domain name.

For example,

http://ipv6.test-ipv6.com

becomes

http: // [2001: 470: 1: 18 :: 119].

For additional information, refer to Request For Comments (RFC) 3986 "Uniform Resource Identifier (URI): Generic Syntax".

(Caution: This substitution can sometimes fail. Explanation of possible reasons for this are available. If you encounter problems, review the Broken User FAQ article found on that website for several possible explanations. For even more possible explanations, review this article on the ARIN IPv6 wiki.)

If it is necessary to specify a port number as part of the URI, it would follow the IPv6 literal address (as is the case with IPv4 addresses).

For example, http://ipv6.test-ipv6.com:443 becomes http: // [2001: 470: 1: 18 :: 119]: 443.

Note 1: Neither Edge nor IE can browse IPv6 websites if configured to use a proxy server that does not support IPv6. When Edge or IE is configured to use a proxy server, name resolution requests for websites are forwarded to the proxy server. Unless the proxy server is IPv6-enabled, proxy-based requests for local or remote IPv6 web pages will not work.

To disable use of a proxy server in any version of Windows:

1. Tap or click Internet Options in the Control Panel.
2. In the Internet Options dialog box, tap or click the Connections tab, then tap or click LAN Settings.
3. In the Local Area Network (LAN) Settings dialog box, clear the Use a proxy server for your LAN checkbox and tap or click OK.
4. Tap or click OK to save changes to Internet Options and exit.

To disable IE use of a proxy server:

Tap or click on the gear-wheel (Tools, Alt + X, Gear / Configuration) in the upper right hand corner of the window, then tap or click Internet Options. Then perform steps 2 through 4 above.

To disable Edge use of a proxy server:

1. Tap or click on "Settings and more" (...) in the upper right hand corner of the window.
2. Scroll down and tap or click on "Settings".
3. Scroll down and tap or click on "View advanced settings"
4. Tap or click on "Open proxy settings" under "Proxy setup".
5. Set "Use setup script" and "Use proxy server" to Off and exit Settings.

Note 2: If for some reason you need to use the Universal Naming Convention [UNC] path name that must include an IPv6 literal address to test access to a web page on a shared folder, be forewarned that the colon is an illegal character in a UNC path name. For just this reason, Microsoft has implemented a transcription algorithm that uses a second-level Internet domain, ipv6-literal.net. (The ipv6-literal.net domain is registered to Perfect Privacy, LLC, but don't let that hinder you.) IPv6 addresses may be transcribed by substituting a dash for each colon and appending the ipv6-literal.net domain, as follows :

2001: 0db8: 85a3: 08d3: 1319: 8a2e: 0370: 7348

would be written as

2001-db8-85a3-8d3-1319-8a2e-370-7348.ipv6-literal.net

and the resulting URI will then be directly resolved by Microsoft software without DNS queries to any nameservers. When a zone index is part of a link local IPv6 address, substitute the letter "s" for the percent sign as follows:

fe80 :: 3% 1

would be written as

fe80--3s1.ipv6-literal.net.

Note 3: Access to web pages on UNC path name-specified shared folders with an included IPv6 or IPv4 literal address is typically prohibited by Edge and most versions of IE unless the shared folder is explicitly added to the Trusted sites zone under the Security tab in the Internet Options dialog box.

Good luck!

If this information was useful, please mark it as a "Useful" answer and click on "I solved my problem", if your question has not been solved, please post again here. Thanks for contacting the Microsoft Community!

Please don't forget to rate my service!

Hope this helps!

Sincerely,

Jediael Elias Corrêa

Answer 2

Hello and thank you for your quick response

As mentioned in the original post, typing a literal address into the address bar such as (http://[2001:41d0:701:1100::29c8]/) does indeed work as expected. However, any v6 only domain name such as (http://2001-41d0-701-1100--29c8.ipv6-literal.net/)  will fail to connect with ERR_NAME_NOT_RESOLVED error. Other browsers including Internet Explorer can open the URL just fine. Problem exists solely on edge

I do not have any proxy configured on my computer and I have disabled every addon on edge but problem persists.

Thank you again

Edit: To clarify, I can connect to dual stack domains but edge will only use IPv4 to connect to such domain names.

Answer 3

Hi,

Thank you for your return!

Please check the procedures below:

First access this link to see if your question is answered:

https://www.ionos.com/digitalguide/hosting/tech...

And the Option below:

First restart your system and see whether problem is resolved or not. If not, you can follow below steps

1: Use the Network Troubleshooter

Open Start> Settings> Update & security> Troubleshoot

Scroll down> Click Network adapters> Click Run the Troubleshooter

2 - IP and DNS Setting

Type ncpa.cpl in Windows start search (Cortana)> Right click on your network> Properties> Select Internet Protocol Version 6 (TCP / IPv6)> Hit properties> Make sure below ones are checked

Obtain an IP Address Automatically

Obtain DNS Server Address Automatically

You can also try Google DNS

Select Use the following DNS Server Addresses

Preferred DNS Server - 8.8.8.8

ALternate DNS Server - 8.8.4.4

Try Open DNS

Preferred DNS server: 208.67.222.222

Alternate DNS server: 208.67.220.220

3: Use Networking Commands

Type cmd in Windows Start Search box

Right click on cmd.exe> ​​Run As Administrator

Type netsh winsock reset and press Enter

Type netsh int ip reset and press Enter

Type ipconfig / release and press Enter

Type ipconfig / renew and press Enter

Type ipconfig / flushdns and press Enter

4: Turn Off Firewall temporarily. Test is by turning off anti-virus and malware protection softwares. Enable them after testing is over,

5: Rollback the Driver

Windows Key + X> Click Device Manager> Expand Network Adapter

Right click on your network adapter> Click Properties

Go to Driver tab> If there is rollback option, click it

Restart your computer

6: Update network driver from manufacturer's website

Go to the website of the network adapter's manufacturer or computer's manufacturer> See if some driver is released for your model and OS

If yes, download that> Install the downloaded driver

Restart your computer

7: Network Reset (Last Resort)

Windows Key + i> Network & Internet> Status> Network Reset

Reboot your computer

Source - https://support.microsoft.com/en-us/help/10741/...

If possible to inform more details of what is happening we will do our best to solve your problem!

If this information was useful, please mark it as a "Useful" answer and click on "I solved my problem", if your question has not been solved, please post again here. Thanks for contacting the Microsoft Community!

Please don't forget to rate my service!

Hope this helps!

Sincerely,

Jediael Elias Corrêa

Answer 4

Hey there Lowix,

I know this was posted quite a while ago but I wanted to check in and confirm if you're still seeing this error on the latest version of Microsoft Edge. The team took a look and was not able to reproduce this on the latest version, and confirmed that several fixes in this area have gone out since Version 86. If you are still seeing this, please let me know!