Dynamic DNS and IIS Web Servers
by Pierre Boisvenue. 24/04/2007
Part II
It seams a lot of websites have been created without an understanding of how web search engines such as google and yahoo works. Then, I you do not wish to have search engines Crawl your website then there is no to need read further however if you care please read on. The key word here is SEO witch stand for Search Engine Optimization, they are quite of a few books on the matter however being a hands on type of person I wanted to know more and this is when I stumbled upon a few documents that explain the meaning of HTTP return code 302 and 301.
You see, Domain Name Service provider offers a service for a little guy like me to be able to have my own web presence by providing URL forwarding to another PORT like HTTP port 8080 to circumvent the block instituted by my ISP via the standard HTTP port 80. This is where the interesting stuff in regards to SEO occurs. You see, various techniques are used in URL forwarding. One being masking that hides the redirection URL from the user’s web browser. The impact of this is that your web site will be showed in a frame and frames are known to not be SEO friendly. If you opt for not masking then your Domain Name service provider will likely return a HTTP code of 302 to search engines crawling your web site. HTTP Status 301 and 302 codes are legitimate code used in the Internet work to direct search engines and DNS services to your web site.
This has been a source of much confusion among web site designers and developers. My main concerned was would you has a web surfer reach my web site, hosted on my web server. So far the answer is yes and no. I have tried accessing my web site from work and no luck reaching the web site. But in other cases I can. I think it is a firewall issues from work where they clamp down hard HTTO port communication and are block port 8080.
From another PC, I could connect to the web site. I guess for casual web surfers my main target audience all will be fine?. Being on a Wi-Fi home based network for a reason I have yet to understand my local ip address, the one provided to my main Desktop PC being 192.168.2.3 before that 192.168.2.2, My virtual server on my firewall being set to 192.168.2.2 would not longer let my desktop PC act as a WEB server. I had to re program the router accordingly. For more technical detail please visit
Matt Cutts web site, Matt is a goggle insider with much more to say on the subject.
DNS, IIS
Comments view
Add Comments
: Name
: Email Address