 |
 |
 |
|
DNS
Dude, DNS does NOT PROPAGATE. DNS is decentralized except for one tiny part. Each domain name is listed in all of the top-level name servers, of which there are a bunch named by letter (a, b, c, etc.). When someone, somewhere on the Net wants searls.com, their stub DNS resolver connects with the DNS server in their TCP/IP config. That DNS server queries the top-level nameservers (updated at least daily, if not more often, from information provided by registrars). The top-level nameservers provide the SOA (start of authority) info, which tells that querying DNS server which DNS server on the Internet "knows" all the details for that domain name. This happens for each query, except that local DNS servers cache information for anywhere from a few minutes to weeks, depending on the domain that's requested's settings (your local DNS server can override this). So it's the reverse of propagadation. It's more like reverse percolation: all the cached values must time out at places like Earthlink, AOL, etc., for your domain to reappear. Your information is correct on your DNS server and in the top-level name servers. They're just not consulted until the expiry. There are responses to this message:
|
