raymond blogs…

$ sudo mount -o loop /path/to/feisty-desktop-i386.iso /tmp/ubuntu-livecd

This command will replace all instances of ‘replaceme’ with ‘newstring’ in files ‘*.php’ on /home/mysite/httpdocs.

find /home/mysite/httpdocs -name '*.php' | xargs replace 'replaceme' 'newstring' --

 cat /etc/passwd | cut -d":" -f1

Follow the links:

Virtual host examples from Apache website.

http://httpd.apache.org/docs/2.0/vhosts/examples.html

Turns out that it is possible to have multiple VirtualHosts on port 80 (Default http), but because of a limitation of SSL, we can’t have multiple VirtualHosts on port 443 (Default https).
I solved the problem as follows. I created the two VirtualHosts on port 80, one on port 443 and one on port 444.

Shared IP, multiple vhosts and multiple SSL certificates on Apache

The process is only 2 steps and involves modifying your Apache configuration.
1.  Create virtual hosts “map file”.
2.  Modify existing SSL vhost.

Caveat: The SSL certificate used will be common to all SSL vhosts.

Hosting multiple SSL vhosts on a single IP/Port/Certificate with Apache2

The following article discusses the following:
Basics Of Virtual Hosts, Name-Based Virtual Hosts, IP-Based Virtual Hosts, Configuring IP Aliasing, Virtual Hosts with IPs, Multiple Instances of Apache, Example for name based virtual hosts, Example for IP based virtual hosts.

Creating Name Based and IP Based Virtual hosts in Apache

These free tools have been designed to validate and check the health of your public DNS servers.

Free Secondary DNS for your domains. If your looking for another DNS to put your domain in, this is for you. Providing additional secondary servers can greatly improve the reliability and accessibility of your domain. Should your primary DNS become unavailable due to network problems, your secondary DNS entries come into play, the more DNS servers you have, the greater the resilience to errors.

Here are the steps:

1. Locate named.conf and go to that folder.
2. Add DNS entries for your nameserver.

Edit the pri.yourname.com file for the domain you are adding nameservers for.
Add these two lines at the bottom of the file:
ns1 IN A 10.10.10.10 (replace with your nameserver IP)
ns2 IN A 10.10.10.10
By the way, you can host your website and nameservers on the same IP.

3. Reload the nameserver daemon.
   $ sudo /etc/init.d/bind9 reload
4. Ping the nameservers, and they should resolve to the correct IP.
   If they do not, edit /etc/resolv.conf and add the following line above all other lines beginning with “nameserver”, add:
   nameserver 127.0.0.1
5. Go to your registrar of your domain name, and register the nameservers to point to the your nameserver IP.

To keep the root hints file current, use the following command.

$ dig @a.root-servers.net . ns > db.cache

If you are running BIND 9, you have handy new tools to help maintain your nameserver files: named-checkconf and named-checkzone. These tools reside in /usr/sbin or /usr/local/sbin.

named-checkconf checks the configuration file for syntax errors.
$ /usr/sbin/named-checkconf zonename db.local
zone zonename/IN: loaded serial 1
OK

named-checkzone checks a zone file for syntax errors.
$ /usr/sbin/named-checkzone zonename pri.108.10.20.in-addr.arpa
zone zonename/IN: loaded serial 2004071902
OK


This how-to assumes a Debian-type Linux server. 

1)  Install BIND

$ sudo apt-get install bind9

2)  Run BIND chrooted.  For security reasons we want to run BIND chrooted so we have to do the following:

$ sudo /etc/init.d/bind9 stop

Edit the file /etc/default/bind9 so that the daemon will run as the unprivileged user bind, chrooted to /var/lib/named. Modify the line: OPTIONS=”-u bind” so that it reads OPTIONS=”-u bind -t /var/lib/named”:

$ sudo vi /etc/default/bind9

OPTIONS="-u bind -t /var/lib/named"
# Set RESOLVCONF=no to not run resolvconf

RESOLVCONF=yes

3)  Create the necessary directories under /var/lib:

$ sudo mkdir -p /var/lib/named/etc
$ sudo mkdir /var/lib/named/dev
$ sudo mkdir -p /var/lib/named/var/cache/bind
$ sudo mkdir -p /var/lib/named/var/run/bind/run

4)  Then move the config directory from /etc to /var/lib/named/etc:

$ sudo mv /etc/bind /var/lib/named/etc

5)  Create a symlink to the new config directory from the old location (to avoid problems when bind gets updated in the future):

$ sudo ln -s /var/lib/named/etc/bind /etc/bind

6)  Make null and random devices, and fix permissions of the directories:

$ sudo mknod /var/lib/named/dev/null c 1 3
$ sudo mknod /var/lib/named/dev/random c 1 8
$ sudo chmod 666 /var/lib/named/dev/null /var/lib/named/dev/random
$ sudo chown -R bind:bind /var/lib/named/var/*
$ sudo chown -R bind:bind /var/lib/named/etc/bind

7)  We need to modify /etc/default/syslogd so that we can still get important messages logged to the system logs. Modify the line: SYSLOGD=”" so that it reads: SYSLOGD=”-a /var/lib/named/dev/log”:

$ sudo vi /etc/default/syslogd

## Top configuration file for syslogd
##
# Full documentation of possible arguments are found in the manpage
# syslogd(8).
#
#
# For remote UDP logging use SYSLOGD="-r"
#
SYSLOGD="-a /var/lib/named/dev/log"

9)  Restart the logging daemon:

$ sudo /etc/init.d/sysklogd restart

10)  Start up BIND, and check /var/log/syslog for errors:

$ sudo /etc/init.d/bind9 start

A.  How to check if nameserver is valid

$ dig ns com
;; ANSWER SECTION:
com. 93009 IN NS a.gtld-servers.net.
com. 93009 IN NS b.gtld-servers.net.
com. 93009 IN NS c.gtld-servers.net.
com. 93009 IN NS d.gtld-servers.net.
com. 93009 IN NS e.gtld-servers.net.
com. 93009 IN NS f.gtld-servers.net.
com. 93009 IN NS g.gtld-servers.net.
com. 93009 IN NS h.gtld-servers.net.
com. 93009 IN NS i.gtld-servers.net.
com. 93009 IN NS j.gtld-servers.net.
com. 93009 IN NS k.gtld-servers.net.
com. 93009 IN NS l.gtld-servers.net.
com. 93009 IN NS m.gtld-servers.net.

$ host NS1.example.com i.gtld-servers.net
Using domain server:
Name: i.gtld-servers.net
Address: 192.10.10.10#53
Aliases:

NS1.example.com has address 69.10.10.180

If the nameserver is invalid, you will not have the last line above.

B.  To check nameserver configuration of a site, do this:

$ nslookup -q=any example.com