3 ms·
Yup. Amazon has 3 too! $ dig amazon.com ; <<>> DiG 9.7.0-P1 <<>> amazon.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcod
by joevandyk 15y ago
Yup. Amazon has 3 too!
$ dig amazon.com
; <<>> DiG 9.7.0-P1 <<>> amazon.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41998
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;amazon.com. IN A
;; ANSWER SECTION:
amazon.com. 36 IN A 72.21.194.1
amazon.com. 36 IN A 72.21.211.176
amazon.com. 36 IN A 72.21.214.128
- imbriaco 15y agoNot exactly. The 3 IPs that are returned for proxy.heroku.com are not fixed. They are a just subset of the available front-end proxy servers.
- 140am 15y agoExactly - its a common practice to use DNS servers to spread load across backend instances. Example djbdns/tinydns by default "only" returns up to 8 IP addresses so if you setup more then that those IPs will be randomly returned. http://cr.yp.to/djbdns/balance.html http://cr.yp.to/djbdns/balance.html