DNS updates will take < 5 minutes to propagate, vs. 48 hours
Collapse
X
-
except for all the ISP dns proxies that cache info for 24 hours or more, and ignore dns settings.
Plus... I believe this will just effect new and changed dns zone loading for domains registered thru verisign. -
Originally posted by decostopexcept for all the ISP dns proxies that cache info for 24 hours or more, and ignore dns settings.
Plus... I believe this will just effect new and changed dns zone loading for domains registered thru verisign.
From their FAQ:
How long will it take from when I register a domain or make a change to an existing domain on my registrar's web site until I see the change in DNS?
It depends on how the registrar's systems work and how long it takes the registrar to communicate your request to the .com/.net registry. Once the registrar successfully submits a command to the .com/.net registry, the new domain or changes to an existing domain should be visible in DNS on average within five minutes.Comment
-
You would think buy now verisign could provide an "update list" so that ISPs can download that update evey 5 minutes and update their cache. Perhaps verisign do but isps don't use it, no idea.Comment
-
You can get updates from the root server if you configure the dns server properly. You should only update every 20 minutes as a courtesy.Comment
Related Topics
Collapse
-
When will vbulletin update my site from 5.24 to 5.25?
-
Channel: vB Cloud Support & Troubleshooting.
-
Comment