|In the following article we are going to describe how to configure an IP address to host a domain name. This procedure also applies for domain names with wildcard certificate extensions, as explained in previous post on Configuring the DNS Server to Manage Domains andIP Addresses. In this article we are only going to discuss how to change the IP address of a domain name that you already have. It is easy to achieve it, as you just need to change the IP from one of the following sources:|
o ICMP Echo Request. An IP address is returned by the ICMP Echo Request message. For this, you need to construct a TCP-socket connection or open a standard query/response transaction on the ICP socket of the remote machine. Then, you can create your own ICMP Echo Request message with the use of the netspn utility or you can copy the ICP Echo Request message and paste it into another application.
o FRS Domain Name System (FRS). The FRS is a part of the ICMP Echo Request (ICMP ECHORE) message. The FRS is a standard that allows domain name resolution from a trusted source. Basically, when you enter a domain name into a computer that is not configured to handle FRS, the computer returns an ICMP ECHORE message for more than 1 sec. In order to configure a computer to return the ICMP ECHORE message from a trusted domain name, you need to enable the Use Default DNS to FRS Policy in the Network settings.
o Session Initiation Protocol (SIP). The SIP is a standard that enables a client to establish a session on an IP network. The IP address of the client is translated by the client in the TCP/IP packet and this packet is sent to the remote system for translation and authentication
o Ressource Eines. In previous discussion it was mentioned that a domain name represents a point in a data stream. This concept is very much similar to the concept of a buffer. However, in this case, a domain name is translated directly into an IP address, which is an independent point within the data stream. Furthermore, the data stream can be broken up into smaller pieces and this is done by the ressource server in session 2.
o Domain Name Server (DNS). Basically, the DNS is a name server that translates a domain name into an IP address. Basically, the DNS servers work with domain name queries and provide information on the addresses of the requested names. They are mainly used by organizations and webmasters. The DNS also controls which names are accessible through DNS and these names are actually related to IP addresses.
o Protocol Server. On the other hand, the protocol server controls and coordinates the communication between the domain name client and the IP data resource. It is responsible for encapsulating the domain name and IP address in a certain type of traffic that enables data exchange. Usually, the protocol servers are run on the network nodes. Some also use a layer 2 multipoint technology to provide efficient data transfers.
o Resolver. As the name implies, the resolver acts as a middleman between the domain name server and the IP data resource. In simple words, the resolver maps the IP addresses to domain name clients. As the name suggests, it translates the domain name into IP address and vice versa. Therefore, a single IP address can be represented by multiple domain name clients.
o Lookup/Query Server. The lookup/querying server is another component that acts as a link between the DNS and the domain name client. Basically, it performs a reverse search or query on the domain name provided. This is done to obtain information about any sub-domain or top level domain name. These servers can be either resolved locally or via an IP changing agent.
o Forwarding Server. Another component of the DNS is the forwarding server. This server broadcasts domain name requests to the name servers and IP changing agents. It forwards the request to the domain name client where it receives and parses the requested information and returns it to the domain name server.
o Lookup/ Query Database. As already mentioned, a DNS has a large number of IP addresses, and it is only logical to store information about all these addresses. This is done via the lookups and queries database. This is a part of the DNS which contains the information about every IP address registered in the system. In short, this database is the heart of IP DNS and serves as a repository from which domain name clients can lookup or get details about any IP address.