[27808] in North American Network Operators' Group
Re: Alternative to BGP-4 for multihoming?
daemon@ATHENA.MIT.EDU (Pete Templin)
Tue Mar 14 12:11:50 2000
Date: Tue, 14 Mar 2000 11:06:40 -0600 (EST)
From: Pete Templin <templin@urdirect.net>
Reply-To: Pete Templin <templin@urdirect.net>
To: nanog@merit.edu
In-Reply-To: <Pine.BSF.4.20.0003140925010.511-100000@alive.znep.com>
Message-ID: <Pine.LNX.3.96.1000314105757.5521C-100000@alpha.urdirect.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
On Tue, 14 Mar 2000, Marc Slemko wrote:
> Saying "the clients's primary DNS" is misleading. There is no way to know
> what the "primary" DNS server is for a zone, and there may not even be
> what is typically known as a primary.
And to be done correctly, what "zone" is important? Would it be the
server (primary/secondary/master/slave) authoritative for the reverse zone
containing the client IP address? The domain name of the client found via
reverse DNS? The caching proxy server in between (at the client end, or
perhaps at the server end)?
What if it's a UUNet resold modem to a client of iAmerica - what server
gets used then? We know that UUNet's DNS servers are likely to not be
located close (in net terms) to the client, and how do we know what DNS
servers are being assigned to the client?
Or what if my clients get assigned dns servers in 192.168.254/24? Sounds
to me like it's not a valid geographic identifier.
Pete
--
Peter J. Templin, Jr., CCNA
Systems and Networks Administrator
On-Line Internet Services - URDirect.net
A division of Global On-Line Computers
2414 Babcock Rd. Suite 106 templin@urdirect.net
San Antonio, TX 78229 (210)692-9911
