network admin, ip addresses for webserver

[Niles Rogoff]

But the DNS lookup is for an internal hostname, it's not like you're
looking up google.com, you're looking up new-host-6.local, which takes
significantly less time because the router's internal DNS server already
has it, it doesn't have to forward the lookup. It does add some time, but
not probably 200ms. However, this latency is for each packet, not just the
start of a connection, so the faster the forward the better

On Mon, Oct 27, 2014 at 4:53 PM, Jacob Mansfield <cyberjacob at gmail.com>
wrote:

> On 27 Oct 2014, at 8:39PM, Niles Rogoff wrote:
> > My understanding is that on each inbound connection, the router will
> have to resolve the hostname to an internal IP address, which takes time
> and resources. You probably don't need to worry about it so long as the
> hostname and MAC address of the computer never change
>
> Very true. Routing a packet takes around 100-200 μs, whereas a DNS lookup
> takes around 200ms (200000μs).
> That sort of delay is far too much to add to the TCP stream, and could
> cause large delays and packet losses as the router struggles to catch up.
>
> Kind Regards,
> Jacob Mansfield
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20141027/9d8c7b64/attachment.html>