Most of people face issue in using Google sites is redirection……i,e www.domain.com works fine (becoz of presence of cname record) BUT domain.com fails here……
SO lets see the possible ways out to the issue:
- use redirection offered by Registrar (eNom, Godaddy, name.com etc…)
- use redirection offered by third party dns hosts. (only redirection and NOT dns hosting)
In this post, i will consider #2 as for #1 instructions are already available (Google for them!) and also i guess most of you people are reading this post because you were unable to do the #1!
since we are using free services, they are perfect for blogger, small biz sites (having low traffic…i.e less then 10,000 visitors per day)
We can use any of following host for setting redirection:
here i like #1 the most as for redirection as its really fast and simple (though as dns host it is worst!)
and so i will be giving steps for setting up redirection only in everydns…..and anyone can easily use any other service….as steps will be quite similar…
To use its redirection, follow these steps:
- Get a free account at http://everydns.com
- now login and then add you domain as webhop….
i.e you need to add your-domain.com webhop to http://www.your-domain.com(look at pic. below)
- Now wait for 10-15mins…..
(so that a zone file is created for your domain on everydns)
- Now you need to get the ip of everydns redirection server……..which is running redirection script and will be doing redirection of your domain.
This can be done easily by doing an “A record” lookup for your domain on everydns nameservers…..
you can either simply use any dns lookup tool like e.g http://zoneedit.com/nslookup.htm here just
put your domain in first field, select record type – a in second fiend and put ns of everydns to which you want to query….so you can use ns1.everydns.net in 3rd
- so from here we get ip of server is – 220.127.116.11plz not if you get error like – no a records were found for domain.com on server ns1.everydns.net
Its just means that everydns server’s are ot hosting your domain yet…wait sometime to see that….
Incase you are on linux, just put up dig command with “a” and “@” parameters…..
so the command here as per this example will be
dig domain.com a @ns1.everydns.net
[anurag@root ~]$ dig domain.com a @ns1.everydns.net
; <<>> DiG 9.3.4-P1 <<>> domain.com a @ns1.everydns.net
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21777
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4
;; QUESTION SECTION:
;domain.com. IN A
;; ANSWER SECTION:
domain.com. 3600 IN A 18.104.22.168
;; AUTHORITY SECTION:
domain.com. 86400 IN NS ns1.everydns.net.
domain.com. 86400 IN NS ns2.everydns.net.
domain.com. 86400 IN NS ns3.everydns.net.
domain.com. 86400 IN NS ns4.everydns.net.
;; ADDITIONAL SECTION:
ns1.everydns.net. 7200 IN A 22.214.171.124
ns2.everydns.net. 7200 IN A 126.96.36.199
ns3.everydns.net. 7200 IN A 188.8.131.52
ns4.everydns.net. 7200 IN A 184.108.40.206
;; Query time: 35 msec
;; SERVER: 220.127.116.11#53(18.104.22.168)
;; WHEN: Sat Nov 29 01:08:52 2008
;; MSG SIZE rcvd: 192
- now just delete all A records present at your dns hosting for “domain.com”
- create new A record for domain.com (or root zone…or whatever your dns host calls it) pointing to 22.214.171.124
Hope that will help you in redirection setup 🙂