How to force IE8 to just open links in new tabs?

Whenever I click on a program link in Internet Explorer 8 it opens on a new window. It's so annoying! Is there any way for me to force IE8 to just open links in new tabs?

Follow these steps:

1. Click on Tools of Main Menu
2. Tools --> Internet Options
3. General
4. Settings
5. Tabs
6. Under 'Open Links from other programs..." choose 'A New Tab in Current Window'
7. OK

Continue Reading...

how to copy google sites to a different google app domain?

1. In domain1, share the site with a user of domain2 as owner of the site
2. In the gmail of the user@domain2, open the site, and be sure it's opened with the user@domain2
3. copy the site (because you are also owner). It will copy the site in the domain2 domain.

Continue Reading...

Block and redirect domains with dnsmasq

Reading the dnsmasq manpage I found the following:
A, --address=/<domain>/ [domain/] <ipaddr><br /> Specify an IP address to return for any host in the given<br /> domains. Queries in the domains are never forwarded and always<br /> replied to with the specified IP address which may be IPv4 or<br /> IPv6. To give both IPv4 and IPv6 addresses for a domain, use<br /> repeated -A flags. Note that /etc/hosts and DHCP leases over-<br /> ride this for individual names. A common use of this is to redi-<br /> rect the entire doubleclick.net domain to some friendly local<br /> web server to avoid banner ads. The domain specification works<br /> in the same was as for --server, with the additional facility<br /> that /#/ matches any domain. Thus --address=/#/1.2.3.4 will<br /> always return 1.2.3.4 for any query not answered from /etc/hosts<br /> or DHCP and not sent to an upstream nameserver by a more spe-<br /> cific --server directive."

This seemed to be exactly what I wanted. It redirects any server in a given domain to a specified ip address

sample of my /etc/dnsmasq.conf: (where 192.168.1.1 is the local webserver)
address="/ac.rnm.ca/192.168.1.1"<br />address="/accelerator-media.com/192.168.1.1"<br />address="/action.ientry.net/192.168.1.1"<br />address="/actionsplash.com/192.168.1.1"<br />address="/actualdeals.com/192.168.1.1"

I got this running from this source : http://www.debian-administration.org/articles/535

Continue Reading...

url redirect codes

Below are a Couple of methods to implement URL Redirection

IIS Redirect

In internet services manager, right click on the file or folder you wish to redirect
Select the radio titled "a redirection to a URL".
Enter the redirection page
Check "The exact url entered above" and the "A permanent redirection for this resource"
Click on 'Apply'

ColdFusion Redirect
<br /><.cfheader statuscode="301" statustext="Moved permanently"><br /><.cfheader name="Location" value="http://www.new-url.com">

PHP Redirect
<?<br />Header( "HTTP/1.1 301 Moved Permanently" ); <br />Header( "Location: http://www.new-url.com" ); <br />?>

ASP Redirect
<br /><%@ Language=VBScript %><br /><%<br />Response.Status="301 Moved Permanently"<br />Response.AddHeader "Location","http://www.new-url.com/"<br />%>

ASP .NET Redirect
<script runat="server"><br />private void Page_Load(object sender, System.EventArgs e)<br />{<br />Response.Status = "301 Moved Permanently";<br />Response.AddHeader("Location","http://www.new-url.com");<br />}<br /></script>

JSP (Java) Redirect
<br /><%<br />response.setStatus(301);<br />response.setHeader( "Location", "http://www.new-url.com/" );<br />response.setHeader( "Connection", "close" );<br />%>

CGI PERL Redirect
$q = new CGI;<br />print $q->redirect("http://www.new-url.com/");

Ruby on Rails Redirect
def old_action<br />headers["Status"] = "301 Moved Permanently"<br />redirect_to "http://www.new-url.com/"<br />end

Redirect Old domain to New domain (htaccess redirect)

Create a .htaccess file with the below code, it will ensure that all your directories and pages of your old domain will get correctly redirected to your new domain.
The .htaccess file needs to be placed in the root directory of your old website (i.e the same directory where your index file is placed)

Options +FollowSymLinks
RewriteEngine on
RewriteRule (.*) http://www.newdomain.com/$1 [R=301,L]

Please REPLACE www.newdomain.com in the above code with your actual domain name.

In addition to the redirect I would suggest that you contact every backlinking site to modify their backlink to point to your new website.

Note* This .htaccess method of redirection works ONLY on Linux servers having the Apache Mod-Rewrite moduled enabled.


Redirect to www (htaccess redirect)

Create a .htaccess file with the below code, it will ensure that all requests coming in to domain.com will get redirected to www.domain.com
The .htaccess file needs to be placed in the root directory of your old website (i.e the same directory where your index file is placed)

Options +FollowSymlinks
RewriteEngine on
rewritecond %{http_host} ^domain.com [nc]
rewriterule ^(.*)$ http://www.domain.com/$1 [r=301,nc]

Please REPLACE domain.com and www.newdomain.com with your actual domain name.

Note* This .htaccess method of redirection works ONLY on Linux servers having the Apache Mod-Rewrite moduled enabled.

Continue Reading...

Setup bind to resolve local dns request and not recursive

So, I want to allow programs on my server to ask my copy of BIND to perform recursive queries, but I don’t want it performing them for anyone else. How did I configure that? It’s very simple–it only takes a line in each of two configuration files. First, my resolv.conf file contains this line:

nameserver 127.0.0.1

That means that programs on my server should send DNS queries to the DNS server at IP address 127.0.0.1 (which as you may know is the “localhost” address–on every computer, it’s an IP address used by that computer). That line was already there, so I didn’t have to change that.

Second, I added one line to named.conf. The “allow-recursion” line in the “options” section specifies which IP addresses can request recursive queries from this server.

options {
allow-recursion { 127.0.0.1/32; };
// etc.
};

This means that recursive DNS requests coming from 127.0.0.1 (with all 32 bits being significant) are allowed. All other recursive requests are blocked.

Continue Reading...