Provide IPv6 DNS addresses #31

Closed
opened 2026-03-04 00:04:23 -05:00 by deekerman · 12 comments
Owner

Originally created by @ameshkov on GitHub (Aug 22, 2016).

Originally assigned to: @nkartyshov, @ameshkov on GitHub.

Read here the details:
https://blog.adguard.com/en/adguard-dns-beta/#comment-2846431854

We should do something about it.

Originally created by @ameshkov on GitHub (Aug 22, 2016). Originally assigned to: @nkartyshov, @ameshkov on GitHub. Read here the details: https://blog.adguard.com/en/adguard-dns-beta/#comment-2846431854 We should do something about it.
deekerman 2026-03-04 00:04:23 -05:00
Author
Owner

@TPS commented on GitHub (Oct 15, 2016):

Unblocking Disqus on that link seems to deadlock my browser consistently (transcript/translation requested, please 🙏), so I can't tell if this was brought up, but is this issue requesting IPv6 DNS address:

  • equivalents for the resolvers, for those who want/need IPv6 addresses for 176.103.130.130, 176.103.130.131, 176.103.130.132, & 176.103.130.134?
  • resolution/filtering so that all the functionality for IPv4 DNS replies is also provided for IPv6 1s?

I'd like both, so I can test replacing my current OpenDNS settings everyplace. Particularly, Windows's IPv6 implementation wants IPv6-formatted DNS addresses.

@TPS commented on GitHub (Oct 15, 2016): Unblocking Disqus on that link seems to deadlock my browser consistently (transcript/translation requested, please :pray:), so I can't tell if this was brought up, but is this issue requesting IPv6 DNS address: - _equivalents_ for the resolvers, for those who want/need IPv6 addresses for 176.103.130.130, 176.103.130.131, 176.103.130.132, & 176.103.130.134? - _resolution/filtering_ so that all the functionality for IPv4 DNS replies is also provided for IPv6 1s? I'd like both, so I can test replacing my current OpenDNS settings everyplace. Particularly, Windows's IPv6 implementation wants IPv6-formatted DNS addresses.
Author
Owner

@TPS commented on GitHub (Nov 11, 2016):

I ended up using http://en.toolpage.org/tool/ipv4-to-ipv6 to bulk-convert

176.103.130.130
176.103.130.131
176.103.130.132
176.103.130.134

to

0:0:0:0:0:ffff:b067:8282
0:0:0:0:0:ffff:b067:8283
0:0:0:0:0:ffff:b067:8284
0:0:0:0:0:ffff:b067:8286

which is, of course, same as

::ffff:b067:8282
::ffff:b067:8283
::ffff:b067:8284
::ffff:b067:8286

D'y'all mind testing? I'm not (yet) using AGDNS, but probably will soon.

@TPS commented on GitHub (Nov 11, 2016): ~~I ended up using http://en.toolpage.org/tool/ipv4-to-ipv6 to bulk-convert~~ ~~176.103.130.130~~ ~~176.103.130.131~~ ~~176.103.130.132~~ ~~176.103.130.134~~ ~~to~~ ~~0:0:0:0:0:ffff:b067:8282~~ ~~0:0:0:0:0:ffff:b067:8283~~ ~~0:0:0:0:0:ffff:b067:8284~~ ~~0:0:0:0:0:ffff:b067:8286~~ ~~which is, of course, same as~~ ~~::ffff:b067:8282~~ ~~::ffff:b067:8283~~ ~~::ffff:b067:8284~~ ~~::ffff:b067:8286~~ ~~D'y'all mind testing?~~ I'm not (yet) using AGDNS, but probably will soon.
Author
Owner

@Bluscream commented on GitHub (Nov 11, 2016):

The ISP needs to assign ipv6 adresses for the dns servers

@Bluscream commented on GitHub (Nov 11, 2016): The ISP needs to assign ipv6 adresses for the dns servers
Author
Owner

@Bluscream commented on GitHub (Jan 29, 2017):

Damn i wish ag ipv6 dns would be a thing now :)

@Bluscream commented on GitHub (Jan 29, 2017): Damn i wish ag ipv6 dns would be a thing now :)
Author
Owner

@koesherbacon commented on GitHub (May 24, 2017):

I'm not certain if this is still an open issue, but is there a roadmap that estimates when AdGuard DNS will have its own IPv6 addresses as well as the tried and true IPv4? Many thanks

@koesherbacon commented on GitHub (May 24, 2017): I'm not certain if this is still an open issue, but is there a roadmap that estimates when AdGuard DNS will have its own IPv6 addresses as well as the tried and true IPv4? Many thanks
Author
Owner

@ameshkov commented on GitHub (May 28, 2017):

At the moment we use two different hosting providers. One of them provides IPv6 connectivity and the other one does not.

The other problem is that we don't own an IPv6 block and using some random address is not an option.

So, once we buy an IPv6 addresses block, we can use it for at least some servers.

@vbagirov need you to assist me on this.

@ameshkov commented on GitHub (May 28, 2017): At the moment we use two different hosting providers. One of them provides IPv6 connectivity and the other one does not. The other problem is that we don't own an IPv6 block and using some random address is not an option. So, once we buy an IPv6 addresses block, we can use it for at least some servers. @vbagirov need you to assist me on this.
Author
Owner

@smed79 commented on GitHub (Jul 16, 2017):

Are there any news about IPv6 Adguard DNS addresses?

@smed79 commented on GitHub (Jul 16, 2017): Are there any news about IPv6 Adguard DNS addresses?
Author
Owner

@ghost commented on GitHub (Jul 16, 2017):

As soon as there are IPV6 addresses, I'm going to switch all my devices over as I'm unable to control the IPv6 DNS on my gateway. Being able to add the Adguard DNS IPv6 to my devices to override it would be wonderful.

@ghost commented on GitHub (Jul 16, 2017): As soon as there are IPV6 addresses, I'm going to switch all my devices over as I'm unable to control the IPv6 DNS on my gateway. Being able to add the Adguard DNS IPv6 to my devices to override it would be wonderful.
Author
Owner

@ameshkov commented on GitHub (Jul 17, 2017):

We've acquired an IPv6 addresses block, so we're close.

@ameshkov commented on GitHub (Jul 17, 2017): We've acquired an IPv6 addresses block, so we're close.
Author
Owner

@Snapy commented on GitHub (Oct 21, 2017):

@ameshkov Can you update readme with the now available IPv6 addresses ? TIA

@Snapy commented on GitHub (Oct 21, 2017): @ameshkov Can you update readme with the now [available](https://blog.adguard.com/en/dns-ipv6-support/) IPv6 addresses ? TIA
Author
Owner

@TPS commented on GitHub (Oct 21, 2017):

Also, update the regular/DNSCrypt sections of the apps w/ AG IPv6 options (like y'all have for OpenDNS, Babylon, D0wn Resolver, &c)?

@TPS commented on GitHub (Oct 21, 2017): Also, update the regular/DNSCrypt sections of the apps w/ AG IPv6 options (like y'all have for OpenDNS, Babylon, D0wn Resolver, &c)?
Author
Owner

@ameshkov commented on GitHub (Oct 22, 2017):

Done!
https://github.com/AdguardTeam/AdguardDNS

Regarding DNSCrypt, it will be updated in due course (the pull request was accepted recently, but we need to add one more).

@ameshkov commented on GitHub (Oct 22, 2017): Done! https://github.com/AdguardTeam/AdguardDNS Regarding DNSCrypt, it will be updated in due course (the pull request was accepted recently, but we need to add one more).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/AdGuardHome#31
No description provided.