What you don't understand is that I do not have the technical
understanding at the detailed level that is required to get it all
right, but my mail forwarder at ics.uci.edu is upportive and only puts
in the NMA.COM zone file what I agree to have put there. He controls
the passward, but does not
Michael Sondow wrote:
It's not delegated to the tech contact. It's arrogated by the
tech contact.
There's a big, big difference. The only ISP who lets the client
have control
over the zone file is pgmedia, where the client is not only the admin and
billing contacts but also the tech
Einar Stefferud a écrit:
And, for Michael's information, the fact that he has contractred with
an ISP to do everythig for his DNS Zone, and not let him have password
control of it is his decision and not a feature of the DNS!
In my own case, I cvontrol all aspects of the content of my
In message 001401be52fb$9ddc9320$010a@jbr, "John B. Reynolds" writes:
Michael Sondow wrote:
Einar Stefferud a écrit:
I agree with this concern, and I suggest that the initial membership
be defined in some other more well defined way. One suggestion that
makes sense to me is
All of them! (see Eberhard's question below;-)...
I also agree that the initial members of the startup DNSO should be
the Zone Administrators and not the Technical Contacts!
And, for Michael's information, the fact that he has contractred with
an ISP to do everythig for his DNS Zone, and not
At 09:49 PM 2/7/99 -0500, Michael Sondow wrote:
John B. Reynolds a écrit:
Every domain name holder directly or
indirectly administers a DNS zone file. Are you sure you're not
confusing "DNS zone" with "root zone"?
No, the domain holders don't administer zone files. That's done by the ISPs
Michael,
John is right.
In message [EMAIL PROTECTED], Michael Sondow writes:
John B. Reynolds a =E9crit:
You administer your zone indirectly by controlling which ISP runs it
directly.
Administer the zone indirectly? What are you talking about? Is this
a game of semantics to you?
In message [EMAIL PROTECTED], "Roeland M.J. Meyer" wri
tes:
At 09:49 PM 2/7/99 -0500, Michael Sondow wrote:
John B. Reynolds a écrit:
Every domain name holder directly or
indirectly administers a DNS zone file. Are you sure you're not
confusing "DNS zone" with "root zone"?
No, the
You contact with an ISP to create and maintain a zone file on your behalf.
If you don't like what they do with it, you can move to another
ISP or make
other arrangements. Ultimate control remains vested in you. I don't see
how I could make this any more clear than I already have.
Oops,
Kent Crispin wrote:
Running the hearing slows down the process, intrinsically. A hearing
takes time that would have been spent doing other things. As long as
I am guaranteed a "fair hearing" at will, I can slow down the
process.
If a hearing catches and corrects a problem before the process
John B. Reynolds wrote:
5.11 Further Review of Changes
Whenever a proposal has been changed as a result of
the preceding processes, any changes resulting from
such processes shall be republished on the DNSO
website and subject to review under the prior
provisions of this section.
My
Translation: Expediency is more important than fairness
David Schutt
Running the hearing slows down the process, intrinsically. A hearing
takes time that would have been spent doing other things. As long as
I am guaranteed a "fair hearing" at will, I can slow down the
process.
Put it
Not a good example, my browser timed out.
There are lots of experimental and/or educational systems out there, I'm
more interested in commercial services that can take a spike without
gasping.
David Schutt
Linux and BIND are both free software. The real sticking point is the
requisite
On Mon, 8 Feb 1999, Roeland M.J. Meyer wrote:
At 09:49 PM 2/7/99 -0500, Michael Sondow wrote:
John B. Reynolds a écrit:
Every domain name holder directly or indirectly administers a DNS zone
file. Are you sure you're not confusing "DNS zone" with "root zone"?
No, the domain holders
On Mon, Feb 08, 1999 at 12:16:50PM -0500, Jay Fenello wrote:
At 2/8/99, 11:48 AM, Kent Crispin wrote:
I am not talking about there being just *one* hearing. As soon as
the first FH concludes, the second one will be requested, and then
after that the third, and so on. As far as I can see,
In message [EMAIL PROTECTED], Michael Sondow writes:
The average client of an ISP, that is, the average domain name
holder, cannot tell the ISP what to put into their zone file. I've
had trouble with every single one of the five ISPs I've used because
of this, and I've heard the same stories
Roeland M.J. Meyer a écrit:
There is some argument that one can use a Windows machine for primary DNS.
I'm a typical end-user. I have a laptop running Windows95. There are
configuration pop-ups for TCP/IP and DNS confirguration. But I've never seen
a book anywhere, and I've been looking for
Good constructive and useful criticism as I read it;-)...
From your message Sun, 7 Feb 1999 10:42:42 -0600:
}
}William X. Walsh wrote:
}
} I call for a vote of participants on this list for which draft
} they support.
}
} It is time to vocalize your support, and clearly indicate who you
}
I would have to see the specific wording, but my initial reaction is that
the changes you suggest would largely answer my concerns (although I would
still prefer explicitly defined initial constituencies), along with a
revision to Section 5.9 similar to that suggested by AIP and NSI.
I am not
Michael Sondow wrote:
Einar Stefferud a écrit:
I agree with this concern, and I suggest that the initial membership
be defined in some other more well defined way. One suggestion that
makes sense to me is "Anyone with a DNS Zone file to administer" to be
used to elect an INITIAL Names
John B. Reynolds a écrit:
How would this give control to ORSC?
Alright, perhaps my reaction was slightly exaggerated. Let's just say it's
strictly in their interest, to the direct detriment of other interests, my
own for example.
Every domain name holder directly or
indirectly administers
Michael Sondow wrote:
John B. Reynolds a écrit:
Every domain name holder directly or
indirectly administers a DNS zone file. Are you sure you're not
confusing "DNS zone" with "root zone"?
No, the domain holders don't administer zone files. That's done
by the ISPs
and the layers
John B. Reynolds a écrit:
You administer your zone indirectly by controlling which ISP runs it
directly.
Administer the zone indirectly? What are you talking about? Is this a game
of semantics to you? It's a file. How do I change it's contents when it's on
a server in the house or office of
23 matches
Mail list logo
