|
On Wed, 28 Sep 2005, Dan Trainor wrote:
Hello, all -
Sorry to not reply with the correct headers here; I just signed up for
this list, and it just so happened that Jacob Coby asked a question that
was similar to the one which I wanted to ask, so here goes.
and what is your question?
The problem with DNS is not the servers but the resolvers
AFAIK. The nameserver can be hung in a way that the client
resolver interprets as there being no IP for the name, and
it doesn't go onto the next nameserver in the list. A client
should be able to differentiate no answer from one saying
that there is no resolution for that name. I can't imagine
how the broken clients (in all OSs) are going to be fixed
and we aren't the people to fix it.
The nameresolving process is totally broken
http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.services.general.html#name_resolution
and no-one seems to have noticed. The only solution I can
see is to present a perfect nameserver via something like
LVS, where the client never sees a bad nameserver.
Joe
--
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!
|
