Hi folks, lately I've been debugging slow web page loading, and the culprit seems to be AT&T's DNS servers. I'm using the gateway in its default configuration as a router and thus using the default DNS servers. When I use dig to test with a bunch of domain names, I'm seeing sporadic timeouts. For example:
From http://192.168.1.254/cgi-bin/broadbandstatistics.ha
Primary DNS 68.94.156.1
% dig @68.94.156.1 marywood.edu;; communications error to 68.94.156.1#53: timed out;; communications error to 68.94.156.1#53: timed out ; <<>> DiG 9.18.26 <<>> @68.94.156.1 marywood.edu; (1 server found);; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17723;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION:; EDNS: version: 0, flags:; udp: 4096;; QUESTION SECTION:;marywood.edu. IN A ;; ANSWER SECTION:marywood.edu. 3600 IN A 3.33.211.116marywood.edu. 3600 IN A 15.197.240.141 ;; Query time: 18 msec;; SERVER: 68.94.156.1#53(68.94.156.1) (UDP);; WHEN: Sat Aug 03 09:05:40 PDT 2024;; MSG SIZE rcvd: 73
Of course, the server caches results, so I need to keep trying new domain names to repro the failure.
On my own machines I can program in 1.1.1.1 as DNS and that seems to fix things, but I would like AT&T to fix this on their end.
I'm curious if any others are seeing this, or if the DSLR hivemind has given up on AT&T dns servers and I should get the hint, heh :)
↧