Revision history for HowYouCanHelp
Revision [3685]
Last edited on 2016-05-30 22:49:37 by AvoYager [Replaces old-style internal links with new pipe-split links.]Additions:
The first thing to do is to contact the administrator of the server for which you are configured to resolve DNS. This will generally be either the tech support group at your ISP or the IT/Support group at your office or company. By only resolving the [[LegacyDNS | Legacy TLDs]], they are restricting your ability to see a growing part of the general Internet.
If your ISP or IT support folks are not interested in supporting OpenNIC as a network-wide facility on their network you can still resolve OpenNIC names by [[ConfiguringYourComputer | configuring your personal computer]] to use a server that does.
Obviously, the first step is to [[Tier2ServerConfig | set your server]] to use OpenNIC. In addition, however, you could also open access to resolve on your server as a [[VolunteerHosts | Tier 2 public name server]] for the OpenNIC. This will help distribute the load on general name resolution.
To get involved in maintaining the OpenNIC itself, you could also volunteer to [[http://www.opennic.unrated.net/new_tlds.html | organize a new TLD]] within OpenNIC and arrange service for it.
We are developing a set of utilities and applications both for automating the OpenNIC itself and to help users and administrators switch their machines to OpenNIC. In the long run, the suggestion has been raised that we should begin work on new name resoltion protocols and software for the existing protocols. If you are interested in working on these projects, please [[MailingLists | join the discussion list]] and let us know.
If your ISP or IT support folks are not interested in supporting OpenNIC as a network-wide facility on their network you can still resolve OpenNIC names by [[ConfiguringYourComputer | configuring your personal computer]] to use a server that does.
Obviously, the first step is to [[Tier2ServerConfig | set your server]] to use OpenNIC. In addition, however, you could also open access to resolve on your server as a [[VolunteerHosts | Tier 2 public name server]] for the OpenNIC. This will help distribute the load on general name resolution.
To get involved in maintaining the OpenNIC itself, you could also volunteer to [[http://www.opennic.unrated.net/new_tlds.html | organize a new TLD]] within OpenNIC and arrange service for it.
We are developing a set of utilities and applications both for automating the OpenNIC itself and to help users and administrators switch their machines to OpenNIC. In the long run, the suggestion has been raised that we should begin work on new name resoltion protocols and software for the existing protocols. If you are interested in working on these projects, please [[MailingLists | join the discussion list]] and let us know.
Deletions:
If your ISP or IT support folks are not interested in supporting OpenNIC as a network-wide facility on their network you can still resolve OpenNIC names by [[ConfiguringYourComputer configuring your personal computer]] to use a server that does.
Obviously, the first step is to [[Tier2ServerConfig set your server]] to use OpenNIC. In addition, however, you could also open access to resolve on your server as a [[VolunteerHosts Tier 2 public name server]] for the OpenNIC. This will help distribute the load on general name resolution.
To get involved in maintaining the OpenNIC itself, you could also volunteer to [[http://www.opennic.unrated.net/new_tlds.html organize a new TLD]] within OpenNIC and arrange service for it.
We are developing a set of utilities and applications both for automating the OpenNIC itself and to help users and administrators switch their machines to OpenNIC. In the long run, the suggestion has been raised that we should begin work on new name resoltion protocols and software for the existing protocols. If you are interested in working on these projects, please [[MailingLists join the discussion list]] and let us know.
Revision [556]
Edited on 2007-07-21 11:12:56 by AvoYager [Replaces old-style internal links with new pipe-split links.]Additions:
The OpenNIC has some difficult challenges to deal with to establish itself. Most of the real technical issues have been dealt with, but new ones will always crop up; it seems to be in the nature of computers and networking. The most important issues, however, are social. The established DNS system and the corporations who control are very large and very rich and are, in general, not fond of the idea that the users should own the DNS system; they are simply making too much money from it.
Deletions:
Additions:
Obviously, the first step is to [[Tier2ServerConfig set your server]] to use OpenNIC. In addition, however, you could also open access to resolve on your server as a [[VolunteerHosts Tier 2 public name server]] for the OpenNIC. This will help distribute the load on general name resolution.
Deletions:
Additions:
If your ISP or IT support folks are not interested in supporting OpenNIC as a network-wide facility on their network you can still resolve OpenNIC names by [[ConfiguringYourComputer configuring your personal computer]] to use a server that does.
Deletions:
Additions:
If your ISP or IT support folks are not interested in supporting OpenNIC as a network-wide facility on their network you can still resolve OpenNIC names by [[http://www.opennic.unrated.net/personal.html configuring your personal computer]] to use a server that does.
Obviously, the first step is to [[http://www.opennic.unrated.net/server.html set your server]] to use OpenNIC. In addition, however, you could also open access to resolve on your server as a [[VolunteerHosts Tier 2 public name server]] for the OpenNIC. This will help distribute the load on general name resolution.
We are developing a set of utilities and applications both for automating the OpenNIC itself and to help users and administrators switch their machines to OpenNIC. In the long run, the suggestion has been raised that we should begin work on new name resoltion protocols and software for the existing protocols. If you are interested in working on these projects, please [[MailingLists join the discussion list]] and let us know.
Obviously, the first step is to [[http://www.opennic.unrated.net/server.html set your server]] to use OpenNIC. In addition, however, you could also open access to resolve on your server as a [[VolunteerHosts Tier 2 public name server]] for the OpenNIC. This will help distribute the load on general name resolution.
We are developing a set of utilities and applications both for automating the OpenNIC itself and to help users and administrators switch their machines to OpenNIC. In the long run, the suggestion has been raised that we should begin work on new name resoltion protocols and software for the existing protocols. If you are interested in working on these projects, please [[MailingLists join the discussion list]] and let us know.
Deletions:
Obviously, the first step is to [[http://www.opennic.unrated.net/server.html set your server]] to use OpenDNS. In addition, however, you could also open access to resolve on your server as a [[VolunteerHosts Tier 2 public name server]] for the OpenNIC. This will help distribute the load on general name resolution.
We are developing a set of utilities and applications both for automating the OpenNIC itself and to help users and administrators switch their machines to OpenDNS. In the long run, the suggestion has been raised that we should begin work on new name resoltion protocols and software for the existing protocols. If you are interested in working on these projects, please [[MailingLists join the discussion list]] and let us know.
Additions:
The first thing to do is to contact the administrator of the server for which you are configured to resolve DNS. This will generally be either the tech support group at your ISP or the IT/Support group at your office or company. By only resolving the [[LegacyDNS Legacy TLDs]], they are restricting your ability to see a growing part of the general Internet.
