Request: Control reverse dns on tunnel endpoint
Shadow Hawkins on Monday, 06 June 2011 22:11:19
In order to make the traceroute a little more explaiatory i suggest that over the web interface one can change the reverse lookup of the tunnel-endpoints.
Tracing route to hermod.hgv10.aconsult.no [2001:16d8:eeb3:1::2]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms heimdall.l41.aconsult.no [2001:16d8:eeb8:1::1]
2 35 ms 35 ms 35 ms gw-342.osl-01.no.sixxs.net [2001:16d8:ee00:155::1]
3 46 ms 46 ms 45 ms cl-331.osl-01.no.sixxs.net [2001:16d8:ee00:14a::2]
4 45 ms 45 ms 45 ms hermod.hgv10.aconsult.no [2001:16d8:eeb3:1::2]
Trace complete.
I would prefer to be able to control the ip adress of the SixXS adapter on my host, and also, but a little less important, the reverse dns of the pop ip. Not neccesarly with records on my own dns, but what is deemed most fitting by people having a better understanding of the SiXS core.
-Anders
Request: Control reverse dns on tunnel endpoint
Jeroen Massar on Thursday, 23 June 2011 17:28:20
The traceroute perfectly shows which hosts and networks are involved.
Tunnels are considered tranfer networks between the PoP and the enduser, as such they have proper reverses.
Posting is only allowed when you are logged in. |