<p dir="ltr">sent from Google nexus 4<br>
kindly excuse brevity and typos.<br>
On 25 Feb 2014 05:24, "manning bill" <<a href="mailto:bmanning@isi.edu">bmanning@isi.edu</a>> wrote:<br>
><br>
> Answers below:<br>
><br>
><br>
> /bill<br>
> Neca eos omnes. Deus suos agnoscet.<br>
><br>
> On 24February2014Monday, at 20:17, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>> wrote:<br>
><br>
> > sent from Google nexus 4<br>
> > kindly excuse brevity and typos.<br>
> > On 25 Feb 2014 03:02, "manning bill" <<a href="mailto:bmanning@isi.edu">bmanning@isi.edu</a>> wrote:<br>
> > ><br>
> > > (very local) root server. Why would that be better for you/us?<br>
> > ><br>
> > > if the presumption is low latency name resolution, this might be reasonable, if there was poor/no connectivity<br>
> > > to the rest of the Internet _and_ no caching locally.<br>
> > ><br>
> > Yeah poor is more like it as if there were no connectivity at all then there won't be a need to use internet resource better.<br>
><br>
> If bandwidth is a concern, then you don;t want a root server, you want a hefty robust cache.<br>
><br>
Did my mail imply that bandwidth is the issue?(well maybe) however If a root server is as close as possible wouldn't latency be relatively better. I have explained the mobile to ISP to name server scenario in my pervious mail.</p>
<p dir="ltr">> > ><br>
> ><br>
> > > The downside of a local root server is that the root server is a global resource and will be expected to field queries<br>
> > > from anywhere on the Internet… Which is why (many years ago) we installed and then removed a root server<br>
> > > from Australia, since they didn’t want to pay for the cost of fielding global DNS queries. Costs have changed since<br>
> > > then, but the basic presumption is still there - a root server is expected to answer DNS priming queries from _ANYWHERE_<br>
> > > on the Internet, not jus those queries local to you.<br>
> > ><br>
> > You are very right about this and this perhaps is one of the reasons why some ISPs don't won't to support hosting such servers especially in my region where bandwidth cost is still on the high side. (Which is one of the processes I refer)<br>
><br>
><br>
> Again, you really don’t want a root server….<br>
><br>
Maybe you should tell me the cost you are referring to which made you drop your root server in Australia as I think this still comes down to bandwidth required to serve the rest of the world.</p>
<p dir="ltr">Cheers!<br>
></p>
<p dir="ltr">><br>
> > ><br>
> > > /bill<br>
> > > Neca eos omnes. Deus suos agnoscet.<br>
> > ><br>
> > > On 24February2014Monday, at 7:53, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>> wrote:<br>
> > ><br>
> > > > On Mon, Feb 24, 2014 at 4:38 PM, Steve Crocker <<a href="mailto:steve@shinkuro.com">steve@shinkuro.com</a>> wrote:<br>
> > > > Marilyn, et al,<br>
> > > ><br>
> > > > Thanks. Two comments about root servers…<br>
> > > ><br>
> > > > 1. A list of which countries have root servers and which do not is the beginning but not the end of the discussion. The technical question is whether a locale is being served well enough. "Well enough" is usually measured in terms of delay to get an answer to a look up, e.g. 89 milliseconds, and reliability, e.g. answers are received 99.923% of the time. (Both of the numbers in the previous sentence are illustrative and not related to any actual measurement. I made them up as I typed.) On the other hand, many people seem concerned with political questions, e.g. which countries are important enough to have root servers. It would help the discussion to know what questions are being asked. The list of root server locations may or may not be relevant.<br>
> > > ><br>
> > > > For me, i am not really about the political aspect, just as you indicated the more local the root is the better for us.<br>
> > > ><br>
> > ><br>
><br>
</p>