4 ms·
Rest of the .google pages (like a.google) show the nginx start page. Sounds like a last minute idea to host com.google. Even com.google uses an iframe with src
by 1234567890123 12y ago
Rest of the .google pages (like a.google) show the nginx start page. Sounds like a last minute idea to host com.google. Even com.google uses an iframe with src google.com?igu=2
- JosephRedfern 12y agoThat's because *.google points to 127.0.53.53, aka your loopback device - so the nginx start page is coming from your machine! ➜ ~ dig a a.google ; <<>> DiG 9.8.3-P1 <<>> a a.google ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32515 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;a.google. IN A ;; ANSWER SECTION: a.google. 600 IN A 127.0.53.53 ;; Query time: 31 msec ;; SERVER: 192.168.1.254#53(192.168.1.254) ;; WHEN: Wed Apr 1 12:34:27 2015 ;; MSG SIZE rcvd: 42
- TazeTSchnitzel 12y agoOh, it's a loopback domain? Did they register it for the same reason as .dev, purely to avoid reconfiguring their Intranet? :/
- 0x006A 12y agothey all resolve to 127.0.53.53 that nginx start page is your localhost