NEW DELHI: Internet search giant Google has won a cybersquatting case at the World Intellectual Property Organization (WIPO) against an Indian who had tried to block the domain name ‘googblog.com’.

According to the information available with the WIPO, Geneva-based WIPO Arbitration and Mediation Center has ordered the transfer of domain name to the US-based search giant after Herit Shah of Gujarat offered to surrender the disputed name to Google.

Google had challenged the registering of domain name ‘googblog.com’ by Shah at WIPO stating that it was confusingly similar to its trademark on which the company has rights.

Cybersquatting is an illegal activity of buying and officially recording an address on the internet that is the name of an existing company or a well-known person, with the intention of selling it to the owner in order to make money.

As per the information available with the WIPO, Google filed the complaint against Shah on March 26 this year. However, the disputed name has been registered by Shah since September 25, 2008.

WIPO is a specialised agency of the United Nations for developing a balanced and accessible international system in the field of intellectual property rights.

The California-headquartered firm has been using the name ‘GOOG’ as a NASDAQ financial stock ticker since 2004. The company has used the trademark GOOGLE since the inception of its business in 1997.

The search giant operates a blog service under the brand ‘Blogger’. As per the details available with WIPO, a pre-complaint correspondence between the parties (Google and Shah) failed to resolve the dispute.

However on May 2, after commencement of administrative proceedings, Shah stated before the panel that the registration of domain name was in bad faith and was an infringement of intellectual property.

"I was in a bad faith that I can legally keep the domain googblog.com … I really did very unfair to Google. I sincerely apologize to Google for infringement, misuse of their intellectual property (GOOGBLOG.COM)," Shah stated.

The WIPO panel found in this case the consent-to-transfer request replaces the need to assess the matter under the elements of its Uniform Domain Name Dispute Resolution Policy and ordered the transfer of the domain name to Google.

Incoming search terms:

latest domain name dispute cases

Overview

Network Tools allow a user to find information about a domain. This can be useful when making sure your DNS is set up properly. This feature provides a way for you to find out information about your IP address as well as your DNS entries. Network Tools also allow you to run a trace the route from the server your site is on to the computer you are accessing cPanel. The information shown will provide the number of servers and what servers your data must pass through to get to your site.

Using Domain Lookup

To use the “Domain Lookup” feature, enter the domain you want to lookup in the “Enter a domain to lookup” text box. Then click on the Lookup button. The next screen provides information about the domain you are looking up.

Using The Trace Route

Click on the Trace button. The next screen provides information about the trace route, including hops and number of milliseconds it took each hop during the route from your computer to the domain you are using cPanel.

Incoming search terms:

network tools

ACTIVE: The registry sets this status. The domain can be modified by the registrar. The domain can be renewed. The domain will be included in the zone if the domain has been delegated to at least one name server.

REGISTRY-LOCK: The registry sets this status. The domain can not be modified or deleted by the registrar. The registry must remove the REGISTRY-LOCK status for the registrar to modify the domain. The domain can be renewed. The domain will be included in the zone if the domain has been delegated to at least one name server.

REGISTRAR-LOCK: The sponsoring registrar sets this status. The domain can not be modified or deleted. The registrar must remove REGISTRAR-LOCK status to modify the domain. The domain can be renewed. The domain will be included in the zone.

REGISTRY-HOLD: The registry sets this status. The domain can not be modified or deleted by the registrar. The registry must remove the REGISTRY-HOLD status for the registrar to modify the domain. The domain can be renewed. The domain will not be included in the zone.

REGISTRAR-HOLD: The sponsoring registrar sets this status. The domain can not be modified or deleted. The registrar must remove REGISTRAR-HOLD status to modify the domain. The domain can be renewed. The domain will not be included in the zone.

REDEMPTIONPERIOD: The registry sets this status when a registrar requests that the domain name be deleted from the registry and the domain has been registered for more than 5 calendar days (if the delete request is received within 5 days of initial domain registration it will instead be deleted immediately). The domain will not be included in the zone. The domain can not be modified or purged; it can only be restored. Any other registrar requests to modify or otherwise update the domain will be rejected. The domain will be held in this status for a maximum of 30 calendar days.

PENDINGRESTORE: The registry sets this status after a registrar requests restoration of a domain that is in REDEMPTIONPERIOD status. The domain will be included in the zone. Registrar requests to modify or otherwise update the domain will be rejected. The domain will be held in this status while the registry waits for the registrar to provide required restoration documentation. If the registrar fails to provide documentation to the registry within 7 calendar days to confirm the restoration request, the domain will revert to REDEMPTIONPERIOD status. The domain status will be set to ACTIVE only if the registrar provides documentation to the registry within 7 calendar days to confirm the restoration request.

PENDINGDELETE: The registry sets this status after a domain has been set in REDEMPTIONPERIOD status and the domain has not been restored by the registrar. The domain will not be included in the zone. Once in this status all registrar requests to modify or otherwise update the domain will be rejected. The domain will be purged from the registry database after being in this status for 5 calendar days.

Incoming search terms:

Domain Name Status Codes

If you wish to change the setup of the VirtualHosts for all domains, you can do so by creating your own custom templates.

cd /usr/local/directadmin/data/templates
cp virtual_host*.conf custom
cd custom

Once you’ve copied the 4 VirtualHost files (or just the ones you want) to the custom directory, you can then edit the new files you’ve just copied. DirectAdmin will always check for the custom file before going to the default ones. Failure to copy the virtual_host*.conf files to the custom directory before modifying them will result in a loss of all changes when DirectAdmin updates itself (the files are overwritten). Note that there are actually 8 virtual_host files, but you only need to worry about the 4 that apply to you. The files with the 2 in them are for apache 2.x. The ones without the 2 in them are for apache 1.3.
Inside the virtual_host*.conf files, you’ll find code that is similar to httpd.conf code, but contains what are known as tokens. These tokens are what will be replaces with specific user data for each domain created.

Available tokens

DOMAIN
the name of the domain. eg: domain.com

IP
the IP address associated with that domain. eg: 192.168.3.4

HOME
The users home directory. eg: /home/gary

ADMIN
The email address of the server admin. webmaster@domain.com

HOSTNAME
The hostname of the server. eg: server.domain.com

SAFE_MODE
ON or OFF if php safe_mode is enabled or not

PHP
ON or OFF if php is enabled or not

CGI
The whole httpd.conf line used to add the Script-Alias

HANDLERS
httpd.conf code holding all apache handlers

MIMETYPE
httpd.conf code holding all apache mime types

USER
the username

GROUP
the users group name (99% of the time, it’s the same as the USER)

DOCROOT
The DocumentRoot of the VirtualHost. This is the path that apache will use to access the data when the ServerName (domain.com) is requested

SUB
for the virtual_host_*sub.conf file, the subdomain name. eg: sub

CUSTOM
custom httpd.conf code to be inserted if the domain.com.cust_httpd file exists. (See Adding custom httpd.conf code the VirtualHost of one domain)

CAROOT
The whole httpd.conf line used to load in the SSLCACertificateFile directive

CERT
The path of the certificate to be used for the domain

KEY
The path of the certificate to be used for the domain

The top of the templates should contain |?CGI=…| and |?DOCROOT=…|. These lines are where the data for the CGI and DOCROOT tokens are set. If cgi is not enabled, this line wil be ignored and the CGI token will be empty. If the domain is suspended, the DOCROOT will be filled the the path of the suspend page. The CAROOT token will be empty unless the User has added a valid CARootCertificate through DA.
You can use tokens when assigning a value to CGI or DOCROOT, just use `TOKEN` instead of |TOKEN|.
Once you are happy with your new virtual_host*.conf files they’ll need to be used in the real httpd.conf files. You can trigger DirectAdmin to rewrite all User httpd.conf files by running:

echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue

The command will be added the the task queue which is checked once per minute, so it may be a few minutes before all httpd.conf files have been rewritten. *Note: the main /etc/httpd/conf/httpd.conf is never overwritten (unless DirectAdmin is reinstalled) so any changes you make will be safe.
Note, that you can also use if-then-else statements if you don’t want all settings to be global. Example, say you want a custom item added, only for 1 domain:

|*if DOMAIN="domain.com"|
#custom item for just this domain
|*endif|

See the if-then-else link for more info on what else you can do with this basic scripting tool.
You can also run actual scripts with database queries, etc… if you wanted using the script portion of the templates.
More info on that here: http://www.directadmin.com/features.php?id=756

Incoming search terms:

cpanel server change virtual host template,custom template cpanel virtual host,direct admin virtual host tutorial,directadmin virtual host template,ign template

Checking Disk Space and Bandwidth 

To check disk space and bandwidth usage, click on the "Statistics" icon from the main control panel menu.  At the top of the screen you will see these tables:

The numbers in the tables represent megabytes, and approximately 1000 megabytes = 1 gigabyte. 

You are provided with two different disk space / bandwidth measurements.  The first table lists usage by domain and the second table lists total usage.  Total usage is generally higher than domain usage because total usage statistics include factors that are separate from your domain, such as MySQL databases and control panel use.  It is possible to host several domains on one account, so separating domain and total usage is necessary.

Note:  DirectAdmin uses total usage (not domain usage) to determine when quotas have been exceeded.

Accessing System Logs

At the top of the Statistics menu are three text links: "Backed up Apache Logs," "Apache Usage Log," and "Apache Error Log."

Backed up Apache Logs

Clicking the "Backed up Apache Logs" link will bring you to a File Manager screen containing a list of .tar.gz files named by domain/subdomain and month.  For example:

Here we see four backups for the month of April: the subdomains (admin, newsub, and reseller), and the backup for the main domain (Apr-2003.tar.gz).  Backed up Apache logs contain both usage and error data.

Click on the file name of the backup to download it.

Note:

Log files are owned by the server administrator and cannot be deleted.  Log files do not count towards your disk space quota.

Apache Usage and Error Logs

Apache usage and error logs can be viewed directly by clicking on the "Apache Usage Log" or "Apache Error Log" link. 

The raw logs appear in a large text box that looks like this:

The above image is an example of an error log.  Viewing raw logs are a great way to troubleshoot specific problems, such as installing and executing scripts.  Both logs (usage and error) are backed up monthly and archived in /home/domain.com/logs.  Please see the previous section ("Backed up Apache Logs") for more information.

Viewing Account Information

The main Statistics menu provides a great deal of information.  As mentioned above, the first two rows of the table (Bandwidth / Disk Space) provide total usage.  That is, DirectAdmin uses these numbers for quota purposes (and not the numbers in the Domain Statistics table — see first section entitled "Checking Disk Space and Bandwidth").

When your account reaches the maximum bandwidth usage, your site will stop functioning until the first day of the next month.  When your account reaches the maximum disk space usage, you will not be able to upload to your site until some files are deleted.

The information in this table is self-explanatory and will not be discussed in depth.  If you haven’t done so already, please set your current e-mail address in the "Email" field and click "Save."

Webalizer Statistics

In the main Statistics menu, click on the appropriate domain name to launch Webalizer.  Please note that your site must be up for 24 hours and have some log activity before Webalizer statistics will become active.

At the first Webalizer screen, you will see a chart (like the one above) and a list of months in a table below.  Click on the month you want to view.  Webalizer statistics are very detailed and will provide a great deal of information about site traffic, most requested URLs, exit points, location of visitors, and much more.

Incoming search terms:

statistic user count not directadmin,directadmin disk space update,directadmin log usage,directadmin no complete usage statistics,directadmin see incomming trafic,minecraft-crack,plugin directadmin stats