Help

Getting Started Company Information 1. Who maintains the Dot Church registry? 2. Are there differences between how Dot Church domain names and .COM/.NET /.ORG domain names work? 3. Who is helping to shape Dot Church? Background Information 1. 2. 3. 4. 5. 6. 7. What is a domain name? What languages are the Dot Church domain extensions available in? Can I register domain name extensions such as: .COM, .NET, or .ORG through New.net? What does it mean to "register" a domain name? Why should I register a Dot Church domain name? Once I purchase a domain name, how long may I use it? How much does it cost to register a domain name?

Registration Process 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. How do I register a domain name with New.net? What do I need in order to register a domain name? How long does Dot Churchs registration process take? Is it possible for another person to register my domain name on the Dot Church Registry after I have registered it? What methods of payment does Dot Church accept? What are the valid characters for a domain name and how long can it be? Is there any guaranteed minimum number of people that will be able to access Dot Church domain names? Are there trademark restrictions on purchasing Dot Church domain names? Is my contact information for my Dot Church domain publicly available? Once I have registered a Dot Church domain, how do I get my site onto the Internet? Does Dot Church provide web space? Where do I enter my credit card billing information when I register a Dot Church domain? I no longer want my Dot Church domain name. Will Dot Church refund my money?

Company Information 1. Who maintains the Dot Church registry?

Dot Church, LLC maintains its registry through its business partners, New.net and Bulk Register in a similar way that Verisign maintains the registries for .COM, .NET, and .ORG. 2. Are there differences between how .church domain names and .COM/.NET/.ORG domain names work?

There are some differences, but in many ways the domain names work the same. One difference is that in order for people to use New.net domain names, they must either access the Internet through one of our many ISP partners or download and install our plug-in. If either one of these requirements is met, then New.net domains will work just as you are used to .com and .net domains working. 3. Who is helping to shape Dot Church?

Dot Church has many partners that are working with us to make .church domains widely recognized around the world. Some of our current partners include: New.net Bulk Register Salem Web Network

Background Information 1. What is a domain name?

Domain names are the familiar, easy to remember names for computers on the Internet (such as my.dotchurch). They correspond to a series of numbers called Internet Protocol numbers (IP numbers, such as 244.120.0.43) that serve as routing addresses on the Internet. Domain names are used generally as a convenient way of locating information and reaching others on the Internet, without having to remember a long string of numbers. A domain name extension is the suffix that is attached to the end of a domain name. For example, in the domain name "my.CHURCH"; ".CHURCH" is the domain name extension. You may be familiar with other domain name extensions such as .COM, .ORG, .NET, .EDU, and .GOV. Now there are new domain name extensions such as: .CHURCH, .LOVE, and .MP3. 2. What languages are the .church domain names available in?

At this time, the .church domain name extensions are available in the following languages: ENGLISH ESPANOL FRANCAIS PORTUGUES DEUTSCH ITALIANO

You may see the current list of multi-lingual domain name extensions by scrolling to the top of the main page and clicking on the appropriate language tab (i.e., English, Espanol, Francais, Portugues, Deutsch, Italiano). We plan to introduce multi-language extensions in the future based on market data and information gathered from our customers.

4. Can I register domain name extensions such as: .COM, .NET, or .ORG through New.net?

Yes, you can register domain names extensions such as: .com, .net, or .org through Dot Church. 5. What does it mean to "register" a domain name?

The Internet Domain Name System (DNS) consists of a directory, organized hierarchically, of all the domain names and their corresponding computers registered to particular companies and persons using the Internet. When you register a domain name, it will be associated with the computer on the Internet you designate (DNS information) during the period the registration is in effect. You can also use the domain name to point to another website address (URL Forwarding) such as point www.jones.family to www.geocities.com/~thomasjones/family/index.html. 6. Why should I register a Dot Church domain name?

Registering a domain name for your church or business is essential to your marketing efforts. A domain name gives your business a unique identity on the World Wide Web (WWW). Individuals also register domain names to use as an address for their personal web site. The market for .COM and .NET and all other widely used domains has become very crowded. There is a need for even more descriptive domain name extensions for faith based organizations. Dot Church answers both of these concerns. 7. Once I purchase a domain name, how long may I use it?

Your .church domain name will be yours for as long as you pay the yearly registration fees and comply with the terms specified during the registration process. 8. How much does it cost to register a .church domain name?

Registering a domain at New.net is $45 for the first year for each domain.

Registration Process 1. How do I register a domain name with Dot Church?

Registering a domain name at New.net is simple; just scroll up to the top of this page and enter a domain name of your choice and follow the steps thereafter. 2. What do I need in order to register a domain name?

To register a domain name with Dot Church, you only need to specify the Contact Information and credit card billing information associated with your domain name. DNS information is not required during sign-up; this can be edited at any time after the registration is complete. 3. How long does Dot Churchs registration process take?

Dot Churchs registration process should only take a few minutes to complete. Once your registration has been confirmed it will take no more than a few hours for Dot Churchs database to be updated with your new domain. 4. Is it possible for another person to register my domain name on the Dot Church Registry after I have registered it?

No. Dot Churchs system prevents duplicate registrations on the New.net Registry. Domains are registered on a first-come, first-served basis. Once a domain is registered, any other person or domain registration site cannot register it with New.net. You should be aware; however, that other companies may offer alternate registries and that New.net has no control over their registration procedures. 5. What methods of payment does New.net accept?

A valid MasterCard, Visa, American Express, or Discover Card is currently the only means of payment accepted. Online checks will be accepted in the near future. 6. What are the valid characters for a domain name and how long can it be?

The only valid characters for a domain name are letters (a-z), numbers (0-9), and a hyphen "-". A hyphen may not begin or end a domain name. Spaces and special characters like the underscore "_" or an exclamation mark "!" are NOT permitted. Example: your name.church (not valid, no spaces allowed) Example: your_name.church (not valid, no underscores allowed) Example: your&name.church (not valid, no special characters allowed) Example: your-name.church (valid) Example: yourname.church (valid) A Dot Church domain name can be up to 55 characters long - excluding the characters used to identify the domain name extension (.CHURCH, .MP3, etc.). 7. Is there any guaranteed minimum number of people that will be able to access Dot Church domain names? No. There is no guarantee that the entire Internet will recognize Dot Church domain names. However, Dot Church, LLC intends to seek to maximize the recognition of .church domain names. 9. Are there trademark restrictions on purchasing New.net domain names?

Every Dot Church domain name is available for purchase on a first-come, first-served basis. However, each purchaser of a Dot Church domain name must represent in the registration agreement that he or she does not intend to use the domain name in a manner that infringes on anyone else's intellectual property rights. Each purchaser is reminded of this obligation during the registration purchase process. All domain name registrations are subject to Dot Churchs Model Domain Name Dispute Resolution Policy. 10. Is my contact information for my Dot Church domain publicly available?

Yes. The Administrative Contact information as well as the first and last name of the Registrant is publicly available to anyone. This is to permit enforcement of consumer protection, trademark and other laws, and rapid resolution of technical issues. The Administrative Contact information may be changed at any time under Manage My Account from the Dot Church site. 11. Once I have registered a New.net domain, how do I get my site onto the Internet? Does Dot Church provide web space?

When you register a Dot Church domain, you do not receive any web space on our servers. Once you have registered your domain name, you may purchase our web hosting services. 12. Where do I enter my credit card billing information when I register a Dot Church domain?

All of your credit card billing information is entered in the final step of the registration process. 13. I no longer want my New.net domain name. Will New.net refund my money?

Dot Church upholds a no refund policy on all domain name registrations. For more information on this policy, please visit the New.net Registration Agreement, Section 3. Plug-In 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. What are the minimum system requirements for the plug-in? Is the plug-in required to resolve Dot Church domains? What browsers currently support the plug-in installation? How can I fully uninstall the Dot Church plug-in? Will there be newer versions of the plug-in that I would need to download and install? What information is sent to the Dot Church servers during an auto-update? Isn't this considered "spyware"? The plug-in will not install when using Windows 95a, Windows 95b or Windows NT. Why? Is there a standalone version of the plug-in that I can send via e-mail or save on disk? How can I configure my MAC to resolve New.net domains? How can I configure my Linux/Unix machine to work with New.net domains? How can I configure my Win98 (Windows 98) or WinME (Windows ME) machine to work with New.net domains? How can I configure my Win2K (Windows 2000), or WinXP (Windows XP) machine to work with Dot Church domains? What is Quick!? Frequently Asked Questions (FAQs)

14. How can I get Quick!? 15. Can I Turn Quick! Off? E-mail 1. Can I use my Dot Church domain names for e-mail? 2. How do I configure a mail server to support Dot Church domain names? 3. Sending, receiving and replying to e-mail addresses containing Dot Church domain names? 4. What e-mail clients does the Dot Church plug-in support? 5. What web mail programs does the Dot Church plug-in support? 6. Does the Dot Church plug-in support IMAP4 or MAPI? 7. What is an MX Record and how can I use it? URL Forwarding 1. How can I forward my new domain to an existing website?

Web Hosting 1. I represent a web host company, how can I configure my name servers to support Dot Church domains? 2. Which web hosts currently support Dot Church domains? Search Engines 1. How can I submit my Dot Church domains into the popular search engines? Technical 1. How can I get my ISP to provide access to Dot Church domain name extensions? 2. I represent an ISP, how can I provide access to Dot Church domain name extensions? 3. How do I configure my name servers for my Dot Church domains?

Plug-In 1. What are the minimum system requirements for the plug-in?

The plug-in requires Windows 98, Windows ME, Windows 2000, Windows XP Home, or Windows XP Pro. Installation requires Internet Explorer 5.0 or higher and/or Netscape Navigator/Communicator v4.7 or higher. Note: Windows 2000 and Windows XP users require administrator access in order to install our plug-in.

2. Is the plug-in required to resolve Dot Church domains?

No. The plug-in is only necessary for customers that do not currently access the Internet with one of our ISP partners. Customers using one of our ISP partners are able to resolve all Dot Church domains without the need for our plug-in. 3. What browsers currently support the plug-in installation?

The plug-in installation only supports Netscape Navigator/Communicator and Internet Explorer v4.5 or higher. There is a separate installation for Netscape and Internet Explorer. Below are the URLs for each browser installation: Note: AOL uses Internet Explorer for their browser. Internet Explorer and AOL: http://www.new.net/download/instructions_win_ie.tp Netscape Navigator/Communicator: http://www.new.net/download/instructions_win_netscape.tp 4. How can I fully uninstall the Dot Church/New.net plug-in?

To uninstall the application, please follow the steps below: 1. 2. 3. 4. 5. 6. 7. Click on Start. Select Settings. Click on Control Panel. Double-click on the Add/Remove Programs icon. Select the New.net Application. Click on the Add/Remove button. Once the program has uninstalled, click on the OK button.

After completing all of these steps, please reboot the computer. This will have removed the Dot Church application from your system. The above steps will fully remove the New.net plug-in. However, the Windows operating system will retain a record that the New.net plug-in previously had been installed on your computer in "C:\Windows\Downloaded Program Files." This file is harmless, but can be removed by following the steps below: 1. 2. 3. 4. 5. 6. 7. 8. 9. Click on Tools. Click on Internet Options. Under the General tab, click on the Settings button. Within the Settings window, click on the View Objects button. Within the Downloaded Program Files window, locate and delete Tldctl2c Class. Close the Downloaded Program Files window. Click on the OK button within the Settings window. Click on the OK button within the Internet Options window. Close Internet Explorer.

5. Will there be newer versions of the plug-in that I would need to download and install?

There is never a need to download and install our plug-in again once installed initially. Our plug-in has a built in auto-update feature that automatically checks our servers periodically for a new version. If a new version is found, it is automatically downloaded and installed with no need for interaction by the customer. 6. What information is sent to the New.net servers during an auto-update? Isn't this considered "spyware"?

Dot Church respects the privacy of all its customers and would never transmit any personal information from any computer. The ONLY information sent from our plug-in to our servers is the version number. 7. The plug-in will not install when using Windows 95a, Windows 95b or Windows NT. Why?

The plug-in is no longer supported on Windows 95 and Windows NT machines. You can still access New.net domains if you are using one of our ISP partners for Internet access. Click here to see the list of our ISP partners. 8. Is there a standalone version of the plug-in that I can send via e-mail or save on disk?

Currently, there is no standalone version of the plug-in. However, if you would like to send the link to in stall the plug-in via e-mail; the URLs are provided below. Internet Explorer: http://www.new.net/download/instructions_win_ie.tp Netscape Navigator/Communicator: http://www.new.net/download/instructions_win_netscape.tp 9. How can I configure my MAC to resolve Dot Church domains?

For Macs running MacOS 7.5.2 through 9.1: 1. Open the TCP/IP Control Panel and locate the box labeled "Additional Search Domains" 2. In this box, type: "new.net" (without quotes) on its own line. 3. Close the TCP/IP Control Panel For Macs running MacOS X: 1. 2. 3. 4. Open the Network pane of the System Preferences. If locked, click on the lock icon and provide your user name and password. Locate the Search Domains box under the TCP/IP tab. In this box, type: "new.net (without quotes) on its own line.

Your Mac should now resolve and enable your web browser to see the new domains. 10. How can I configure my Linux/Unix machine to work with New.net domains?

Edit the following file: /etc/resolv.conf. In this file, look for the line that starts with "search" and add "new.net" to the end of the line. Thus if the resolv.conf file currently reads like this:

search company.com nameserver 1.2.3.4

You should change it, so that it now reads:

search company.com new.net nameserver 1.2.3.4

If there is no "search" line in the file, but there is a "domain" line, then replace "domain" with "search" and then add the new.net as above. Your Linux/Unix machine should now resolve and enable your web browser to see the new domains. Back to top 11. How can I configure my Win98 (Windows 98) or WinME (Windows ME) machine to work with Dot Church domains?

Currently, there are two ways that your machine can work with New.net domains: 1. If you are already using one of our ISP partners for Internet access, then you will need to do nothing but enter the domain name within the browser on your machine. Click here to see the list of our ISP partners. OR 2. If you are not using one of our ISP partners for Internet access, then you will need to download and install our plug-in. Once installed, your machine will be able to browse New.net domains. There are two different links for the plug-in : Netscape and Internet Explorer. 12. How can I configure my Win2K (Windows 2000), or WinXP (Windows XP) machine to work with New.net domains? Currently, there are two ways that your machine can work with New.net domains. 1. If you are already using one of our ISP partners for Internet access, then you will need to do nothing but enter the domain name within the browser on your machine. Click here to see the list of our ISP partners. OR 2. If you are not using one of our ISP partners for Internet access, then you will need to download and install our plug-in. Once installed, your machine will be able to browse

New.net domains. There are two different links for the plug-in: Netscape and Internet Explorer. Note: Windows 2000, Windows XP users require administrator access in order to install our plugin. Click here to download System Administration Instructions. E-mail 1. Can I use my Dot Church domain names for e-mail?

Yes, New.net domain names can be used in e-mail addresses as follows: First, as with any domain name that you want to use for e-mail, you need to either (1) sign up for e-mail service with a third-party provider, or (2) operate your own mail server for e-mail. Many companies that offer hosting services also provide e-mail services, and other companies provide web-based e-mail services. The third-party provider that you choose will need to configure their mail servers to support Dot Church domain names. If you operate your own mail server, you will need to do the same. See "How do I configure a mail server to support Dot Church domain names?" below. In the coming weeks, we will provide a list of leading third-party e-mail service providers that support New.net domain names. Second, you need to configure your e-mail client (i.e., Outlook, Eudora or other e-mail application) to include your Dot Church domain name in your email address for sending and receiving e-mails, just like you would do to set up e-mail for any other domain name. If you do not use an ISP that supports Dot Church domain names AND you do not use the Dot Church plug-in, we recommend that you set up your e-mail client to use the longer form of your Dot Church domain name (i.e., "your.church.new.net" instead of "your.church") in your e-mail address. Third, when you send e-mails to persons who have not installed New.net's plug-in AND do not use one of New.net's ISP partners, such persons will need to add ".new.net" to your email address in order to reply to your e-mail. If you are using the New.net plug-in, the plugin will automatically append ".new.net" to your e-mail address when you send e-mail, and persons receiving the e-mail will be able to reply without making any change. If you do not use the New.net plug-in, we recommend that you configure your e-mail client to automatically include the following as a "signature" or "tag line" on the bottom of every email that you send: "To reply to this e-mail, get the New.net plug-in at www.new.net or add ".new.net" to the end of my-email address." 2. How do I configure a mail server to support Dot Church domain names?

When a Dot Church domain name is purchased, we assign both www.your.church and www.your.church.new.net. This ensures that the website can be accessed both by users who access the Internet via one of our ISP partners and users that use our plug-in to recognize New.net domains. This also holds true for e-mail. In our example, users with access to New.net domains via the plug-in will send the e-mail address of yourname@your.church.new.net and users with access via ISP partners will send the e-mail address of yourname@your.church. Because there are two different requests that can be

sent to the name server, it is very important to recognize both forms of the domain name and keep them synchronized. To do this, you would need to create two separate zone files, one for your.church and the other for your.church.new.net, and they both need to point to the same MX Record. Your Dot Church domain host or your IT professional would normally configure the above procedures. 3. Sending, receiving and replying to e-mail addresses containing New.net domain names?

The ability of users to send, receive and reply to e-mails that contain Dot Church domain names varies depending on whether users use one of Dot Churchs partner ISPs to access the Internet and/or use the New.net plug-in: Persons who access the Internet via one of Dot Churchs and New.net's partner ISPs can send, receive and reply to e-mails containing Dot Church and New.net domain names in the same manner as e-mails containing any other domain names. The mail servers at Dot Churchs and New.net's partner ISPs have been configured to recognize New.net domain names. (We have identified a problem with Net Zeros mail server configuration that is causing send failures and a problem with Juno's e-mail client that is causing retrieval failures; we are working with these ISPs to solve these problems as soon as possible.) Persons who use Dot Church/New.net plug-in also can send, receive and reply to e-mails containing New.net domain names. The plug-in enables e-mail with New.net domain names by (1) adding ".new.net" to an e-mail address containing a New.net domain name when an e-mail is sent by someone using the plug-in, and (2) deleting ".new.net" to an email address containing a New.net domain name when an e-mail is received by someone using the plug-in. The process of adding or deleting ".new.net" occurs in the background without being visible to the sending or receiving user. Thus, if you use the New.net plugin when sending e-mails, recipients of your e-mails will receive them either in the long form (yourname@domain.extension.new.net) or the short form (yourname@domain.extension) depending on whether the recipient uses the New.net plug-in. The recipient will be able to reply to your e-mail in either case. Persons that neither use one of New.net's partner ISPs nor the New.net plug-in can send and reply to e-mails containing New.net domain names by manually adding ".new.net" to the end of the e-mail address. Such persons also can receive emails containing New.net domain names (without adding ".new.net") in most cases unless the provider of their email service has configured its mail servers to reject e-mails received from addresses containing domain names that its mail servers cannot resolve.

4. What e-mail clients does the Dot Church/New.net plug-in support? Currently, the Dot Church/New.net plug-in has been tested with and supports POP3 and SMTP protocols with the following e-mail clients: Outlook Outlook Express Eudora Vista NetMail Netscape Messenger 4.7

Netscape Messenger 6.0 EasyMailer Pine AOL Pegasus Mulberry The Bat The Dot Church/New.net plug-in enables e-mail with New.net domain names by (1) adding ".new.net" to an e-mail address containing a New.net domain name when an e-mail is sent by someone using the plug-in, and (2) deleting ".new.net" to an e-mail address containing a New.net domain name when an e-mail is received by someone using the plug-in. Persons that use the plug-in with the AOL e-mail program will see the longer form of the e-mail address (yourname@domain.extension.new.net), but this will not affect operability. 5. What web mail programs does the Dot Church/New.net plug-in support?

Currently, the New.net plug-in has been tested with and support the following web-based e-mail programs: Yahoo Hotmail Visto Netscape Excite With these web-based e-mail programs, using the Dot Church/New.net plug-in will add ".new.net" to any e-mail sent or replied to by a user of such programs, but the appended ".new.net" will be visible to the user. 6. Does the New.net plug-in support IMAP4 or MAPI?

Currently, the New.net plug-in does not support e-mail clients that use IMAP4 or MAPI protocols. We plan to add support for these protocols in future versions of the plug-in. 7. What is an MX Record and how can I use it?

An MX (Mail eXchanger) record controls which mail server deals with the email sent to your domain. With access to the MX record for your domain you can ensure email is routed to a mail server you are running or the mail server of another company providing this service to you. From Manage My Account, click on the Edit DNS Info button below the domain you want to configure for a mail server. MX Records are only supported when using either URL Forwarding or Use New.net Name Servers. For each section you will have a primary and secondary MX Record; the secondary server will be used if the primary server does not respond. In the MX Record 1 and MX Record 2 fields you may enter the IP Address or hostname for the mail server (ex., "192.168.1.55" or "mail.your.church"). Click on the Submit button at the bottom of the screen. It will take anywhere from 2 hours to 2 days for your new settings to take effect. There is no additional charge for this service.

URL Forwarding 1. How can I forward my new domain to an existing website?

From Manage My Account, click on the Edit DNS Info button below the domain you want forwarded. Select the second option, Use URL Forwarding and then enter the URL of the existing website into the Existing URL field. Click on the Submit button at the bottom of the screen. It will take anywhere from 2 hours to 2 days for your new settings to take effect. There is no additional charge for this service.

Web Hosting 1. I represent a web host company, how can I configure my name servers to support New.net domains?

When a Dot Church domain name is purchased, we assign both www.your.church and www.your.church.new.net. This ensures that the website can be accessed both by users who access the Internet via one of our ISP partners and users that use our plug-in to recognize Dot Church and New.net domains. In our example, users with access to Dot Church New.net domains via the plug-in will send the URL of www.your.church.new.net and users with access via ISP partners will send the URL of www.your.church. Because there are two different requests that can be sent to the name server, it is very important to recognize both forms of the domain name and keep them synchronized. To do this, you would need to create two separate zone files, one for www.your.church and the other for www.your.church.new.net, and they both need to point to the same A Record or IP Address. New.net plans to reconfigure its infrastructure shortly to eliminate the need to recognize www.your.church.new.net. 2. Which web hosts currently support New.net domains?

A list of some of the web hosts that support New.net domains can be seen here.

Search Engines 1. How can I submit my New.net domains into the popular search engines?

Currently, in order to submit your New.net domain URL into search engines you will need to use the "long" URL. For example, if you own www.your.church, you would need to submit it as

www.your.church.new.net. We are actively pursuing search engine partnerships so that domains can be submitted with the "short" URL.

Technical 1. How can I get my ISP to provide access to New.net domain name extensions?

Contact your ISP and ask them to "turn on" access. The steps for an ISP to provide access are simple and take only a few minutes to implement. 2. I represent an ISP, how can I provide access to Dot Church/New.net domain name extensions?

Click here for configuration instructions. 3. How do I configure my nameservers for my Dot Church/New.net domains?

When you purchase Dot Church domain names, we assign to you both www.your.church and www.your.church.new.net. This ensures that your Web site can be accessed both by users who access the Internet via one of our participating ISPs and users that use our software plug-in to modify their Internet browsers to recognize our domain names. If you choose to use Dot Churchs/New.net's DNS setting or URL Forwarding options, New.net will maintain both of these domains for you. If you choose to delegate the authority to your own nameservers, you will have to set up your Web site to recognize both forms of your domain name and keep them synchronized. New.net plans to reconfigure its infrastructure shortly to eliminate the need for you to continue recognizing www.your.church.new.net as we will be setting this automatically for you based on what you've configured in your www.your.church domain. Support For questions regarding domain registration or pricing. Customer Service Email: support@dotchurch.info For technical questions regarding our website or plug-in. Technical Support Email: support@dotchurch.info

ISP Information

UNIX ISP Network Administrators:

ISP's who would like to provide their users with immediate access to New.net's domain names may do so by making one simple change to your systems. On each recursive nameserver that is serving clients, you may implement any one of the options described below, assuming that you are using BIND on a Unix box (if you are not, then please email us for further information at: isp@New.net). Each of the following methods is roughly equivalent, with each having a minor advantage or disadvantage over the others. It is entirely up to you which you 'd like to pursue. After you've activated your network for New.net domains, we'll give your service free promotional placement on our site. All you have to do is email your logo to us and once we've verified that you've made the necessary changes, we'll post your logo. First, please note that "BIND config directory" refers to the directory listed in an options statement such as "/var/named" here:

options { directory "/var/named/"; } Here are four options you can choose from:

1. Our preferred solution is that you use a list of stub zones to supplement the ICANN roots with New.net domain extensions. For this option, do the following: Download ftp://ftp.New.net/domain/bind/root-stubs.conf into your BIND config directory. Append the following line to your /etc/named.conf: include "root-stubs.conf";

Reload the BIND configuration with the command "ndc reload". The list of stubs is expected to change up to once per month. You may wish to set up a process to mirror root-stubs.conf weekly from New.net and reload your nameserver if you use this method.

2. Replacing the root.cache file with one that lists our new root servers. In /etc/named.conf, find the filename for ".".

zone "." { type hint; file "named.root"; };

This file will be in the BIND config directory. In this case, it would be "/var/named/named.root". Download ftp://ftp.New.net/domain/bind/named.cache and overwrite the contents of that file with it. Your server will grab a new list of root servers from those listed in the hints file every time it starts up, and will use those for all queries.

3. Alternatively, you may slave the root zone, ".", from a master DNS server. Download ftp://ftp.New.net/domain/bind/root-slave.conf into your BIND config directory. In /etc/named.conf, find the section listing hints for ".", the root zone. They will look something like:

zone "." { type hint; file "named.root"; };

Delete that section, and insert in its place:

include "root-slave.conf";

Reload the BIND configuration with the command "ndc reload". This will slave a copy of the root zone from a New.net master nameserver. Your server will remain in sync with ours automatically.

4. Fourth, if you have a mechanism already in place to publish authoritative zones to all of your servers, you can use it to also publish ".".

You will need to daily or weekly grab a copy of ftp://ftp.New.net/domain/root.zone and publish it to your nameservers with the zone name of ".". The root zone is nothing special as far as BIND is concerned. If your nameservers know the information contained within it, they will not need to query our servers for that. Please note, if your company does not have a mechanism for change control publication, then you should not be considering this option. But if you do have such a mechanism, then the method is to simply publish to root zone information gathered from our ftp location , and publish as you would for any other zone that you are authoritative for. We highly recommend that you check our ftp for updates regularly, and in any event at least twice each week.

Here are two options you can choose from: Option 1:

1. Stop the DNS Server 2. Open the cache.dns file located in c:\winnt\system32\dns 3. Delete the information within (Option Make a copy of this file and save it) 4. Cut and paste the information located at ftp://ftp.new.net/domain/bind/named .cache 5. Save as "cache.dns" 6. Start the DNS Server 7. Verify functions by performing nslookup functions

Option 2: Instructions for adding a secondary "." zone for Domain name extensions from New.net DNS servers. In NT 4.0: NOTE: The procedure shown is intended for NT 4.0. The process can be used for Windows 2000

as well.

1. Open the DNS admin tool. 2. Highlight the server that is intended to hold the secondary zone. 3. Using your mouse, right click the server and select "New Zone" option, or from the drop down "DNS" menu select "New Zone" option . 4. Click the radio button for "Secondary" zone. (Figure 1.1)

Figure 1.1 5. The zone name should be "." (without quotes). 6. Choose a New.net server to act as the secondary zone. You can use FQDN or ip. The example shows the IP for ns0.newdotnet.net. 7. Click "Next". (Figure 1.2)

Figure 1.2 Zone Information screen 8. Leave the zone name as "." 9. The zone can have any name. However, be sure to leave the ".dns" suffix. 10. Click "Next". (Figure 1.3)

Figure 1.3 Zone transfer information 11. Enter the IP address of the server from which you plan to transfer. This should be the IP address for the server chosen in step 6 above. The example shows the IP for ns0.newdotnet.net. 12. Click "Add". 13. Click "Next" and then "Finish".

Zone transfer should occur within a few minutes. You can start and stop the dns service if you want to facilitate the transfer, but it is not necessary. Check functionality and event logs for any errors. Also, be sure to have the latest service pack applied. Network Administrators

How do I resolve the Dot Church/New.net domain name extensions in a business network environment?

If your business accesses the Internet via one of our service provider partners, then your staff will be already activated to access the new domains. If not, however, then there are several options open to you to get your company activated. Enable DNS resolution of our domains without the plug-in

Alternatively, you can enable users to access our domains by adding ".new.net" to the search path in your company's DNS system that you wish to grant such access to; either centrally via the Registry, or locally on each machine via the Append Search Paths option. Editing the Registry

Under Win2000 and WinNT, the "append these DNS suffixes" data are stored as commadelimited data in the REG_SZ value "SearchList" in the following registry key: KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters You will of course use Regedit to do this task, and you will need to have system administrator status to edit the Registry. Edit the value of "SearchList" to add "new.net" making it the last entry in that key (or the only one if you have no others listed already). You should propagate this change to the machines on your network in the usual manner in which you employ for such updates. Adding "new.net" to the Domain Suffix Search Order in TCP/IP Properties

In the Control Panel on each machine that you wish to activate for the new domains, Open "Network." Select "Protocols" and then select the item listed there, "TCP/IP Protocol." Now select "Properties." In the properties box select the menu item "DNS." At the bottom of this dialog box is a section headed "Domain Suffix Search Order." Click "Add" and then enter "new.net" and press "Add" again. Now you have successfully added the new.net domain to your DNS search path and all the new domains will now be resolved. Exit the Network control panels. Note: if you have added new.net to the DNS search path via a Registry change, then this will also appear here too.