On current move ICANN has started deleting outdated domain, they have already deleted .um tld, .um is now no more in use, this domain was for US minor outlying islands and the university of Southern California’s Information Science Institute which had grown tired for maintaining it. Another domain .su comes on the top of the list on deletion of outdated suffixes, however it is not easier for ICANN to remove .su as google still lists 3 million of .su sites though ICANN has started taking comments for deletion of such outdated domain.

You can follow these simple step for a 301 Redirect on your website using a Unix server:

* Create or locate a .htaccess file on your server. Your .htaccess file gives search engine robots instructions on security and redirects.

* If you don’t have an .htaccess file on your server, you can easily create one using a text file. Name it “.htaccess”

* If there is already an .htaccess file scroll down past the code that is already there and begin your new redirect instructions.

* Put in your redirect information, which should look like this:
redirect 301 /directory/file.html http://www.domainame.com/directory/file.html

* Note: The first part “/directory/file.html” is the location of the file being moved and the second part “http://www.domainame.com/directory/file.html” is where the file is being moved.

* Upload the file to your server.

How to access cpanel without pointing DNS to that server

Hello Friends,

You can access your cpanel without pointing your DNS to that server from your local machine. For that please follow the following steps.

1. Make sure that you are having the account on that server which you are trying to access.

2. You must have the cpanel login details.

3. put the following entries in your local machine hosts file. for that edit

c:\WINDOWS\system32\drivers\etc\hosts

add the following line as

domain.com

and now you can access your cpanel without pointing DNS to that server.

The Domain Name System (DNS) is a distributed database system that provides hostname-to-IP resource mapping (usually the IP address) and other information for computers on an internetwork. Any computer on the Internet can use a DNS server to locate any other computer on the Internet.

DNS is made up of two distinct components, the hierarchy and the name service. The DNS hierarchy specifies the structure, naming conventions, and delegation of authority in the DNS service. The DNS name service provides the actual name-to-address mapping mechanism.

Each organization that maintains a computer network will have at least one server which is handling DNS queries. That server is called a name server.
Each computer on each network needs to know the location of only one name server. When your computer requests an IP address, one of three things happens, depending on whether or not the requested IP address is within your local network:

1) If the requested IP address is registered locally (i.e., it’s within your organization’s network), you’ll receive a response directly from one of the local name servers listed in your workstation configuration.

2) If the requested IP address is not registered locally (i.e., outside your organization’s network), but someone within your organization has recently requested the same IP address, then the local name server will retrieve the IP address from its cache. There should be little or no wait for a response.

3) If the requested IP address is not registered locally, and when you are accesing it first time then the local name server will perform a search on behalf of your workstation. This search may involve querying two or more other name servers at potentially very remote locations. These queries can take anywhere from a second or two up to a minute (depending on how well connected you are to the remote network and how many intermediate name servers must be contacted). Sometimes, due to the lightweight protocol used for DNS, you may not receive a response. In these cases, your workstation or client software may continue to repeat the query until a response is received, or you may receive an error message.

When you use an application such as telnet to connect to another computer, you most likely type in the domain name rather than the IP address of that computer. The telnet application takes the domain name and uses one of the above methods to retrieve its corresponding IP address from the name server.

Following are the TCP/IP Application protocols:
1.DHCP:

DHCP Dynamic Host Configuration Protocol is defined by RFC’s 2131
and 2132.DHCP is Dynamic Host Configuration
Protocol (DHCP) allows IP addresses to
be allocated to hosts on an as-needed basis.DHCP lets a host
‘borrow’ an IP address from a pool of IP addresses; when the
address is no longer required it is recycled and made available for
use by other host. DHCP also allows a host to retrieve a
verity of configuration information.

DCHP depends on UDP to carry packets between the client and server
tasks.

2. DNS

The DNS (Domain Name System) provides ondemand dynamic
translation between human-readable names (like www.mydoamin.com)
and the numeric addresses actually used by IP (like
192.169.10.28). The basics of DNS operation are defined in RFC’s
1034, 1101, 1876, 1982 and 2065.

A very widely-used implementation of DNS called BIND
(Berkeley Internet Name Domain)
DNS uses both UDP and TCP. It used UDP to carry simple queries and
responses but depends on TCP to guarantee the correct and orderly
delivery of large amounts of bulk data (eg zone configurations) across the network.

3. FTP

File Transfer Protocol (FTP) provides a mechanism for transfering data
files between various systems. In addition to the fundamental PUT and GET
operations, FTP provides a small number of file management and
user authentication facilities. FTP uses port 21

FTP depends on TCP to guarantee the correct and orderly delivery
of data across the network.

4. HTTP

Hyper Text Transfer Protocol (HTTP) is the protocol used to publish
Web pages across an internet. HTTP depends on TCP to guarantee the
correct and orderly delivery of data across the network.

5. IMAP

Interactive Mail Access Protocol (IMAP) allows clients to
manipulate email messages and mailboxes that reside on some server
machine. The current version of IMAP is Version 4, IMAP is more powerful
and more complex than the other widely-used mail-reading protocol
POP.

6. NFS

Network File System (NFS) allows files stored on one machine (the
“server”) to be accessed by other machines (the “clients”) as
though the files were actually present on the client systems. NFS
is defined in terms of a Remote Procedure Call (RPC) abstraction
which in turn formats its packets according to a
processor-independent eXternal Data Representation (XDR).

NFS is most often used over UDP. UDP does not guarantee packet delivery or ordering, so
when NFS runs over UDP the RPC implementation must provide its own
guarantees of correctness.

7. NNTP

Network News Transfer Protocol (NNTP) is used to propagate netnews
postings (including Usenet postings) between systems.

8. NTP

Network Time Protocol (NTP) is used to synchronise time-of-day
clocks between various computer systems. The current version of
NTP is Version 3, defined in RFC 1305.

9. POP

Post Office Protocol (POP) allows clients to read and remove email
from a mailbox that resides on some server machine. The current
version of POP is Version 3, usually referred to as POP3. POP uses port 110

10. Rlogin

Remote Login (rlogin) provides a network terminal or “remote
login” capability. Rlogin is similar to Telnet but it adds a
couple of features that make it a little more convenient than
Telnet.

11. Rsh

Remote Shell (rsh) is an r-command that provides for remote
execution of arbitrary commands. It allows you to run a command on
a server without having to actually log in on the server. More
importantly it allows you to feed data to the remote command and
retrieve the command’s output without having to stage the data
through temporary files on the server.

12. SMTP

Simple Mail Transfer Protocol (SMTP) is used to deliver email from
one system to another. The port used by SMTP is 25.
13. SNMP

Simple Network Management Protocol (SNMP) provides a means of
monitoring and managing systems over a network. SNMP defines a
method of sending queries (the GET and GET-NEXT primitives) and
commands (the SET primitive) from a management station client to
an agent server running on the target system, and collecting
responses and unsolicited event notifications.

14. Ssh

Secure Shell (ssh) provides remote login and execution features
similar to those of the rsh and rlogin r-commands, but ssh
encrypts the data that is exchanged over the network. Encryption
can protect sensitive information, and it is not uncommon for
security-conscious administrators to disable plain rsh and telnet
services in favour of ssh.

The SSH protocol used by the ssh command has also been used to
build a secure file transfer application which can be used as an
alternative to FTP for sensitive data.

15. Telnet

Telnet provides a network terminal or “remote login” capability.
The Telnet server accepts data from the telnet client and forwards
them to the operating system in such a way that the received
characters are treated as though they had been typed at a terminal
keyboard. Responses generated by the server operating system are
passed back to the Telnet client for display.

16. X Window System

The X Window System allows client programs running on one machine to control the graphic
display, keyboard and mouse of some other machine or of a
dedicated X display terminal.

enjoy…..:)

Set SPF record for your domain:

In order to set SPF record for your domain go to the site called

http://www.openspf.org/

Select option there called SPF WIZARD

Put your domain name there and say start.

Select all those options you want there like A record, MX record and press “continue” button.

You will get a spf record for your domain under the heading,

The SPF record:

v=spf1 a mx ?all

Now you will have to put this record in the dns zone for that domain on the server.

You will have to add the entry in dns zone for that domain, for spf record as per given below,

domain.com.  IN  TXT  v=spf1 a mx ?all

You can check whether it is added correct to your domain at — http://www.dnsreport.com/tools/dnsreport.ch?domain=domain.com >> Mail >> SPF record option.