Hey folks! Here's something that stumped me this afternoon:
At work, I need to use the following DNS records to develop with a local application server:
% nslookup android.twitch.techThis worked fine 6 months ago, but it's stopped working for me today, and I don't exactly know why, but I think I've narrowed it down to my AT&T Router. I'm curious if people know anything about how I could try to narrow this down further.
Server: 68.94.156.1
Address: 68.94.156.1#53
Non-authoritative answer:
Name: android.twitch.tech
Address: 10.0.2.2
% nslookup localhost.twitch.tech
Server: 68.94.156.1
Address: 68.94.156.1#53
Non-authoritative answer:
Name: localhost.twitch.tech
Address: 127.0.0.1
I have AT&T Home internet with a NOKIA BGW320-505 Router (Nokia from now on).
I have it configured to do IP Passthrough into my Asus RT-AX86U (Asus from now on),meshed with another Asus RT-AX86U via Cat 7 with a 2.5Gbps backhaul.
The Nokia IP address is 192.168.1.254 internally.
The Asus IP address is 192.168.50.1 internally.
The Nokia says 68.94.156.1 is the DNS server that my router shows as the Primary DNS under the Broadband -> Status Menu.
The Asus is configured under its WAN setting to use the Get the DNS IP from your ISP automatically setting (my understanding is that this means the Asus is using the DHCP settings from its lease from the Nokia).
In this configuration, android.twitch.tech lookups fail:
% nslookup android.twitch.techbut localhost.twitch.tech lookups succeed:
Server: 192.168.50.1
Address: 192.168.50.1#53
Non-authoritative answer:
*** Can't find android.twitch.tech: No answer
% nslookup localhost.twitch.techI've turned off all firewalls and packet filters on the AT&T Router.
Server: 192.168.50.1
Address: 192.168.50.1#53
Non-authoritative answer:
Name: localhost.twitch.tech
Address: 127.0.0.1
If I query using dig and use the AT&T DNS (68.94.156.1) directly (bypassing the Nokia), things work:
% dig @68.94.156.1 android.twitch.techAnd when I configured my Asus to use the AT&T DNS instead of the Nokia, things work:
; <<>> DiG 9.10.6 <<>> @68.94.156.1 android.twitch.tech
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49473
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;android.twitch.tech. IN A
;; ANSWER SECTION:
android.twitch.tech. 300 IN A 10.0.2.2
;; Query time: 84 msec
;; SERVER: 68.94.156.1#53(68.94.156.1)
;; WHEN: Mon Nov 03 19:02:17 CST 2025
;; MSG SIZE rcvd: 64
% dig @192.168.50.1 android.twitch.techAnd when I use dig to query the Nokia directly, things don't work (as expected):
; <<>> DiG 9.10.6 <<>> @192.168.50.1 android.twitch.tech
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36774
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;android.twitch.tech. IN A
;; ANSWER SECTION:
android.twitch.tech. 300 IN A 10.0.2.2
;; Query time: 54 msec
;; SERVER: 192.168.50.1#53(192.168.50.1)
;; WHEN: Mon Nov 03 19:03:10 CST 2025
;; MSG SIZE rcvd: 64
% dig @192.168.1.254 android.twitch.techTell me if you have any ideas on how to debug this further or on why the Nokia might be doing this. Thanks!
; <<>> DiG 9.10.6 <<>> @192.168.1.254 android.twitch.tech
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52979
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;android.twitch.tech. IN A
;; Query time: 202 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Mon Nov 03 19:03
