-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dnseval: displaying the IP TTL? #31
Comments
The idea of guessing hop count to DNS server is interesting, but I am not sure if people expect to see IP TTL as the output of performance evaluation. Maybe there is a better way to do this. Another question is that ( given dnseval sends multiple requests to each server) what if all TTLs are not equal due to routing issues in the path? |
Well, to my mind this is interesting. ;) For example: I have three name servers on the Internet but I am interested which one is "closest" to my current location. I am not only intereseted in time but also in hop counts.
Yes, good question. Maybe answering with the range of all requests? |
Note: I did a quick research on this and it seems we cannot set |
Ok, thanks for the info anyway. |
Just another idea: Could you add a column to dnseval to display the TTL (hop limit) value of the IP packet? This could give some ideas on "how far" the DNS server is.
Well, since this is not a traceroute (which would display the hop count exactly), you can only display the received TTL. Since some servers start by 64 while others start by 256 (or any other value), only experts can use the provided information, such as "if it displays a 56 I suppose it is 8 hops aways", or the like.
What do you think about that?
The text was updated successfully, but these errors were encountered: