Skip to content
This repository has been archived by the owner on Jun 18, 2022. It is now read-only.

Resolve Domains. #16

Open
martafolf opened this issue Jan 23, 2017 · 2 comments
Open

Resolve Domains. #16

martafolf opened this issue Jan 23, 2017 · 2 comments
Assignees
Milestone

Comments

@martafolf
Copy link

Have the ability to automatically distinguish between IP's and Domains being input by the user, and resolve these to execute the tests on.

Allow to select v4 and v6, potentially with default to one of them. (Up to you.)

@Fusl Fusl self-assigned this Jan 23, 2017
@Fusl Fusl added this to the v2 milestone Oct 2, 2020
@totoCZ
Copy link

totoCZ commented Oct 15, 2020

FYI this will break services that use EDNS to give you different IPs based on source

Also, right now we have two different commands and it auto defaults to IPv4, so you can't ping google over v6 with the domain name.
I think the only way to fix that is resolve the domain and set the command to v6 if it has AAAA records. (but resolve it on the probe again, unless you enable resolving on mtr.sh server)

@Fusl
Copy link
Owner

Fusl commented Oct 16, 2020

FYI this will break services that use EDNS to give you different IPs based on source

It won't since each probe will resolve the domain instead of the frontend server doing so.

Also, right now we have two different commands and it auto defaults to IPv4, so you can't ping google over v6 with the domain name.

A fix for this is actually already implemented and live on https://mtr.sh/, will be backported into the git repo with the next big v1 update.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants