[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
History of 4.2.2.2. What's the story?
- Subject: History of 4.2.2.2. What's the story?
- From: patrick at ianai.net (Patrick W. Gilmore)
- Date: Tue, 16 Feb 2010 22:33:27 -0500
- In-reply-to: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAADT0eC+Ss13TLme8r+R6s5VAQAAAAA=@iname.com>
- References: <[email protected]>	<[email protected]>	<[email protected]>	<[email protected]>	<[email protected]>	<[email protected]>	<!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAADT0eC+Ss13TLme8r+R6s5VAQAAAAA=@iname.com>
On Feb 16, 2010, at 10:24 PM, Frank Bulk wrote:
> We do.  It's at our upstream provider, just in case we had an upstream
> connectivity issue or some internal meltdown that prevented those in the
> outside world to hit our (authoritative) DNS servers.  Of course, that's
> most helpful for DNS records that resolve to IPs *outside* our network. 
What you describe - authorities used by people off your network to resolve A records with IP addresses outside your network - is not what Joe was describing.  What the recursive name server your end users queried to resolve names, the IP address in their desktop's control panel, outside your network?
I can see a small ISP using its upstream's recursive name server.  But to the rest of the world, most small ISPs look like a part of their upstream's network.
-- 
TTFN,
patrick
> ===
> <snip>
> 
> For what it's worth, I have never heard of an ISP, big or small,  
> deciding to place resolvers used by their customers in someone else's  
> network. Perhaps I just need to get out more.
> 
> Joe
> 
> 
>