--- Begin Message ---
While all the authoritative name servers for bit.ly currently have the
same serial number (1), my resolver got a SOA with a different number,
and a different content (no A and no AAAA):
% dig bit.ly
; <<>> DiG 9.18.39-0ubuntu0.24.04.2-Ubuntu <<>> bit.ly
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64698
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 1232
;; QUESTION SECTION:
;bit.ly. IN A
;; AUTHORITY SECTION:
bit.ly. 6623 IN SOA ns-1372.awsdns-43.org.
ns-cloud-c3.googledomains.com. (
2003080406 ; serial
10800 ; refresh (3 hours)
3600 ; retry (1 hour)
604800 ; expire (1 week)
21600 ; minimum (6 hours)
)
;; Query time: 4 msec
;; SERVER: 192.168.2.254#53(192.168.2.254) (UDP)
;; WHEN: Fri Feb 13 11:24:42 CET 2026
;; MSG SIZE rcvd: 121
Testing with RIPE Atlas probes
<https://atlas.ripe.net/measurements/154580059>, I see that I'm not
the only one who got this serial number 2003080406.
Temporary error in publication? Or an anycast instance somewhere
serving a wrong zone?
--- End Message ---
_______________________________________________
dns-operations mailing list
[email protected]
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
