Pages

What Is the GNU Public License?

What Is the GNU Public License?
The most important thing to emerge from the GNU project has been the GNU General Public
License (GPL). This license explicitly states that the software being released is free, and that
no one can ever take away these freedoms. It is acceptable to take the software and resell it,
even for a profit; however, in this resale, the seller must release the full source code, including any changes. Because the resold package remains under the GPL, the package can be distributed free and resold yet again by anyone else for a profit. Of primary importance is the liability clause: The programmers are not liable for any damages caused by their software. More about GNU and the GPL can be found at http://www.gnu.org.

It should be noted that the GPL is not the only license used by free software developers
(although it is arguably the most popular). Other licenses, such as BSD and Apache, have
similar liability clauses but differ in terms of their redistribution. For instance, the BSD license
allows people to make changes to the code and ship those changes without having to disclose
the added code. (The GPL would require that the added code be shipped.) For more information about other open-source licenses, check out http://www.opensource.org.

ISP’s Primary DNS Server Setup Architecture

ISP’s Server Architecture

Primary DNS Server:

Partition Table Informtion

Filesystem Size Used Avail Use% Mounted on

/dev/sda1 3.0G 667M 2.2G 24% /

tmpfs 252M 0 252M 0% /dev/shm

/dev/sda5 102M 36M 67M 36% /boot

/dev/sda7 2.4G 33M 2.2G 2% /tmp

/dev/sda2 2.0G 96M 1.8G 5% /var

Packages used for DNS: bind-utils-9.3.1-3, bind-chrootenv-9.3.1-3, bind-9.3.1-3, bind-libs-9.3.1-3.2

Configuration file: /etc/named.conf

# Copyright (c) 2001-2004 SuSE Linux AG, Nuernberg, Germany.

# All rights reserved.

#

# Author: Frank Bodammer, Lars Mueller

#

# /etc/named.conf

#

# This is a sample configuration file for the name server BIND 9. It works as

# a caching only name server without modification.

#

# A sample configuration for setting up your own domain can be found in

# /usr/share/doc/packages/bind/sample-config.

#

# A description of all available options can be found in

# /usr/share/doc/packages/bind/misc/options.

options {

# The directory statement defines the name server's working directory

directory "/var/lib/named";

# Write dump and statistics file to the log subdirectory. The

# pathenames are relative to the chroot jail.

dump-file "/var/log/named_dump.db";

statistics-file "/var/log/named.stats";

# The forwarders record contains a list of servers to which queries

# should be forwarded. Enable this line and modify the IP address to

# your provider's name server. Up to three servers may be listed.

#forwarders { 192.0.2.1; 192.0.2.2; };

# Enable the next entry to prefer usage of the name server declared in

# the forwarders section.

#forward first;

# The listen-on record contains a list of local network interfaces to

# listen on. Optionally the port can be specified. Default is to

# listen on all interfaces found on your system. The default port is

# 53.

#listen-on port 53 { 127.0.0.1; };

# The listen-on-v6 record enables or disables listening on IPv6

# interfaces. Allowed values are 'any' and 'none' or a list of

# addresses.

listen-on-v6 { any; };

# The next three statements may be needed if a firewall stands between

# the local server and the internet.

#query-source address * port 53;

#transfer-source * port 53;

#notify-source * port 53;

# The allow-query record contains a list of networks or IP addresses

# to accept and deny queries from. The default is to allow queries

# from all hosts.

#allow-query { 127.0.0.1; };

# If notify is set to yes (default), notify messages are sent to other

# name servers when the the zone data is changed. Instead of setting

# a global 'notify' statement in the 'options' section, a separate

# 'notify' can be added to each zone definition.

notify no;

};

# To configure named's logging remove the leading '#' characters of the

# following examples.

#logging {

# # Log queries to a file limited to a size of 100 MB.

# channel query_logging {

# file "/var/log/named_querylog"

# versions 3 size 100M;

# print-time yes; // timestamp log entries

# };

# category queries {

# query_logging;

# };

#

# # Or log this kind alternatively to syslog.

# channel syslog_queries {

# syslog user;

# severity info;

# };

# category queries { syslog_queries; };

#

# # Log general name server errors to syslog.

# channel syslog_errors {

# syslog user;

# severity error;

# };

# category default { syslog_errors; };

#

# # Don't log lame server messages.

# category lame-servers { null; };

#};

# The following zone definitions don't need any modification. The first one

# is the definition of the root name servers. The second one defines

# localhost while the third defines the reverse lookup for localhost.

zone "." in {

type hint;

file "root.hint";

};

zone "localhost" in {

type master;

file "localhost.zone";

};

zone "0.0.127.in-addr.arpa" in {

type master;

file "127.0.0.zone";

};

zone "ns1" IN {

type master;

file "master/ns1.zone";

allow-transfer {202.125.142.117;};

};

zone "142.125.202.in-addr.arpa" IN {

type master;

file "master/rns1.zone";

};

zone "pucit.edu.pk" IN {

type master;

file "master/pucitedu.zone";

allow-transfer {202.125.142.117;};

};

zone "pucitonline.net" IN {

type master;

file "master/pucitnet.zone";

allow-transfer {202.125.142.117;};

};

zone "mapasha.com" IN {

type master;

file "master/mapasha.zone";

allow-transfer {202.125.142.117;};

};

zone "mtexperts.co.uk" IN {

type master;

file "master/mtexpert.zone";

allow-transfer {202.125.142.117;};

};

zone "agiletechnologies.org" IN {

type master;

file "master/agile.zone";

allow-transfer {202.125.142.117;};

};

zone "ktexperts.com" IN {

type master;

file "master/ktexperts.zone";

allow-transfer {202.125.142.117;};

};

zone "completeislam.com" IN {

type master;

file "master/cislam.zone";

allow-transfer {202.125.142.117;};

};

zone "peace.com.pk" IN {

type master;

file "master/peace.zone";

allow-transfer {202.125.142.117;};

};

zone "ghazisolutions.com" IN {

type master;

file "master/ghazi.zone";

allow-transfer {202.125.142.117;};

};

zone "puran.info" IN {

type master;

file "master/puran.zone";

allow-transfer {202.125.142.117;};

};

zone "nms.pucit" IN {

type master;

file "master/nms.zone";

allow-transfer {202.125.142.117;};

};

zone "pucitonline.com" IN {

type master;

file "master/pucitonline.zone";

Allow-transfer {202.125.142.117;};

};

zone "ngnexporters.com" IN {

type master;

file "master/ngnexporters.zone";

Allow-transfer {202.125.142.117;};

};

# Include the meta include file generated by createNamedConfInclude. This

# includes all files as configured in NAMED_CONF_INCLUDE_FILES from

# /etc/sysconfig/named

include "/etc/named.conf.include";

# You can insert further zone records for your own domains below or create

# single files in /etc/named.d/ and add the file names to

# NAMED_CONF_INCLUDE_FILES.

# See /usr/share/doc/packages/bind/README.SUSE for more details.

/var/lib/named/pucitnet

$TTL 2D

@ IN SOA ns1.pucitonline.net. root.pucitonline.net. (

200312121;

3600;

3600;

3600;

1h );

IN NS ns1

IN NS ns2

ns1 IN A 202.125.142.107

ns2 IN A 202.125.142.117

www IN A 202.125.142.121

pucitonline.net. IN MX 10 mail

mail IN A 202.125.142.115

ftp IN A 202.125.142.121

radius IN A 202.125.142.108

nms IN A 202.125.142.108

/var/lib/named/pucitedu

$TTL 2D

@ IN SOA ns1.pucitonline.net. root.pucitonline.net. (

200312121;

360;

3600;

3600;

1h );

IN NS ns1.pucitonline.net.

IN NS ns2.pucitonline.net.

ns1 IN A 202.125.142.107

ns2 IN A 202.125.142.117

www IN A 202.125.142.121

pucit.edu.pk. IN MX 10 mail

mail IN A 202.125.142.122

ftp IN A 202.125.146.174

flypucit IN A 202.125.142.109

moon IN A 202.125.142.97

library IN A 202.125.142.112

alumni IN A 202.125.142.112

lectures IN A 202.125.142.112

Forex Trading