Wednesday, 28 November 2012

Grant To Start Business - DNS Propagation Explained - or Why You Have to Wait the 72 Hours


Or had a professional design firm create a web site for you, paid for hosting (leasing space to store all the files that will be publicly accessed as web pages) with a WHP - aka Web Hosting Provider (such as bsleek.com) and even uploaded your website to the WHP's servers, figured out how to register it, so you found a perfect domain name that was not already taken.

And what is this "propagation" nonsense those techies are trying to bamboozle you with? Is it that nobody really cares about customer service anymore? ! That went pretty fast, when they took your credit card payment, hey! ? Is't this the promise of the e-commerce age, why can't you see your website instantly - after all? Of your money spending and of the headaches you got from trying to make sense of all the technobabble were in vain, it looks like the results of your hard work, alas?

? Did you make a big mistake chosing it? Is your new Web Host Provider a lemon?

Wait. . . . And why is it that the only thing we can do to speed the process up is, how it works, what DNS propagation is, by telling you in plain English, i will try to demistify the DNS propagation process, over the next few paragraphs. Unless you understand exactly how things work, all this has to be very frustrating.

) Etc, a text document, whether a web page, we call a computer a server when that machine is up and running and providing a service ("serving" something. Your beloved computer can be a server too. That's right! Like the one you are using now to read this, think of a server as a regular computer. Another article written in technicalese language", i know the word Server is intimidating and you are thinking "oh sure. DNS stands for Domain Name Server.

The strangest things can happen that would lead you to believe that your new web hosting provider is at fault. Especially when first registering a domain name or transferring your website to a web hosting provider, i will tell you that DNS can be tricky, with the language barier lowered.

99.99% of the time the Web Hosting Provider is not to blame and I will explain why.

Things will look much brighter, once you understand how things work, like everything else in life, again. But it has to be done, sorry. There are a number of things involved in DNS that I will familiarize you with.

Things you need to hear about are:

- IP Addresses

- Service Providers

- Domain Names

- Domain Name Registrars

- DNS

- The Propagation Process

IP Addresses 1.

It all boils down to an address or what we call an "IP Address", when one computer wants to speak to another computer. Our computers talk to each other by identifying themselves using numerical addresses much like the address on your home or for your telephone.

Here is an example: 64.247.43.26

They are the assigned numbers authority and they control who gets IP addresses in the US. The American Registry for Internet Numbers, iP addresses in the United States are assigned by ARIN. Service providers (see below) receive thousands of IP addresses to be used on their networks, here's a piece of trivia for all interested in cool facts: Typically. . . . Is actually limited and we are almost on the verge of exhausting all the numbers, while immense to the untrained eye, the number of possible addresses, as you would imagine.

Service Providers 2.

The service providers will use IP addresses to identify their network equipment so that they can conduct business on the internet.

I will only discuss two of them, there are many different types of service providers but for the purpose of this article.

This IP address will be used to identify your computer while you are connected to the internet. They will assign your computer one of their IP addresses, when you connect to your ISP. You would not be able to send email or surf the world wide web, without them. The ISP (or Internet Service Provider) is the company that provides you with access to the internet.

The WHP has already assigned this server one of their IP addresses. It is placed on a special computer known as a server that is connected to the internet via a high-speed connection, when the website is published. Such as bsleek.com) is a company that provides a means for individuals or businesses to publish a website on the internet, the WHP (or Web Host Provider.

Let's summarize what we have learned so far by looking at a typical internet users experience: now,

You then open up your web browser and type in your website's domain name: yourdomain.com. Etc) from your ISP, a license plate, you connect to the internet and your computer gets an IP address (much like a phone number. Let's say that you want to surf your newly published website.

It finally arrives at your WHP's web server because it contains the IP address of the computer you are looking for, after traveling several thousand miles in just a few milliseconds. Across wires and beamed to satellites and back down to Earth again, that request is blasted across the internet jumping through routers and gateways. Your computer sends a request. Then you hit enter.

You are now looking at your published home page in merely a few seconds and being proud of the pretty colors you picked for your menu buttons. The server then responds by sending a copy of the website's home page back to your computer because it knows the IP address of the computer that made the request.

Read on: How did this all happen?

Domain Names. 3.

We also use them when sending email. A domain name is what you typically enter into your web browser when you want to visit a website.

Website: http://www.yourdomain.com / Email: user@yourdomain.com

It is easy to remember the name of a friend's website or a company that you like to shop with rather than trying to remember a number like: 64.247.43.26 Domain names provide a fast and convenient way of reaching our favorite websites and sending email to each other.

. . . Suspense. IP addresses into domain names) and vice versa, the mechanism that translates numbers into names (that is. What are we missing here?

Domain Name Registrar 4.

The registrar is more or less at the top of the whole naming scheme chain. The domain registrar has tools that allow you to search for and register an available domain of your choosing. If you want to have your own domain name you will need to register one through a company called a Domain Name Registrar.

Which is the topic you came here to read about in the first place, dNS. . . I will talk about, as a reward for reading this much of my article, and now. Congratulations - you ar a very determined individual, if you were able to read this far and even stay focus.

DNS 5.

DNS serves two primary functions: DNS is a software program that runs on a dedicated computer known as a DNS server.

1) To translate domain names into IP addresses.

) When your computer needs to know the IP address for yourdomain.com it asks a DNS server (usually the one provided by your ISP. DNS servers make translating or "Resolving" this information fast and seamless. It's much easier to remember a domain like mydomain.com than a sixteen digit number like 64.247.43.26.

2) To act as authority for designated domain names.

Technically this is known as an "A" record for "Authority". These servers will act as the authority for your domain name because your network provider will put a special entry in their DNS server as it relates to your domain name that says: YOU ARE HERE! It is an industry-wide standard to have at least two DNS servers or more, in fact. The network you are on must have its own DNS servers, wherever you decide to host your website.

And a few pointers to find the rest; they only hold the names that they are responsible for, keep in mind that no single DNS server holds all the domain names for the internet. They ARE the yellow pages of the internet and they contain information about your domain name. There are literally hundreds of thousands of these DNS machines world wide.

Remember the "A" record? The server that is responsible for a particular domain is called the "Authority", technically. Many DNS servers do both. Some DNS servers strictly store names while others are doing the work of providing lookup services for computers that need to look up names.

The 'A' record (or your WHP's DNS servers), in this article I will focus only on the domain name, for the purposes of not altering your sanity. In it you can find a variety of other pieces of information (or records) about your domain name. This information as a whole is known as your "DNS Record". There are a few pieces of crucial information stored in a DNS server with regard to your domain name.

The Propagation Process 6.

It is placed into a directory that is broadcast out to primary DNS servers around the world, when it is published. Your domain registrar is the one responsible for publishing your domain name at the very first (called root) DNS level, as I said before.

The primary DNS servers broadcast out to secondary DNS servers and so on and so forth.

Or that the authority for that domain has changed, a domain name has been changed, propagation refers to the amount of time it takes for all the DNS servers everywhere around the world to recognize the fact that either a new domain is being registered. This process is known as propagation and it can take upwards of 72 hours to complete.

When or why one DNS server will receive updated information before another is a complete mystery - really! DNS servers are always updating themselves and changing dynamically during the course of any given day. Other reasons why it takes so long is obviously the size of our planet and the total number of DNS servers that require updated information.

Anywhere on the internet should be able to visit your hosted website, anyone, once propagation is complete. Your DNS propagation will complete well within the 72 hour period but you can't be sure that everything is fine until you wait out the 72 hours, in most cases!

Only one of your ISP's DNS servers might receive the update regarding your domain name and the other might not, 24 hours after making your nameserver changes, well, they use two DNS servers. Take your ISP for example. Knows about your domain name, this is because not every DNS server that needs to know. During that time you may experience strange occurrences.

The next it is not, one moment it is there. What you will experience would be as though your website was going up and down, if only one of these servers can resolve your domain to an IP address and the other can not.

Here is another example:

Ouch! Where your ISP's DNS servers can not.and wait another 72 hours, this is most likely because his ISP's DNS servers are able to get the information at that time. A friend of yours can see your new website and you can not.

Here is a neat one:

They appear and then vanish or they don't appear at all, but you notice that when trying to view your most recent changes. During propagation you are working on development of some pages in your website. You are transferring your hosting to a new WHP.

What you really need to do is WAIT OUT THE 72 HOURS! This can be a weird experience and may take some time to figure out. One server has information about your OLD WHP and the other has information about your NEW WHP! Think about the load-balancing DNS servers again.

They are potentially browsing your site from two different WHPs, they won't realize that you are in a state of propagation and that from one minute to the next. They are just browsing your website, they won't know that you have switched WHP's because as far as they can tell. You will always have a consistent functional website available to your visitors, if you avoid making changes to your website during a transfer/propagation period, you see.

After which these and other similar problems will have vanished, the problem is that the domain owner has not let 72 hours pass by. In reality the server is fine and your WSP is one of the finest. All of these occurrences are very common and each one of them will result in a phone call to the WHP asking why the server is going up and down.

You just must have patience and wait the full three days before you can try to determine if your website is experiencing a problem or not, your Web Service Provider is not at fault, so as you can see.

No comments:

Post a Comment