You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
So global DNS worked fine, but my internal stuff (LAN domain and some stuff I forward for staging/testing environments) would randomly fail to resolve or resolve to the wrong IP via public nameservers (for some it's split DNS) when the query got sent to the OpenWRT box.
And of course, since positive replies get cached by the local dnsmasq (managed by NetworkManager), it would usually work on the second try and stick for a while so it wasn't *too* obvious.
I think this started when I turned that feature on (needed for split DNS with VPNs), because IIRC by default dnsmasq has different behavior from the system resolver (round robin / random instead of trying in order) - previously rogue would probably wind up third and get no hits.
I should document my home networking setup sometime. Physically it's super simple (VDSL modem, Netgear router/AP, extra switch, 4 computers and some game consoles) but logically there's 9 VLANs, 7 SSIDs, 3 network namespaces, multiple VPNs, IPSec between some hosts, ...
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
