The DNS is Domain Name Lookup. You see the website names as http://www.solent-renegades.co.uk, but this gets converted into an IP address In this case 108.161.188.130 so your web browser knows where to get the data from. The names are just put there for easy reading for humans, its all a bunch of numbers behind the scenes.
So when you type in a website name, it goes to a name server, and grabs the details. These names servers are dotted around the world. Our DNS settings are on the old windows website server. By moving these settings to the new dedicated server, we should be able to decrease the look up times.
Testing a page from the content delivery network, we are downloading very quick, at 46ms. Alstohug we have waster 366ms in the look up.
Although by re running the same test, its remembers the DNS.
So repeat pages are quick as your computer remembers previous lookups, just wanted to speed up the initial connection time.
looking up Solent Renegades Car Club will be perhaps 366ms, but then so will looking up cdn.solent-renegades.co.uk as its technically a different location. Which could add another 300ms look up to the total page load time, although many things are loaded in parallel.
So when you type in a website name, it goes to a name server, and grabs the details. These names servers are dotted around the world. Our DNS settings are on the old windows website server. By moving these settings to the new dedicated server, we should be able to decrease the look up times.
Testing a page from the content delivery network, we are downloading very quick, at 46ms. Alstohug we have waster 366ms in the look up.
# | Resource | Content Type | Start Offset | DNS Lookup | Initial Connection | SSL Negotiation | Time to First Byte | Content Download | Bytes Downloaded | Error/Status Code | IP | Location* |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | http://cdn.solent-re...icture26021-202.html | text/html | 0.397 s | 366 ms | 31 ms | - | 45 ms | 1 ms | 8.1 KB | 200 | 108.161.188.130 | NetDNA |
Although by re running the same test, its remembers the DNS.
# | Resource | Content Type | Start Offset | DNS Lookup | Initial Connection | SSL Negotiation | Time to First Byte | Content Download | Bytes Downloaded | Error/Status Code | IP | Location* |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | http://cdn.solent-re...icture26021-202.html | text/html | 0.029 s | - | 29 ms | - | 41 ms | 2 ms | 8.1 KB | 200 | 108.161.188.130 | NetDNA |
So repeat pages are quick as your computer remembers previous lookups, just wanted to speed up the initial connection time.
looking up Solent Renegades Car Club will be perhaps 366ms, but then so will looking up cdn.solent-renegades.co.uk as its technically a different location. Which could add another 300ms look up to the total page load time, although many things are loaded in parallel.
Last edited: