11 {{ upvoteCount | shortNum }}
11 {{ upvoteCount | shortNum }}

DNS question

by Nutrifitness
9 replies
hi
I just changed dns for 1 of my websites and it is already visible in IE ...but I went to AOL browser and it's the old site.....now this should clear up by tomorrow(24 hours correct?)
I found it weird that I could refresh in IE and it came up but even after re booting not so in AOL..weird or not?
#dns #question
  • Profile picture of the author Kevin Birch
    Originally Posted by Nutrifitness View Post

    hi
    I just changed dns for 1 of my websites and it is already visible in IE ...but I went to AOL browser and it's the old site.....now this should clear up by tomorrow(24 hours correct?)
    I found it weird that I could refresh in IE and it came up but even after re booting not so in AOL..weird or not?
    Very strange - don't know how often AOL refreshes its cache - you'll probably find that it happens overnight.
    Signature
    {{ DiscussionBoard.errors[1816950].message }}
  • Profile picture of the author George Wright
    It's probably cached in your aol browser on your PC. Clear the cache. My experience has always been that it shows up in AOL first.

    George Wright
    Signature
    "The first chapter sells the book; the last chapter sells the next book." Mickey Spillane
    {{ DiscussionBoard.errors[1816954].message }}
  • Profile picture of the author bigdaddy99
    Usually dns updates take from 8 to 24 hours. I'm sure that aol has its' own dns servers that are not tied directly to your local isp, which are probably the dns servers you are using. So it will take a while for AOL to get the update.

    You could also try google dns servers at 8.8.4.4 or opendns server at 208.67.222.222

    Both google and opendns have secondary servers too if you want to use both of them.

    I prefer google cuz opendns redirects to their search.

    Bottom line - give it time -you'll be fine - wow such a rhyme!

    hth

    bd99
    {{ DiscussionBoard.errors[1816969].message }}
  • Profile picture of the author seasoned
    It is NOT strange AT ALL! I recently mentioned in another thread about TTL. Unless EVERY visitor, hardcodes it in their hosts file, one HAS to hit a DNS server! Since you can't hit THE .COM DNS server, 1 for approximately every 538,461,538 people on the planet, so that would be just TOO MUCH traffic, you have to hit a COPY! AOL uses AOLs server, and I bet no other ISP does, so you used two different servers. If the TTL is set say 604800, it could take a WEEK to refresh the cache. Most of my sites are set to 14400 which is 4 hours, and that is BEFORE verisign sees it.

    Steve
    {{ DiscussionBoard.errors[1821687].message }}
    • Profile picture of the author Nutrifitness
      Originally Posted by seasoned View Post

      It is NOT strange AT ALL! I recently mentioned in another thread about TTL. Unless EVERY visitor, hardcodes it in their hosts file, one HAS to hit a DNS server! Since you can't hit THE .COM DNS server, 1 for approximately every 538,461,538 people on the planet, so that would be just TOO MUCH traffic, you have to hit a COPY! AOL uses AOLs server, and I bet no other ISP does, so you used two different servers. If the TTL is set say 604800, it could take a WEEK to refresh the cache. Most of my sites are set to 14400 which is 4 hours, and that is BEFORE verisign sees it.

      Steve
      well I understood most of what your saying.....lol is there really anything I can do about that or is it out of my control....as I said I had no problem on my aol software today ..I thought my business partner was nuts but I guess not..
      I never heard of this before...I just would change dns settings and done.
      Signature

      Georgette Pann
      http://thefitnessbootcamp.com
      http://fitnessbootcampworkout.com
      http://fitnessbusinessapps.com -new

      {{ DiscussionBoard.errors[1821727].message }}
      • Profile picture of the author seasoned
        Originally Posted by Nutrifitness View Post

        well I understood most of what your saying.....lol is there really anything I can do about that or is it out of my control....as I said I had no problem on my aol software today ..I thought my business partner was nuts but I guess not..
        I never heard of this before...I just would change dns settings and done.
        It never really comes into play unless someone tries to go to that domain before you do, uses a DNS server you will use, and the cache hasn't expired. Of course, if YOU have control of your domain name server, you can maybe speed things up a little by making THAT TTL smaller. Just be aware that larger numbers mean things may run faster because you won't get as many DNS requests. So there IS a tradeoff.

        The following page was used as a second example ONLY because it was the first site that popped up on google that I thought explained it well:

        DNS TTL (an acronym for Time To Live)

        As it says:

        By specifying TTL settings for a particular domain's DNS records, webmasters define the frequency of website content updates. The longer the TTL value is, the faster[they MEAN slower or longer, but the rest of the message makes that clear.] the domain resolution time periods will be. The TTL value can be set from one to several hours, if you are not planning any changes to your domain's DNS records in the meantime. If you need to make such changes, you will have to decrease the TTL value entry to several minutes to avoid any outdated data on your website.
        they give examples of:

        $TTL 86400 <<<- the old, and more popular standard meaning 1 day 24(hours)*60(minutes)*60(seconds)
        $TTL 1440m
        $TTL 24h
        $TTL 1d


        So you can see I'm not making this up.

        Steve
        {{ DiscussionBoard.errors[1825103].message }}
        • Profile picture of the author Nutrifitness
          Originally Posted by seasoned View Post

          It never really comes into play unless someone tries to go to that domain before you do, uses a DNS server you will use, and the cache hasn't expired. Of course, if YOU have control of your domain name server, you can maybe speed things up a little by making THAT TTL smaller. Just be aware that larger numbers mean things may run faster because you won't get as many DNS requests. So there IS a tradeoff.

          The following page was used as a second example ONLY because it was the first site that popped up on google that I thought explained it well:

          DNS TTL (an acronym for Time To Live)

          As it says:



          they give examples of:

          86400 <<<- the old, and more popular standard meaning 1 day 24(hours)*60(minutes)*60(seconds)
          1440m
          24h
          1d


          So you can see I'm not making this up.

          Steve
          I believe you.. I just never experienced this and from my end all I can do is change DNS to point to my hostgator host...istead of other hosting company where the old site was
          hmm..I just thought of something ..do you think that could be part of the problem?
          Signature

          Georgette Pann
          http://thefitnessbootcamp.com
          http://fitnessbootcampworkout.com
          http://fitnessbusinessapps.com -new

          {{ DiscussionBoard.errors[1825991].message }}

Trending Topics