You are using two different names there, ie: mail-wm0-f46.google.com and mail-wg0-f46.google.com. It looks like the wg address used to map to the same IP.
It looks like we turned down one cluster and turned up another, and moved the IPs across. It's possible there was some overlap between the turn down and turn up, so maybe we were serving the IPs out of both, and now the wg address is gone since that cluster is down. Brandon On Tue, Nov 10, 2015 at 11:48 AM, Matthias Leisi <matth...@leisi.net> wrote: > Two of Google’s IPs do resolve from some sources, but not from others: > > 74.125.82.46 and 74.125.82.54 resolve to mail-wm0-f46.google.com and > mail-wm0-f54.google.com, but those two names only resolve back to the IPs > from some places. The status is NXDOMAIN, not some REFUSED/SERVFAIL. > > From server 1: > > matthias@trillian:~$ dig -t any mail-wg0-f46.google.com > > ; <<>> DiG 9.8.1-P1 <<>> -t any mail-wg0-f46.google.com > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16768 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;mail-wg0-f46.google.com. IN ANY > > ;; AUTHORITY SECTION: > google.com. 42 IN SOA ns3.google.com. > dns-admin.google.com. 107500025 900 900 1800 60 > > ;; Query time: 0 msec > ;; SERVER: 2001:8a8:4806::178#53(2001:8a8:4806::178) > ;; WHEN: Tue Nov 10 20:45:41 2015 > ;; MSG SIZE rcvd: 91 > > From server 2 (where it did not work a couple of days previously): > > root@db ~ # dig -t any mail-wm0-f46.google.com > > ; <<>> DiG 9.9.5-3-Ubuntu <<>> -t any mail-wm0-f46.google.com > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63472 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 5 > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags:; udp: 4096 > ;; QUESTION SECTION: > ;mail-wm0-f46.google.com. IN ANY > > ;; ANSWER SECTION: > mail-wm0-f46.google.com. 86299 IN A 74.125.82.46 > > ;; AUTHORITY SECTION: > google.com. 132863 IN NS ns1.google.com. > google.com. 132863 IN NS ns3.google.com. > google.com. 132863 IN NS ns2.google.com. > google.com. 132863 IN NS ns4.google.com. > > ;; ADDITIONAL SECTION: > ns1.google.com. 134452 IN A 216.239.32.10 > ns2.google.com. 134452 IN A 216.239.34.10 > ns3.google.com. 134452 IN A 216.239.36.10 > ns4.google.com. 134452 IN A 216.239.38.10 > > ;; Query time: 0 msec > ;; SERVER: 127.0.0.1#53(127.0.0.1) > ;; WHEN: Tue Nov 10 20:45:40 CET 2015 > ;; MSG SIZE rcvd: 204 > > Anybody else noticing inconsistencies? > > Note: Even though I noticed this on dnswl.org servers, the behaviour > seems to be erratic also on completely non-dnswl.org-related machines. > > — Matthias > > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > http://chilli.nosignal.org/mailman/listinfo/mailop > >
_______________________________________________ mailop mailing list mailop@mailop.org http://chilli.nosignal.org/mailman/listinfo/mailop
