|
Every DNS Question is cached.
This means: After your first connect to the server, nobody cares about the DNS Server anymore.
Example:
- Surf to google.com
- Your DNS Server gets asked what the ip is.
- If you browse google.com again in some minutes, the DNS Server is not asked again.
Second: If you have a router this does probably caching again, so even if your Operating System does not support caching, it gets cached there.
Third: I don't know if ISPs do this but I could imagine that they implements way to get a better response time for their DNS Server.
Please don't spread missinformation if you have no clue about networking.
|
On August 07 2011 01:24 Narfinger wrote:
Every DNS Question is cached.
This means: After your first connect to the server, nobody cares about the DNS Server anymore.
Example:
- Surf to google.com
- Your DNS Server gets asked what the ip is.
- If you browse google.com again in some minutes, the DNS Server is not asked again.
Second: If you have a router this does probably caching again, so even if your Operating System does not support caching, it gets cached there.
Third: I don't know if ISPs do this but I could imagine that they implements way to get a better response time for their DNS Server.
Please don't spread missinformation if you have no clue about networking.
Ok.
My Name is Shane. I am 22. I am about to finish my CNS degree at ITT. I can assure you that i probably know more about networking than you do. But were not really talking about networking, just DNS as a whole. Let me give you some information.
Your DNS server asks what the ip is, after it receives the IP, it follows that IP's route.
If you change the DNS server, it will recerive a differenet IP than your current DNS server is receiving. It will then follow that IP's Route.
Since every DNS follows a different Route, the response time to different servers can change. So editing your DNS can give you both a negative or positive experience in terms to many different things.
I agree with you. Except that you need to realize different DNS follow different Paths.
|
Ok. Im working on Vista/7 screencaps.
Does anybody know what I did wrong with the image. All i did was hit add image, put the imgur link in, and then hit ok. I then spoilered the image so the post wasn't super long. Is that wrong?
I can right click on 'image loading' and hit view image and see it fine. Can others do that?
|
Perhaps I am missing something but why would different DNS Servers give different IPs?
I don't see the point in letting a third party DNS server do any load balancing.
Could you clarify your statement please with your own words or some documentation on this?
|
I'll give you an example with Netflix.
Netflix servers work with whats called different CDN servers. Depending on the route you take (which is affected by your dns) will depend on which of Netflix's servers you hit. Certain servers are going to give you a higher ping than other servers.
It doesn't matter about the different ip. All that matters is your taking a different route, and the speed of that route.
Another example is how my callcenter works. I can ping Google from my pc and receive a different ip than the ip my customer receives when they ping Google. I will receive different ping times as well. It doesn't even matter tho if we do receive the same or a differenet ip. The route to the server is through different 'internet tubes' so to speak. So the reply speeds will change. YOUR CONNECTION WILL NOT GO FASTER. But you may be able to talk to the same server through a different route faster than the route your taking.
I dont understand why its difficult to grasp.
Im at point A, i need to get to point D. One DNS server may take you on a route that passes through point B and D, and then land on D. Another DNS route may be able to talk from A to C, and then land on D. You got to the same point, but you took a different route. Look at it like driving, same destination, different roads your taking.
|
Hi Shane,
Your saying that the DNS supplies the client with the network path it needs to take to the destination IP it has looked up ?
and another DNS server like google can give a ? better pathway to the host ?
IF you meant to tell us that.
That just does not make any sense.
Narfinger is confused aswell.
seems we interpret your post differently so please,
care to explain ?
|
wow thanks for this dude, trying this now
|
ohampatu,
The problem with your reasoning is that a DNS server only provides you with the endpoint -- the destination. It has nothing to do with routing.
|
The fastest route to the destination is determent by each router and routing protocol right ?
How can a DNS supply you with a path if it cannot know the network traffic at certain point along the route and your starting point because that is relative to me or it needs to know my second hop and make a path from there ?
|
I don't understand how this should technically bring improvement. Once the connection is established the DNS is not needed, so why should that improve lag issues?
@OP You can provide tracert examples to prove your point with the DNS. I would do it but I dont want to change DNS now.
|
On August 07 2011 00:59 DoXa wrote:
For own3D.tv viewers (Blizz EU Invite for example):
You can right-click on the stream and set your resolution to High, Normal or Low. Looked like alot of people didn't know that because there's no resolution setting button visible
edit: You also need to refresh the stream once for the settings to change
this defines only the image quality, as it's a setting for how flash should render the video to display.
it have absolutely nothing to do with the actual stream (or the "resolution button" as you call it), wich still will be the same hq stream, with same bitrate, same resolution etc...
|
maybe it's just the placebo, but it seemed to help so thx!
|
I thought the standard way for fixing lag was to simply stop your torrents....
If you're getting lag after that anyway you can flush your DNS (clear cache) as well
Simply open command prompt:
Open 'Run' then type 'CMD'
Type in:
ipconfig /flushdns
Easy as that
If you want to check your current DNS, go back to the CMD menu and type:
ipconfig /displaydns
|
On August 07 2011 01:56 Shenghi wrote:
ohampatu,
The problem with your reasoning is that a DNS server only provides you with the endpoint -- the destination. It has nothing to do with routing.
My thoughts exactly.
it should be impossible or impractical to do so if you think of it.
if the server receives a request for tl for example.
and then he gives a pathway to follow.
First think that comes to mind is that it cannot tell you a path relative to you because he can only make a path from the DNS to the destination.
or the DNS needs to order the client to fetch/find the path then wy do it because the client needs to do it any way. (and its outdated instantly)
It would force all who request the record along a pre determent path witch if traffic/request increase would lead to congestion/failure.
for it to be effective vs failure of nodes in the network it needs to check if the path it has is alive.
then you have to do that for each record/pathway that exists on the DNS.
ill stop my toughts here but it just does not make sense.
|
Yes, i can provide Tracert and NSlookup to prove my point.
The point is, every example I gave is true. Namely the Netflix example above. Differenet DNS will connect to Differenet CDN servers.
I have been trying to explain in non network talk. But it seems i need to teach everybody networking in order for it be believed. The following post alot of you wont get, but proves my point.
The following post is actually a post where using 3rd party DNS didn't work, but it gives some information on how DNS affects things.
+ Show Spoiler +
Problem #1 – DNS lookup times
The first problem is DNS lookup time. Historically this has not been an issue as many web sites operate off a single IP address and therefore the TTL (ie: how long your DNS resolver and computer can cache a response) has often been anywhere from 4-24 hours and higher.
However, this is 2011. The year where sites are increasingly using DNS for load balancing and failover. The year where the TTL is measured in seconds. This is the year where a slow DNS resolver will have a noticeable user impact and not only on the first request – but subsequent requests as well.
As an example, let’s say that you are browsing a web site that has a TTL of 20 seconds. Because your third party resolver takes 1 second to resolve the hostname, you will experience a 1 second delay when you first go to the web site and every 20 seconds thereafter while you continue browsing the site.
Let’s show this graphically. Using the excellent utility namebench, I ran a benchmark of how long it took my ISP (Internode) to resolve the Alexa top 250 web sites. The results are staggering.
In the first example, we have the fastest time it took to resolve a site. The fastest resolver was my ISP at 44ms. The next closest match was Google Public DNS at 4x that amount – 176ms
Problem #2 – Content Delivery Networks
Content Delivery Networks use carefully positioned global infrastructure to bring content closer to the end user. This results in faster download times and a much better experience. Depending on your DNS, will depend on what CDN you hooking up to. I dont know how JTV works, which is why I gave a Netflix example because its a streaming website. If you would all sit and consider for a second how some people in different contries randomly have issues with JTV.net, you'd see that I'm telling the truth.
Take for expamle: I have 2 pc's in my house. 1 I have my ISP's DNS. The 2nd I have Google's DNS. I have Netflix on both pc's. I choose to watch the SAME EXACT MOVIE. Both pc's will hook up to different CDN's.
|
I have yet to see how this can improve anything but the initial request, which is then cached. For your "tactic" to work, you should include the flush DNS command as well.
|
Why all the mistrust? Give it a try guys, maybe you'll be surprised.
|
On August 07 2011 02:22 Soulish wrote:
Why all the mistrust? Give it a try guys, maybe you'll be surprised.
Lol for real. It takes 2 mins to change it and change it back. If you dont believe me and you think your a network gosu. Do a tracert and nslookup before changing dns, and then do the same tracert and nslookup after changing dns. I can almost guarantee the results will not be the same, just similar. If your isp has slow lookup times, or times out and has to repeat lookup times, it will affect you
Either way, im not giving instructions thats gonna hurt. Just trying to help.
|
Is there any difference in changing the DNS in the router configuration page compared to changing it in Windows? I have my router settings directly using the openDNS IP
|
Either way, no matter if you are right or not, that discussion will go off road real fast, the title is misleading. Saying "how to fix your stream lag" means that you actually have a solution that works, rather than "If your isp has slow lookup times, or times out and has to repeat lookup times, it will affect you".
|
|
|
|
|
|
EPT
