[136325] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: quietly....

daemon@ATHENA.MIT.EDU (Greg Estabrooks)
Wed Feb 2 10:38:08 2011

Date: Wed, 02 Feb 2011 11:35:45 -0400
From: Greg Estabrooks <nanog@phaze.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <5CF16AD6-DDCC-4A72-AD30-9DFC653A0B6D@muada.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


Hi,

> But all of this could easily have been avoided: why are we _discovering_ DNS addresses in the first place? Simply host them on well known addresses and you can hardcode

So, when I take my laptop from Home to work, to the airport, to some 
random cyber cafe I should have to manually alter my DNS servers 
assuming I can find someone in the location who can tell me what they 
are ?? Or let me guess, I should hardcode  some public DNS servers which 
I can hopefully reach from where I am, hopefully is not down or having 
issues and hopefully I don't have poor latency to?

And here I always thought the D in DHCP stood for Dynamic.





home help back first fref pref prev next nref lref last post