4 ms·
>the company's main domain was not architected to process the enormous traffic I understand all the sarcasm expressed here, but this actually may be true if th
by ComodoHacker 9y ago
>the company's main domain was not architected to process the enormous traffic
I understand all the sarcasm expressed here, but this actually may be true if they run their own DNS service. Subdomain isn't a solution in this case, but separate domain is.
- Xylakant 9y agoI fail to see why DNS would be an issue. Set a sufficiently large TTL and you should see almost no queries hit your DNS servers once intermediate caches have seen the domain.
- ComodoHacker 9y agoWith this amount of traffic you have to load-balance, so you can't just set large TTL.
- azinman2 9y agoBut load balancing also applies to their new domain as well. Why would you need a separate hostname?
- Xylakant 9y agoLook, you could just set the new subdomain as a cname with a large TTL and then handle that a-record via a different provider if you really need to. You could also choose to delegate the whole subdomain. Also, load-balancing via multiple a-records does not at all depend on the TTL. DNS is really the easiest part to handle here. Internal policy might prevent delegation, but that’s not a technical problem.
- ComodoHacker 9y agoHow can I handle a subdomain with a different provider while handling the whole zone myself? I'm not an expert in DNS, so really curious.
- Xylakant 9y agoSet an NS record for the subdomain on the parent domain.
- ComodoHacker 9y agoIs it cached the same as A records?
- Xylakant 9y agoIt’s cached according to the TTL you assign it, though it would be common to give it a high TTL.
- speedplane 9y agoIf true, it begs a question as to why. Why does equifax need to be a DNS expert? There are so many inexpensive DNS solutions that work for huge sites... far cheaper than hiring one developer.