New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Round-robin, NSD and multiple IPs - Pleast Test!
If you visit the following URL, what does the location show?
me@home:~$ host test.blite.ca test.blite.ca has address 204.12.214.x test.blite.ca has address 78.129.133.y
I'd thought that multiple IPs for an A record were used in round-robin fashion. But for me, using NSD for DNS hosting, it seems to be dependent on the order they appear in the zonefile, and on whether caching DNS servers respect that order. It seems that most do.
So the great majority of traffic will arrive at the first IP listed in NSD's zonefile.
Comments
On a server...
$ curl http://test.blite.ca/ <p style='margin-top:50px; font:16pt sans-serif; text-align:center; color: #444'> Location: Maidenhead, UK </p>Kansas here from UK
Location: Kansas City, Mo., USA
Location: Maidenhead, UK
Is that your site? If so, how did you do that?
Kansas from MX
What resolvers are used by the server?
It's just a different static html file on each server....
here I get: Location: Maidenhead, UK
Location: Kansas City, Mo., USA
I am from the UK
So far...
Kansas: 5
Maidenhead: 3
But the sample is too small
Please add your test!
Kansas from East Coast, US
I got Maidenhead, UK from my here (UK)
Got Kansas from UK
Kansas - from eastern canada
Kansas: 8
Maidenhead: 4
Keep 'em coming
I tried again and i got: Location: Kansas City, Mo., USA
Interesting. If I understand correctly, that means your dns resolvers are providing round-robin service.
If you try again at 10 minute intervals, closing & restarting your browser, it would be even more interesting.
Thanks
Kansas from UK.
Kansas from Finland.
No,I mean how did you set up that round robin thingy.
I always thought that on v4 the order of records is random.
On IPv6 though, the selection is done by "longest matching prefix".
Location: Maidenhead, UK. I'll try again after 10 minutes. I hope this helps you.
edit: 10 minutes later, I got the same result
Maidenhead, UK from east Canada
Maidenhead from the UK - Kansas from NL VPS
UK from L.A
FWIW, both 'host' and chrome will rotate the ordering for me. I have to manually clear chrome's cache though, otherwise its sticky.
chrome://net-internals/#dns
Kansas City from NYC
Kansas City from a Moscow VPN
Kansas City from a Pune VPS
Maidenhead from a Cape Town VPS
Kansas City from a Beijing VPN
Kansas City from a Panama VPN
Location: Kansas City, Mo., USA via seattle
Location: Maidenhead, UK from Asia
you can use pinging websites like http://www.super-ping.com/?ping=http://test.blite.ca/&locale=en to get faster samples. you can see that the ips can change from test to test for each location this is because the dns is not being cached in the same way as when a user is browsing the page from their browser and also, you should direct some traffic to the website and check the stats over both pages when you can get a big enough sample.
Also this site is showing some more varied results in the resolving: http://www.watchmouse.com/en/ping.php?vtt=1376362037&varghost=http://test.blite.ca/&vhost=_&vaction=ping&ping=start