I Am just GLAD to KNOW it wasnt just Me even though I spent $30 on Software to Find out LOL 
I have been having the problem for the last Mo or so But since the upgrade I haven't had NEAR as many problems
Trouble getting online with American Beagler?
Moderators: Pike Ridge Beagles, Aaron Bartlett
Re: Trouble getting online with American Beagler?
Wheww I Am just GLAD to KNOW it wasnt just Me even though I spent $30 on Software to Find out LOL
I have been having the problem for the last Mo or so But since the upgrade I haven't had NEAR as many problems
I Am just GLAD to KNOW it wasnt just Me even though I spent $30 on Software to Find out LOL I have been having the problem for the last Mo or so But since the upgrade I haven't had NEAR as many problems
From Field to Show and Show to Field the way it should be
Re: Trouble getting online with American Beagler?
Who is everyone's internet provider? The people I know in my area who has had problems provider is Windstream. I have problems at home but never on other computers where Windstream is not the provider.
Re: Trouble getting online with American Beagler?
jdmart, Windstream is my provider too. Maybe they are the problem!
-
goodpickens
- Posts: 407
- Joined: Wed Oct 13, 2010 10:41 pm
- Location: Doniphan, MO
Re: Trouble getting online with American Beagler?
We have windstream, too. Maybe it is them.
-
Mo. Beagler 5000
- Posts: 1272
- Joined: Wed Jun 11, 2008 8:32 pm
- Location: Warrrensburg, Mo
Re: Trouble getting online with American Beagler?
No I have a school network and centurytel and it does it on both of them....
God isn't real, Beer is good and people are crazy, there I fixed it.
Re: Trouble getting online with American Beagler?
Apparently Windstream takes about 72 hours to update their servers. Any changes made by other servers won't be recognized by Windstream for at least that long. They are horrible about that, and if you call them on it they say it's the other providers. Like they are more on it than Go-Daddy? When they can buy a SuperBowl ad I'll believe that. I have more problems with them on the eSPO board because a few regulars there have Windstream and these are some of the things they've been told. I would imagine some of the smaller providers would be the same way.
Here's the long version of why that happens:
What is DNS caching?
All Internet hosts, including your computer when it is connected to the Internet, use a DNS Server. Every time you go to a website, you need to look up the site's IP address using the domain name of the website. Your request for this lookup is eventually passed to a DNS Server somewhere.
But your request is one of thousands, even millions of requests being made at any one time across the Internet. The DNS lookup process requires that if your local DNS Server is not Authoritative for the domain that contains the domain name you are trying to reach, it should ask other Servers to get an answer. Your local Server could get quite busy performing these lookup requests, and this could slow down its performance if it is Authoritative for a domain name.
To combat this the answers that a DNS Server gets from another DNS Server can be added to their own internal Database and retained for a period of time equal to the time to live (ttl) value set on the record stored on the Authoritative DNS Server.
Storing these responses is called Caching, and allows a DNS Server to respond more quickly to multiple queries for the same domain or host. If you are on a website, and want to retrieve the next page on the site, the local DNS Server does not have to look up the host again, provided the time to live (ttl) value has not expired and caused the local DNS Server to delete the information. This is why it takes so long to contact a website at first, but subsequent requests for pages on the same site are somewhat faster.
Caching DNS Servers are configured for recursive lookup as well. This creates a Server that will respond to lookup requests by delivering answers from its cache, or looking them up on other Servers. It is the job of a Caching DNS Server to handle general lookups of Internet domains. A Caching DNS Server reduces the load placed on an Authoritative DNS Server by handling the requests that don not pertain to the local domain.
Almost all Internet Service Providers (ISPs) operate some kind of Caching DNS Server.
Unfortunately DNS Caching is a double-edged sword. It speeds up resolution by storing recent answers, and short-circuiting the normal resolution process. However there is a down side. Because DNS Servers cache answers, and don't delete these answers until the time to live (ttl) expires, it can take hours or days for the entire Internet to recognize changes to DNS information for your domain name.
How often do ISP's update their DNS Caches?
Every ISP (Internet service provider) and web hosting company operates a Domain Name Service. The DNS server translates the Domain Name into a numerical value that the computers on the Internet recognize. The DNS server saves or caches previous translations so that later requests can be handled much more quickly (the name server reads the stored information and does not have to perform a translation/search each time the name is resolved).
The cache of every DNS server is deleted periodically. The length of time between purges is different for everyone though most hosts/ISPs clear DNS cache every 7 to 10 days (some more frequently some less frequently). This means that if your domain is moved or transferred it may take up to 10 days for everyone on the Internet to see the changes. We have no control over how ISP's cache DNS information
Source:
http://www.maintainaweb.com/faq.asp
Here's the long version of why that happens:
What is DNS caching?
All Internet hosts, including your computer when it is connected to the Internet, use a DNS Server. Every time you go to a website, you need to look up the site's IP address using the domain name of the website. Your request for this lookup is eventually passed to a DNS Server somewhere.
But your request is one of thousands, even millions of requests being made at any one time across the Internet. The DNS lookup process requires that if your local DNS Server is not Authoritative for the domain that contains the domain name you are trying to reach, it should ask other Servers to get an answer. Your local Server could get quite busy performing these lookup requests, and this could slow down its performance if it is Authoritative for a domain name.
To combat this the answers that a DNS Server gets from another DNS Server can be added to their own internal Database and retained for a period of time equal to the time to live (ttl) value set on the record stored on the Authoritative DNS Server.
Storing these responses is called Caching, and allows a DNS Server to respond more quickly to multiple queries for the same domain or host. If you are on a website, and want to retrieve the next page on the site, the local DNS Server does not have to look up the host again, provided the time to live (ttl) value has not expired and caused the local DNS Server to delete the information. This is why it takes so long to contact a website at first, but subsequent requests for pages on the same site are somewhat faster.
Caching DNS Servers are configured for recursive lookup as well. This creates a Server that will respond to lookup requests by delivering answers from its cache, or looking them up on other Servers. It is the job of a Caching DNS Server to handle general lookups of Internet domains. A Caching DNS Server reduces the load placed on an Authoritative DNS Server by handling the requests that don not pertain to the local domain.
Almost all Internet Service Providers (ISPs) operate some kind of Caching DNS Server.
Unfortunately DNS Caching is a double-edged sword. It speeds up resolution by storing recent answers, and short-circuiting the normal resolution process. However there is a down side. Because DNS Servers cache answers, and don't delete these answers until the time to live (ttl) expires, it can take hours or days for the entire Internet to recognize changes to DNS information for your domain name.
How often do ISP's update their DNS Caches?
Every ISP (Internet service provider) and web hosting company operates a Domain Name Service. The DNS server translates the Domain Name into a numerical value that the computers on the Internet recognize. The DNS server saves or caches previous translations so that later requests can be handled much more quickly (the name server reads the stored information and does not have to perform a translation/search each time the name is resolved).
The cache of every DNS server is deleted periodically. The length of time between purges is different for everyone though most hosts/ISPs clear DNS cache every 7 to 10 days (some more frequently some less frequently). This means that if your domain is moved or transferred it may take up to 10 days for everyone on the Internet to see the changes. We have no control over how ISP's cache DNS information
Source:
http://www.maintainaweb.com/faq.asp