Recent content by viperk1

Thanks so much! At least we've got to the bottom of this. So unless I upgrade to a new router, this is the behaviour I have to work with.

Hi Merlin, so the command nslookup ca.secureconnect.me 1.1.1.1 works as expected for you? I'm stumped. Was that on the latest stable firmware? I'm running 384.13.

I tried again with OpenDNS servers and it works!!! Guess this is my workaround for now until firmware behaviour (or DNS provider behaviour) changes. admin@RT-AC1900P-5F90:/tmp/home/root# nslookup ca.secureconnect.me 208.67.222.222 Server: 208.67.222.222 Address 1: 208.67.222.222...

Unfortunately, the behaviour is the same with my ISP DNS. s@tanuki:~$ nslookup ca.secureconnect.me 64.71.255.198 ;; Truncated, retrying in TCP mode. Server: 64.71.255.198 Address: 64.71.255.198#53 Non-authoritative answer: Name: ca.secureconnect.me Address: 162.253.131.66...

Hmm, thanks for that insight! I've actually only tried with google and cloudflare since those are the only ones I've ever used. Let me check with my ISP ones. Strange that they act that way though. I wonder who is operating according to spec (or if both behaviours are allowed).

Hey guys, I've scoured the internet for the past week and have not been able to find anything about this. Based on what I'm seeing, if there's ever a DNS query that has a response that's bigger than the UDP packet size which means a switch to TCP is required, the router has problems resolving...