@height8 I probably should stop using them now that Cisco bought them :P

It was only a matter of time before I had to go somewhere again. A quick trip to DC. Image [www.instagram.com]

Really, Gig Harbor? Do we need to pave ALL our land? Image [www.instagram.com]

Hm.. I think I've narrowed it down to OpenDNS being the problematic resolver in this. My local nameserver forwards queries to a few different resolvers and the one that I can make return the bogus query is the OpenDNS one.

@height8 Sometimes I see this: Capture.PNG

@height8 What I'm seeing when I randomly query is that I occasionally get the old NS records back (which are not Cloudflare)

Can y'all look up phoneboy.org on your local DNS resolvers? If you get 67.210.225.171, please let me know (this is bad). Actually, let me know if you get something else too. :P

Hate when consumer router vendors can't deal with networking properly. It's perfectly valid to NOT use a WAN port and set a default route out the LAN port. ?

I have a rather large house and the access point has to be on the top floor at one end. The problem area is at the other end of the house on the bottom floor. ?

I've got this dead spot in my house I can't quite get covered. I suspect I will need to invest in a WiFi extender to cover that part of my house. ?