[122570] in North American Network Operators' Group

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

Re: History of 4.2.2.2. What's the story?

daemon@ATHENA.MIT.EDU (Joe Abley)
Wed Feb 17 00:43:02 2010

From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAACUqDU5a27QSbUT84s99ecOAQAAAAA=@iname.com>
Date: Tue, 16 Feb 2010 21:42:26 -0800
To: frnkblk@iname.com
X-SA-Exim-Mail-From: jabley@hopcount.ca
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


On 2010-02-16, at 20:35, Frank Bulk wrote:

> Our nameservers handle both the authoritative and recursive traffic,

As general advice, and as an aside, don't do that. (Aside from anything =
else, you're inserting authoritative answers in a lookup path that might =
not be found by a parent delegation, e.g. if you host a domain for =
someone who subsequently takes it elsewhere without telling you.)

> If I understand your second sentence correctly, then yes, our DHCP =
server
> hands out the DNS servers, of which one of the three is outside our =
own
> network.

Thanks for the counter-example.


Joe=


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