Welcome to the Gossimer Support Knowledge Base. Here we have listed detailed information regarding all our current Product and Service offerings and answers to your every possible query. The Gossimer Support KB has been divided into Categories indicating a particular Interface or a particular Product/Service. These have been further logically divided into Sub-Categories and Answers, detailing a particular action or query.
In the event, you are unable to locate a particular resource, please make use of the Search box provided on the top of the page or inform our Support Team at http://support.gossimer.com.
Tags: Amp, Chat Services, Customer Control Panel, Demo, Digital Certificates, DNS, Domain Name Registration, Domain Url, Interface, Live Chat, Search Box, Service Offerings, Support Knowledge Base, Web Hosting
Changes in version 3.10
Java Docs updated
Changes related to classes and methods:
New Classes and Methods
| Domains Kit | |
| New Class Name | New Method |
| ThirdLevelDotUk | String invoiceOption |
| ThirdLevelDotUk | String existingEndTime |
New Parameters introduced in Existing Methods
| Other Products Kit | ||
| Class Name | Method Name | New Parameters |
| EngageOrder | renew | String invoiceOption |
| EngageOrder | renew | String existingEndTime |
Deprecated Parameters in Methods
| Domains Kit | ||
| Class Name | Method Name | Deprecated Parameters |
| ZoneOrder | add | “No Of Records” in DomainHash |
Deprecated Methods
| Domains Kit | |||
| Class Name | Deprecated Method | Suggested Class | Suggested Method |
| DomContact | addDefaultContact | DomContact | addDefaultContacts |
| DomContact | add | DomContact | addContact |
| DomContact | list | DomContact | listByType |
| DomContactExt | isValidRegistrantContact | DomContactExt | isValidContact |
| DomOrder | transferDomain | DomOrder | addTransferDomain |
| DomOrder | add | DomOrder | registerDomain |
| ZoneOrder | mod | ZoneOrder | Functionality not required anymore |
| DotEu | tradeDomain | DotEu | trade |
| DotEu | transferDomain | DotEu | transfer |
| DotEu | add | DomOrder | registerDomain |
| Core Kit | |||
| Class Name | Deprecated Method | Suggested Class | Suggested Method |
| Customer | addCustomer | Customer | signUp |
| Customer | modDetails | Customer | mod |
| Reseller | addReseller | Reseller | signUp |
| Reseller | modDetails | Reseller | mod |
| Reseller | addResellerWithStateId | Reseller | Functionality not required anymore |
| OrderSetup | getResellerSlabPercentageForProducts | OrderSetup | Functionality not required anymore |
| OrderSetup | getCustomerSlabPercentage | OrderSetup | Functionality not required anymore |
Changes in version 3.9
Changes related to classes and methods:
The following method in the Domains Kit is deprecated and its use should be discontinued -
Deprecated method Class New method to be used isValidRegistrantContact DomContactExt isValidContact
Changes in version 3.8
Java Docs updated
Changes related to classes and methods:
The following changes have been introduced under the DotEu class within the Domains Kit -
The following new methods have been introduced under DigitalCertificateOrder class within the Other Products Kit -
Changes in version 3.7
Java Docs updated
Changes related to classes and methods:
Some old parameters have been removed and new parameters introduced in their place under the following methods -
| LinuxHostingOrder Class | ||
| Method | Old Parameter | New Parameters |
| add | Hashtable orderParams | String packageKey*, boolean ssl# |
| mod | Hashtable orderParams | String packagekey*, boolean ssl#, int excessBandwidth## |
| getMonthlyCostAndValidate | Hashtable orderParams | String packageKey*, boolean ssl#, int execessBandwidth## |
| getModPricing | Hashtable orderParams | String packageKey*, boolean ssl#, int execessBandwidth## |
| WindowsHostingOrder Class | ||
| Method | Old Parameter | New Parameters |
| add | Hashtable orderParams | String packageKey*, boolean ssl# |
| mod | Hashtable orderParams | String packagekey*, boolean ssl#, int excessBandwidth## |
| getMonthlyCostAndValidate | Hashtable orderParams | String packageKey*, boolean ssl#, int execessBandwidth## |
| getModPricing | Hashtable orderParams | String packageKey*, boolean ssl#, int execessBandwidth## |
| MailHostingOrder Class | ||
| Method | Old Parameter | New Parameters |
| add | Hashtable orderParams | String packageKey* |
| mod | Hashtable orderHash | String packagekey*, int additionalMailBoxes** |
| getMonthlyCostAndValidate | Hashtable orderParams | String packageKey*, int additionalMailBoxes** |
| getModPricing | Hashtable orderParams | String packageKey*, int additionalMailBoxes** |
| SiteBuilder Class | ||
| Method | Old Parameter | New Parameters |
| mod | Hashtable orderParams | String packageKey* |
| getMonthlyCostAndValidate | Hashtable orderParams | String packageKey* |
NOTE:* packageKey will be the Identifier Key of the Plan (plan1, plan2, plan3, plan4) for which the Order needs to be added/modified.
# ssl will be true or false depending whether the user wants Dedicated IP / SSL for the Order placed.
## excessBandwidth is the Bandwidth which the user wants over and above the Bandwidth of the Order’s current plan.
** additionalMailBoxes is the number of additional mail boxes over and above the existing ones in blocks of 100 accounts.
Changes in version 3.6
Java Docs updated
Changes related to classes and methods:
| Deprecated method | Class | New method to be used |
| add | DomContact | addContact |
| addDefaultContact | DomContact | addDefaultContacts |
| list | DomContact | listByType |
| add | DomOrder | registerDomain |
| transferDomain | DomOrder | addTransferDomain |
| transferDomainWithoutValidation | DomOrder | addTransferDomain |
| addTransferDomainWithoutvalidation | DomOrder | addTransferDomain |
| add | DotEu | registerDomain in DomOrder class |
While these methods are currently available, they are no longer supported and may be discontinued in the near future.
Changes in version 3.5
Java Docs updated
Changes related to classes and functions:
Changes in version 3.4
Java Docs Updated
New Classes introduced in all Kits:
Core Kit
TaxService
getApplicableTaxes
getHashedTaxRules
Domains Kit
DotEu
getEUCountryList
tradeDomain
transferDomain
add
isEUCountry
DotEuContact
mod
add
addEuDefaultContact
DomOrder
validateDomainRegistrationParams
validateDomainTransferParams
addTransferDomainWithoutvalidation
addWithoutValidation
Hosting Kit
WindowsHostingPlanOnlyOrder
getDetails
getDetailsByDomain
getOrderIdByDomain
add
mod
renew
del
getMonthlyCostAndValidate
getModPricing
getDeletionRefundAmount
LinuxHostingPlanOnlyOrder
getDetails
getDetailsByDomain
getOrderIdByDomain
add
mod
renew
del
getMonthlyCostAndValidate
getModPricing
getDeletionRefundAmount
MailHostingPlanOnlyOrder
getDetails
getDetailsByDomain
getOrderIdByDomain
add
mod
renew
del
getMonthlyCostAndValidate
getModPricing
getDeletionRefundAmount
list
MailHostingSetup
getHostingKeyDisplayName
getHostingParamsDisplayName
getPricingKeyPricingParamMap
WindowsHostingSetup
getHostingKeyDisplayName
getHostingParamsDisplayName
getPricingKeyPricingParamMap
LinuxHostingSetup
getHostingKeyDisplayName
getHostingParamsDisplayName
getPricingKeyPricingParamMap
Other Products Kit
DigitalCertificateOrder
add
getCertPrice
SiteBuilderSetup
getPricingKeyPricingParamMap
EngageSetup
getPricingKeyPricingParamMap
Changes in version 3.3
3 new functions have been added in the Core Kit under the following classes:
authenticateCustomerId – Customer class
login – Customer class
getOrderIdByDomainAndProductCategory – Order class
The name of the jar file in every kit is now unique.
Bug Fix – A minor Java Script problem was causing the frame links in the examples to not work in some browsers like Mozilla and Opera.
Changes in version 3.2
New methods added viz. Order.removeCustomerLock, Order.getLockList
The testing form provided now has a third frame which accepts the standard parameters passed in every call. If you set these parameters from the form, you can make test calls independent of the settings in the properties/constants file.
Changes in version 3.1
Minor bugs in WSDL files fixed.
Version 3.0 Released
Extensive changes made. Please download the kit and read the appropriate Javadocs for details
Changes in version 2.6
Added the method Customer.delete() which allows you to delete a Customer
Added the method DomOrder.cancelTransferRequest() which allows you to cancel the transfer-in request for a domain name
Added the method Order.sendRfa() which allows you to re/send the email asking for transfer-in approval for domain names.
Changes in version 2.5
Bug fix in Modify Customer Details and Modify Contact Details forms
More details in the Javadocs for DomOrder.getDetails()
Link to new Demo Server added.
Changes in version 2.3
Move Website functionality added in API
Add Funds functionality for both Sub-Resellers and Customers also added
Domain Forwarding, Mail Forwarding, Managed DNS Products now available through the API.
Changes in version 2.2
In customer class new method (authenticateCustomer) is added to authenticate the Customer.
Changes in version 2.1
DomUsContact.class
API for DomUsContact.class is provided
The characteristics of DomUsContact.class includes the method setContactDetails() that needs to be called for any contact used as Registrant contact for .US. for providing applicationPurpose and nexusCategory facility.
list() method
list() method of DomContact.class is now available to Customer as well as Reseller.
The function signature of listContact() is also changed – One has to pass Customer Id after Parent Id besides other parameters.
getCustomerAvailableBalance() fuction
getCustomerAvailableBalance() fuction is added to the Fund.class
This function returns the available balance of a Customer.
getCustomerId() function
getCustomerId() function is added to the Customer.class
This function returns the customer id of the customer.
The prefix of all user classes changed to Customer eg. UserService to CustomerService, UserServiceTest to CustomerServiceTest
Method signature change in DomContact.class
OLD – int add(java.lang.String userName, java.lang.String password, java.lang.String role, java.lang.String langpref, int parentid, int customerId)
NEW – int addDefaultContact(java.lang.String userName, java.lang.String password, java.lang.String role, java.lang.String langpref, int parentid, int customerId)
Tags: Api, Core Kit, Customer Signup, Deprecated Methods, DNS, Java, Java Docs, Kit Class, New Domains, nexusCategory facility, Parameters, Registerdomain, Reseller, SSL
Follow the instructions below to begin integration with the API using PHP -
Make sure you have read the General API Integration Instructions first. If you have already integrated the PHP API Kit at your end, read the Change Log first to know what has changed since.
Reference:
General API Integration Instructions >>
Change Log >>
The PHP API Kit is not compatible with version PHP5. You need to use version PHP4 in order to integrate the API Kit at your end.
Step 1. Download the API Kit
Click the link below to download the relevant API kits (updated on 6th March, 2008).
PHP_CoreKIT_v3_10.zip
PHP_DomainsKIT_v3_10.zip
PHP_HostingKIT_v3_10.zip
PHP_OtherProductsKIT_v3_10.zip
Step 2. Download the API Documentation
The complete documentation of all classes and methods available in the API can be found in the Docs below. The Docs below are javadocs, but the function names and explanations remain the same for all the platforms and the documentation is self explanatory. We recommend you download the docs and read through them completely once before you integrate your application (updated on 6th March, 2008).
Core_Docs_v3_10.zip
Domains_Docs_v3_10.zip (updated on 1st April, 2008)
Hosting_Docs_v3_10.zip
OtherProducts_Docs_v3_10.zip
Since “list” is a keyword in the PHP language, the “list()” methods in the various classes (in the PHP Kit) has been renamed to “listOrder().” However, the documentation still mentions the method name as “list” since the documentation is JAVA specific.
Instructions to pass parameters to functions using the PHP Kit
Since PHP uses typeless variables you will have to ignore the datatypes presented in the docs. But for assigning values to variable of types other than strings and integers special care will have to be taken. Below is the list of datatypes presented in the API Doc and their usage in PHP.
|
Java Data |
Types Assigning values in PHP |
| String | “firstname\@secondname.com” |
| int | 123 |
| HashMap (Datatype for storing name-value pair) | array(“domain.com”=>”1″) |
| Array and Vector (Datatype for storing more than one value) | array(“ns1.domain.com”,”ns2.domain.com”) |
| boolean (Datatype for storing true or false) | true / false |
Example:
For Calling a Function which takes a String datatype and an integer datatype as its paramters
public int function1(java.lang.String userName, int parentid)
$result = $obj->function1(“firstname\@secondname.com”,1);
For Calling a Function which takes a HashMap, a String Array and an integer Array as its parameters
public java.util.HashMap function2(java.util.HashMap domainHash, java.lang.String[] orderby, int[] resellerId)
and domainHash is accepting the domainname and the number of years as name value pair
$result = $obj->function2(array(“domain1.com”=>1,”domain2.com”=>2),array(“column1″,”column2″),array(22,33))
For Calling a Function which takes a Vector and a boolean as its parameters
public java.lang.String function3(java.util.Vector nameServers, boolean add)
$result = $obj->function3(array(“ns1.domain.com”,”ns2.domain.com”),true)
Step 3. Extract the files from the API Kit archive
You should get the following directory & files structure
examples/ – Pre-written examples. You can directly run these examples to test API functionality
lib/ – The PHP class files, library files and wsdl files that you need to run your application
Step 4. Run the examples
You can run the pre-written examples provided in the “examples” folder. Note the following steps to do so -
1. Upload the “examples” and “lib” folders to your web server where you run your PHP scripts. Make sure that both these folders are uploaded to the same parent folder.
2. You must have PHP 4 installed on the server
3. You must have a Demo account ready the first time. Read the General instructions if you have not yet setup your demo account. Reference: General API Integration Instructions >>
The Demo server duplicates all functionality of the live server, however all Domain Names will appear as available on the Demo Server. It does not query the live registry and therefore names which are not available on the live registry will still appear as available on the Demo Server. At times connectivity to the DEMO Registry may be down resulting in errors.
4. Make the appropriate changes to “constants.php” in the “examples” folder, by putting in the values for your “SERVICE_USERNAME”, “SERVICE_PASSWORD”, “SERVICE_PARENTID”. The remaining settings have already been made for you in this file. You may only need to change the path for the “lib” folder if you have uploaded the lib folder elsewhere
5. The URL to which the call is made is maintained in the “config.php” file inside the “lib” folder. By default all calls are made to the demo server URL using HTTP. You can make changes to this file and redirect your calls to the appropriate server
If you are using HTTPS calls you MUST have the extension for CURL installed and enabled in your PHP installation.
6. Another important parameter maintained in the “config.php” file is the variable $DEBUG. If this variable is set to “true”, then for each call you will see the entire XML Request and Response in the output. You should keep it to “true” during testing, but set it to false on the live environment.
7. Every Example file has a set of functions which you can run.
8. Once you have modified the appropriate example file, access it over your webserver by putting in your URL such as http://yourserver/examples/html and choose the required function from the links given in the left frame.
In registering/managing any domain name on the demo server always use ns1.onlyfordemo.net and ns2.onlyfordemo.net as your nameservers. ANY OTHER Nameserver will result in an INVALID NAMESERVER error.
Step 5. Understanding Errors
Make sure you have read the General API Integration Instructions to obtain links to the error format and possible error documents. Reference: General API Integration Instructions >>
Step 6. Writing your own code
After running each example above, if you simply refer to the corresponding .php file in the examples folder you will easily be able to figure out the code snippet you need to write in order to make a similar call.
Making an API call to perform any action is a matter of three steps:
(i) Include the appropriate PHP Class file as below
include($LIB_DIR.”Order.class.php”);
(ii) Obtain a pointer to the required Class. This is done by using the code below
$serviceObj = new Order($LIB_DIR . “wsdl/Order.wsdl”);
(iii) Call the required method on this object. A complete reference of all methods is available in the Docs folder. This can be achieved by using the code below
$AssociativeArray = $serviceObj->setCustomerLock($SERVICE_USERNAME, $SERVICE_PASSWORD, $SERVICE_ROLE, $SERVICE_LANGPREF, $SERVICE_PARENTID, $orderId);
You will notice above that EVERY method in the docs takes the same first 5 parameters as below
String SERVICE_USERNAME, String SERVICE_PASSWORD, String SERVICE_ROLE, String SERVICE_LANGPREF, int SERVICE_PARENTID
In the examples these parameters have been put into a single constants file from which they are accessed by including the constants file. These parameters are common no matter which method you call. These parameters mean the following:
String SERVICE_USERNAME: Your UsernameSERVICE_PASSWORD
String : Your PasswordSERVICE_ROLE
String : This will always be a string "reseller"SERVICE_LANGPREF
String : The 2 letter code of the language in which you wish to receive errors and descriptions - "en" for EnglishSERVICE_PARENTID
int : The ID of your parent which you can get from your profile section
Remember, when passing numerical data in hashtables, please ensure that the number is passed as a String.
Step 7. Change the information to Live information when you are ready
Once you have followed the steps above and got the test examples to work successfully, you can duplicate the same code in your live application and replace the Demo Server and Reseller account information with your live username and password. The URL that you make your calls to also needs to change to the LIVE Server URL. You will make this change in the “config.php” file in the “lib” folder
Once again note, if you are using the HTTPS URL you MUST have the extension for CURL installed and enabled in your PHP installation.
Tags: Api, Api Documentation, Api Guide, Api Kit, appropriate server, Datatype, Datatypes, Demo Server, Docs, Explanations, http, Integers, Integration Guide, Java, Java Data Types, Javadocs, Parameters, Php, Php Guide, PHP installation, Php Java, Php Kit, Php Language, Php4, Platforms, Reference, Step 1, Step 2, Variables, Web Server, Xml
If Gossimer has raised a Invoice or Debit Note for you, you would have to pay for it in order to settle it. Please follow the procedure mentioned below to achieve the same -
Tags: Account Balance, Amp, Billing, Biz, Control, Debit Account, Gossimer, Invoice, Invoices, Reseller Control Panel, Step 2
A Digital Certificate by itself can be used to secure a domain name only on a single server. Additional License(s) for a Digital Certificate allows you to conveniently secure a domain name on multiple servers, using the same Digital Certificate.
You can purchase up to 20 Additional Licenses per Digital Certificate.
Tags: Digital Certificate, Domain Name, Name Servers, Secure Servers, Servers
In order to manage your Digital Certificate orders, you need to search for them from your Control Panel with Gossimer, and access their Order Details view. To do so, follow the simple steps mentioned below –
1. Login to your Control Panel
Resellers do so from http://manage.gossimer.biz/reseller;
Customers do so from http://manage.gossimer.biz/customer.
2. Once logged in to your Control Panel,
Resellers, go to Products -> Search -> Digital Certificate Search
Customers, go to Digital Certificate -> List/Search
and search for the Domain name for which this product has been purchased. (To list all orders, leave all search parameters blank and select the Order Date as All).3. In the next page you would see a list of all Domain Names for whom you have ordered a Digital Certificate through Gossimer.
Clicking on any of the Domain names would take you to the Order details view for the product, where you can manage this order.
Tags: Biz, Certificate Search, Control Panel, Digital Certificate, Domain Name, Domain Names, Gossimer, Reseller Customers, Resellers, Search Domain, Search Parameters, search parameters blank, Simple Steps
Integrating an Electronic Clearing House (Echo-Inc) Credit Card Payment Gateway is very simple and easy process. The Integration does not involve ANY code writing, all you need to do is fill up a form specifying your Account Details and Payment Collection preferences.
Before you Start
I. Signup for a Electronic Clearing House (Echo-Inc) Merchant Account from – http://www.echo-inc.com/echoapp.php
II. Submit your Account Details and Preferences to us:
It consists of the following steps –
1. Login into your Reseller Control Panel from http://manage.gossimer.biz/reseller
2. Click on the Settings -> Finance & Billing -> Payment Gateway -> List / Add
3. Adding a Echo-Inc PG – Click on the Add Payment Gateway button and then on the Add an Electronic Clearing House Credit Card Gateway link.
4. Enter the following Echo-Inc Details and save your changes by clicking on the Submit button
Gateway Name - This Gateway Name would be shown to your Customers / Sub-Resellers, when they are about to make Payment. You can use something like “Credit Card Payment” or “Visa/Master Card” etc.
Merchant ECHO-ID – This is the ECHO-ID provided to you by Echo-Inc, at the time of creation of your Merchant account.
Merchant PIN – The PIN for your Merchant Account with Echo-Inc.
Currency – Currently we allow Echo-Inc to charge your Customers / Sub-Resellers only in US Dollar (USD).
Currency Exchange Rate – If the Currency you selected in the previous option varies from your Selling Currency, we will have to convert the Invoice Value to the Echo-Inc Currency, BEFORE we send your Customer to Echo-Inc. For this purpose the system needs a exchange rate between the two.
You may choose to maintain this exchange rate yourselves or let us maintain it for you. We download forex rates on a daily basis from a recognized source and update exchange rates for you. If however you wish to update the rates yourselves then you may do so by selecting the “I would like to Maintain the currency exchange rate myself” checkbox AND entering your own conversion rates.
Select the types of CREDIT CARD that your Merchant Account Supports: You need to select the types of Credit Card that are supported by your Echo-Inc Merchant Account. The credit card types available are – Visa, Master, Amex, Discover, Diners Card and JCB. You can also decide the sequence in which you want your Customers / Sub-Resellers to view these Card types.
Payment Gateway Access Level for Customers and Sub-Resellers – Click here to know more about Payment Gateway Transaction types and Access Levels for your Customers and Sub-Resellers >>
Deciding whether a Sub-Reseller and Customer is Credited with the Gross Amount or Net – Your Bank and Echo-Inc deducts a fee on a per transaction basis. There are two types of Transactions that can pass through your Echo-Inc integration – Invoice/Debit Note Payment, and Add Funds. Click here to know more about Payment Gateway Transaction types and Access Levels for your Customers and Sub-Resellers >>
In case of an Add Funds Transaction, you have the option of crediting your Customers/Sub-Resellers with the NET Amount that Echo-Inc credits you with, or choose to credit them with the gross funds and bear the charges yourselves. The NET Amount is calculated by subtracting the per transaction charges from the Transaction Amount. The per transaction charges are calculated by adding the Total Fixed fee charged per transaction and the Total Variable fee charged per transaction.
Total Fixed fee charged per transaction for your merchant account (Per Transaction Fixed Fee charged by your Bank + Per Transaction Fixed Fee charged by the Echo-Inc Credit Card Gateway) - Enter the total fixed fee that is charged per transaction in the given textbox. This information is primarily used to calculate the Net Amount that your merchant account is credited with, if you choose to credit your customer / sub-reseller with the Net Amount in an Add funds Transaction. Your bank and/or your gateway may be charging you a different amount of fixed fee per transaction for different credit card types e.g. a certain fixed fee per transaction for Visa cards and a different fixed fee for American Express cards. In case, the amount of fixed fee is different per credit card type, then enter the highest amount of fixed fees charged per transaction to your account e.g. if the total fixed fee for Visa Cards is 25 cents per transaction and the total fixed fee for American Express cards is 30 cents per transaction, then enter 0.30 in the textbox. If there is no fixed fee charged per transaction then enter 0.
Total Variable fee charged per transaction for your merchant account - Enter the total variable fee that is charged per transaction in the given textbox. This information is primarily used to calculate the Net Amount that your merchant account is credited with, if you choose to credit your customer / sub-reseller with the Net Amount in an Add funds Transaction. Your bank and/or your gateway may be charging you a different amount of variable fee per transaction for different credit card types e.g. a certain variable fee per transaction for Visa cards and a different variable fee for American Express cards. In case, the amount of variable fee is different per credit card type, then enter the highest amount of variable fees charged per transaction to your account e.g. if the total variable fee for Visa Cards is 2.50% per transaction and the total variable fee for American Express cards is 3.00% per transaction, then enter 3.00 in the textbox. If there is no variable fee charged per transaction then enter 0.
If you have selected to credit a Customer/Sub-Reseller with the Net Amount in an Add Funds transaction, then you must submit either a Fixed Transaction fee (greater than 0) or a Variable Transaction fee (greater than 0).
Send me a Reminder if a transaction is pending for more than x days – In case you have not yet accepted a payment sent to you via the Echo-Inc Payment Gateway, you can get e-mail reminders sent across to you from our system, after every x number of days, until you either Approve or Decline these payments. Click here to know how to Approve / Decline Payment Gateway transactions >>
Display Position – If you plan on adding Multiple Gateways you can select the position in which you wish to display this Gateway on your Payment Page.
The SuperSite contains information about the various Payment options you offer to your Customers and also presents these options at the time of purchasing Products and Services. This data is downloaded to your SuperSite from your Control Panel and cached (stored) on the SuperSite Server. Hence, you would need to refresh the cache of your SuperSite once you have completed the above process. You can accomplish this from within your Control Panel itself by clicking on Tools -> Reload SuperSite & PartnerSite Cache -> SuperSite Payment Preferences. Click here to know what is SuperSite >>
Tags: Account Details, American Express, Amp, bank, Billing, cent, Credit Card Gateway, Credit Card Payment, Currency Exchange Rate, Daily Basis, Electronic Clearing House, Exchange Rates, Finance, Gateway Link, Invoice Value, Merchant Account, Payment Gateway, Pg, Php, Reseller Control Panel, Resellers, Visa Card, Visa Master Card, Visa Merchant
Follow the process mentioned below to specify a backup policy:
1. Login to your Control Panel, search for the domain name for which you have purchased this hosting package and proceed to the Order Details view. Click here to read how >>
2. Click on Manage Web Hosting Service in the lower toolbar.
3. In the Website Management interface pop-up that follows, go to Manage Website -> Backup Manager -> Add Backup Policy.
4. Specify the following details
5. Click on Submit.
Tags: Archive Files, Backlogs, Backup Directory, Backup Manager, Backup Policy, Control Panel, Details View, Domain Name, Gt 2, Manage Web Hosting Service, Management Interface, Rotation Cycle, Web Hosting Service, Web Service, Website Management
Cache refers to copies of previously accessed Web pages and associated files are stored on a user’s computer or on computers operated by an ISP. A cache merely stays between the server (web servers storing websites) and clients (website viewers), and saves copies of data retrieved, such as HTML pages, and images. Now, when the viewer makes a request for the same data again, it can be served from the cache itself instead of making a fresh query to the original server.
Caches can be classified on basis of their levels of operation, as follows:
1. Browser Caches: The cache setting on your web browser saves content specifically for you. It takes up a portion of your computer’s storage to save copies of the pages you have visited. Its functioning is fairly simple – it simply checks whether the page you are requesting has been visited in the current session, since the browser was started.
The functioning of this cache becomes evident when you hit the BACK button in your browser. Notice the difference in the time it takes to load the same (last visited previously) page now, than it did before (on first request).
2. Proxy Caches: Web proxy caches cater to a large number of users. They are deployed with the aim of reducing network traffic. Proxies serve several users just the way your browser cache serves your purpose. Proxy caches are most useful when it comes to serving the most popular content.
These are often setup by ISPs on their firewalls, and not by the client. For them to function effectively, it is vital that all requests from the clients be retrieved through the proxy. Now, this can be done either by
3. Gateway Caches: Gateway caches are also known as reverse proxy caches. These are generally setup by website administrators to improve the performance and reliability of their websites.
Content delivery networks (CDNs) have linked servers throughout the Internet that help reduce network congestion and server overload for content delivered to many users, serving as gateway caches. Akamai is an example of such CDNs.
Caches are used for 2 main reasons
Tags: Aim, Browser Cache, Browser Caches, Browser Notice, Browser Setting, Cache Cache, Content delivery networks, Firewalls, HTML, Html Pages, Isp, Isps, Network Traffic, Proxies, Reliability, Reverse Proxy, Server Caches, Server Web, Storage, Web Browser, web browser saves content, Web Pages, Web Proxy Caches, Web Servers, web servers storing websites, Website Administrators
You can customize the Title of every HTML Page that exists in your SuperSite and PartnerSite. This page title is seen in the title bar, at the top of your browser window.
Follow the process outlined below to customize the Title of HTML pages:
Customizing the Title of HTML pages provided by default
You can customize these by mentioning your desired title, in the text-box.
For Example,
Standard SuperSite/Partnersite HTML page – Login Page => Customer Login Page
Uploaded HTML page – Index Page => My Index Page
IMPORTANTa. You will have to repeat the above process if you have configured multiple languages for your SuperSite/PartnerSite.
b. If you are not satisfied with the modifications and wish to revert to the text displayed earlier, simply follow steps 3 to 5 above. There you will have to copy the text from the left hand side to the textbox and click on Save Changes.
Customizing the Title of HTML pages added by you
For Example,
my_index.html=My Index Page
IMPORTANTIf you are not satisfied with the editing and wish to revert to the default setting, simply click on Reset to Default from the Edit page, to restore the default settings for that file.
Tags: HTML
Depending upon the Web Server software type you selected at the time of Enrolling for a Digital Certificate, thawte determines if your Digital Certificate is re-signable or non-re-signable on their system. This means that certain platforms will require a new CSR upon Renewal while others enable the existing CSR to be re-signed, in which case the new certificate, once issued, will only work on the private key file that was used to create the CSR originally submitted to thawte. Click here to find a list of Web Server Software platforms which support a re-signable CSR on Renewal >>
thawte Digital Certificates have a lifespan of 1 or 2 years, depending upon the validity period you chose at the time of purchase. You can Renew your Digital Certificate within 90 days prior to its Expiry and within 30 days post Expiry. However, thawte will issue the Digital Certificate only 32 days before your current Certificate expires. This allows you to request your Renewal Certificate timorously and prevents any warnings for your website users which would have been displayed if your existing Certificate would have Expired.
Follow the below mentioned process to Renew your Digital Certificate:
During the Digital Certificate Enrollment process for a SSL123 Certificate, you need to choose either the Corporate Contact or the Technical Contact as the Authorizing Contact for your Digital Certificate.
During the Enrollment process for a SSL123 Certificate, if you had chosen the Corporate Contact as the Authorizing Contact and had matched a pre-determined email address (email alias) with the domain name for which you were requesting the Certificate, then you will be required to provide the Corporate Contact Email Address while Renewing the Certificate.
Once you have Renewed your Digital Certificate successfully, you would be issued your new certificate. You can check the status of your Digital Certificate by clicking the Check Certificate Status button in the Order Details view of the Digital Certificate Order. Once the certificate is issued, you can retrieve the same from the above interface itself and install this renewed certificate on your web server.
Reference:
Click here to find instructions on how to check the status of your Digital Certificate and retrieve your Renewed Digital Certificate >>
Click here to find instructions on how to install your Digital Certificate >>
Tags: Csr, Current, Digital Certificate, Domain Name, Expiry, Key File, Lifespan, Nbsp, Privacy Protection, Private Key, Renew Service, Renewal Certificate, Software Platforms, Software Type, Thawte Digital Certificates, Timorously, Validity Period, Web Server, Web Server Software, Website Users, Website Visitors
The Domain Name System [DNS] is a distributed database, arranged hierarchically, containing records for domain names. The DNS system’s main aim is to match a domain name to an IP Address. In order to fulfill this role, the DNS Server contains Records [called Resource Records] in a Zone File, which contains the domain name and IP address mappings for computers contained within that Zone. All Resource Records have a TTL [Time To Live], specifying the number of seconds other DNS servers and applications are allowed to cache the record.
Most Web Hosting companies do not provide you with an interface to manage your own DNS Records and/or the ability to select multiple providers for various Services like Web Hosting, Mail Hosting, etc..
Gossimer gives you complete control over the following Resource Records by using our Managed DNS Service:
I. Address Record [A Record]
The A Record is the most basic and the most important DNS record type. They are used to translate human friendly domain names such as “www.domain.com” into IP-addresses such as 1.2.3.4 (machine friendly numbers).
When you wish to host your domain name, you will be provided with an IP address that needs to be set as an A Record for that particular domain name.
II. Mail Exchanger [MX] Record
A MX Record identifies the mail server(s) responsible for a domain name. When sending an e-mail to user@xyz.com, your mail server must first look up the MX Record for xyz.com to see which mail server actually handles mail for xyz.com (this could be mail.xyz.com – or someone else’s mail server like mail.isp.com). Then it looks up the A Record for the mail server to connect to its IP-address.
A MX Record has a Preference number indicating the order in which the mail server should be used (only relevant when multiple MX Records are defined for the same domain name). Mail servers will attempt to deliver mail to the server with the lowest preference number first, and if unsuccessful continue with the next lowest and so on.
III. Canonical Name [Alias / CNAME] Record
CNAME Records are domain name aliases. Often computers on the Internet have multiple functions such as Web Server, FTP Server, Chat Server, etc. To mask this, CNAME Records can be used, to give a single computer multiple names (aliases).
Sometimes companies register their multiple domain names for their brand-names but still wish to maintain a single website. In such cases, a CNAME Record maybe used to forward traffic to their actual website. For example, www.abc.in could be CNAMEd to www.abc.com.
The most popular use of the CNAME Record type, is to provide access to a Web Server using both the standard www.domain.com and domain.com (without the www). This is usually done by adding a CNAME-record for the www name pointing to the short name [while creating an A Record for the short name (without www)].
CNAME Records can also be used when a computer or service needs to be renamed, to temporarily allow access through both the old and new name.
IV. Authoritative Name Server [NS] Record
NS Records identify DNS servers responsible (authoritative) for a Zone. A Zone should contain one NS Record for each of its own DNS servers (primary and secondaries). This mostly is used for Zone Transfer purposes (notify). These NS Records have the same name as the Zone in which they are located.
But the most important function of the NS Record is Delegation. Delegation means that part of a domain is delegated to other DNS servers.
You can also delegate sub-domains of your own domain name (such as subdomain.yourname.com) to other DNS servers. An NS Record identifies the name of a DNS server, not the IP Address. Because of this, it is important that an A Record for the referenced DNS server exists, otherwise there may not be any way to find that DNS server and communicate with it.
If a NS Record delegates a sub-domain (subdomain.yourname.com) to a DNS Server with a name in that sub-domain (ns1.subdomain.yourname.com), an A Record for that server (ns1.subdomain.yourname.com) must exist in the Parent Zone (yourname.com). This A Record is referred to as a Glue Record, because it doesn’t really belong in the Parent Zone, but is necessary to locate the DNS Server for the delegated sub-domain.
V. Text [TXT] Record
A Text Record provides the ability to associate some text with a domain or a subdomain. This text is meant to strictly provide information and has no functionality as such. A TXT Record can store upto 255 characters of free form text. This record is generally used to convey information about the zone. Multiple TXT records are permitted but their order is not necessarily retained.
For example, you may add a TXT Record for yourname.com with the value as “This is my mail server”. Here if anybody was checking ALL or TXT records of yourname.com, they would notice the above text appearing in the TXT record.
TXT Record is also used to implement the Sender Policy Framework (SPF) and DomainKeys specifications.
Sender Policy Framework (SPF)
Sender Policy Framework is an extension to the Simple Mail Transfer Protocol (SMTP). SPF allows software to identify and reject forged addresses in the SMTP MAIL FROM (Return-Path), a typical nuisance in e-mail spam.
SPF allows the owner of a domain to specify their mail sending policy, e.g. which mail servers they use to send mail from their domain. The technology requires two sides to work in tandem -
i. the domain owner publishes this information in an TXT Record in the domain’s DNS zone, and when someone else’s mail server receives a message claiming to come from that domain, then
ii. the receiving server can check whether the message complies with the domain’s stated policy. If, for example, the message comes from an unknown server, it can be considered a fake.
DomainKeys
DomainKeys is an e-mail authentication system (developed at Yahoo!) designed to verify the authenticity of the E-mail sender and the message integrity (i.e,. the message was not altered during transit). The DomainKeys specification has adopted aspects of Identified Internet Mail to create an enhanced protocol called DomainKeys Identified Mail (DKIM).
VI. Start of Authority [SOA] Parameters
Each Zone contains one SOA Record, which holds the following parameters for the Zone -
Name of Primary DNS Server - The domain name of the Primary DNS Server for the Zone. The Zone should contain a matching NS Record.
Mailbox of the Responsible Person – The email address of the person responsible for maintenance of the Zone.
Serial Number - Used by Secondary DNS Servers to check if the Zone has changed. If the Serial Number is higher than what the Secondary Server has, a Zone Transfer will be initiated. This number is automatically increased by our Servers when changes to the Zone or its Records are made.
Refresh Interval - How often Secondary DNS Servers should check if changes are made to the zone.
Retry Interval - How often Secondary DNS Server should retry checking, if changes are made – if the first refresh fails.
Expire Interval - How long the Zone will be valid after a refresh. Secondary Servers will discard the Zone if no refresh could be made within this interval.
Minimum (Default) TTL - Used as the default TTL for new records created within the zone. Also used by other DNS Server to cache negative responses (such as record does not exist, etc.).
Tags: Complete Control, delegate, DNS, DNS system, Dns Record Type, Dns Records, Dns Server, Dns Servers, Dns Service, Domain Name System, Domain Names, Domain Owner, E Mail, Internet Mail, Ip Address, Mail Exchanger, Mail Hosting, Mail Server, Mail Servers, Mappings, Mx Record, Mx Records, Resource Records, Sending Mail, Server Mail, SOA, unknown server, Web Hosting, Web Hosting Companies, Web Mail, Web Server, www.abc.com, www.abc.in, www.domain.com, Yahoo!