Disclaimer © 2009 Zero Intellect. All rights reserved. The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway. This material is not sponsored or endorsed by any of the vendors mentioned in this website and their Logos are trademarks of their own and their affiliates.
|
By zrydento, on December 18th, 2009
While I was looking for free public DNS servers the other day, I happened to come across the Google Public DNS. Reading the FAQ I gathered that it was not based upon BIND or NSD but was a proprietary DNS server written by Google.
When you connect to your ISP, most of the time you get an IP
Continue reading Google Public DNS
By zrydento, on December 16th, 2009
Although BIND is the most popular domain name server software being used today, NSD (“name server daemon”) is another popular alternative open-source server program.
NSD is an authoritative name server (i.e., not implementing the recursive caching function by design) and uses BIND-style zone-files (zone-files used under BIND can usually be used unmodified in NSD, once entered into
Continue reading NSD DNS Server
By zrydento, on December 16th, 2009
When a device on a TCP/IP network starts up and is not configured for a static IP address, it needs to receive an IP address before it can communicate with other devices on the network. A standard computer with a hard disk can be enabled for static configuration but a diskless device that does not have
Continue reading Bootstrap Protocol (BOOTP)
By zrydento, on December 16th, 2009
Domain Name Servers on the internet use various software to function, the most popular DNS server type on the internet is BIND, which stands for Berkeley Internet Name Domain. BIND is the predominant system on UNIX based systems.
BIND was originally created at the University of California, Berkeley and is maintained today by the Internet Systems Consortium.
Continue reading BIND DNS Server
By zrydento, on December 16th, 2009
Booting your host from the network without the need to rely on the local operating system or hard disks is a technology that is not used very often in the corporate environment today with some people never having heard that such a thing is possible. With the way things are moving today with virtual machines, virtual
Continue reading Preboot Execution Environment (PXE)
By zrydento, on December 12th, 2009
Inverse Address Resolution Protocol (Inverse ARP or InARP), is a protocol used for obtaining Network Layer addresses of other nodes from Data Link Layer addresses. For example, in Ethernet networks InARP would primarily be used to get IP addresses when MAC addresses are known.
It is primarily used in Frame Relay and ATM networks, in which Layer
Continue reading Inverse Address Resolution Protocol (InARP)
By zrydento, on December 11th, 2009
For those of you who have heard of Address Resolution Protocol (ARP) and think that Reverse Address Resolution Protocol (RARP) is its complement, they are totally off track. RARP is a computer networking protocol used by a host computer to request for an IPV4 address from another host computer if it does not have one used (not statically assigned), the
Continue reading Reverse ARP is not the reverse of ARP
By zrydento, on December 11th, 2009
The Address Resolution Protocol (ARP) is a computer networking protocol to find out the MAC address (Physical address) of a device when the IP address (Logical address) is known. This is predominantly used in Local Area Network (LAN) environments as well as routing data traffic based on IP addresses when the next hop router must be known.
Continue reading Address Resolution Protocol (ARP)
By zrydento, on December 9th, 2009
Nslookup.exe (abbreviation for name server lookup) is a command line utility used for testing and troubleshooting DNS servers. It is built into Unix (including Linux and variants) and Windows. The main purpose of the utility is to query DNS servers to find DNS details, MX records for a domain, NS servers of a domain
In Windows, Nslookup.exe
Continue reading Nslookup command overview
By zrydento, on December 3rd, 2009
I was reading about private IP addresses and RFC 1918 at http://www.ietf.org/rfc/rfc1918.txt
The RFC clearly divides hosts within enterprises into three categories
Category 1: hosts that do not require access to hosts in other enterprises or the Internet at large; hosts within this category may use IP addresses that are unambiguous within an enterprise, but may be ambiguous between
Continue reading RFC 1918 IP address
|
|
|
Popular Topics