What you mention above is like trying to apply the logic of saying that if you travel on a highway, you can travel 120km/hour for 1km, but you can't for 8000km. Well actually you can. Yes time wise it will take a while to travel 8000km, but it won't affect your speed on the highway.
i don't know where you are getting your logic from but if you want to follow the example of the highway
it is agreeable that the distance doesn't make a difference for speed but the distance does make a difference to the chance of congested points on your route
and the amount of time to travel to your destination
take for example from joburg to durban on a clear highway with only you it would take so long but there could be traffic on the route out of joburg and then clear and then traffic at the toll points
all that affects your speed
the distance factor is like travelling from joburg to durban compared to joburg to cape town
they would take a different amount of time to travel to
So in summary:
Distance only affects latency and has absolutely no bearing on the speed of which data can travel.
logic again
our download speeds are measured at Kb or Mb per second
so if it takes 1 second to get the information compared to 3 seconds because its a further distance there will be a speed difference
Secondly, data does not travel through DNS servers. DNS servers merely issue the IP addresses for a domain name or ptr record. When data travels over the internet, it doesn't do DNS lookups for each router it passes through. Yes your traceroute program does DNS lookups, but you can turn that off on a traceroute query.
all data needs to travel through DNS server
the DNS servers tell the data where it needs to go
the web works on IP addresses not server names and the DNS servers translate the server names to IP addresses and keep a record of routes to where data needs to go
please confirm that the person you are saying is wrong before posting
instead just posting because you don't believe it is possible