DNS Broken for pkg.pfsense.org
-
Hi, is this intended or an error?
Thanks!
; <<>> DiG 9.11.1-P1 <<>> pkg.pfsense.org @ns1.netgate.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58889 ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;pkg.pfsense.org. IN A ;; AUTHORITY SECTION: pfsense.org. 300 IN SOA ns1.netgate.com. admin.netgate.com. 201608312 3600 7200 1209600 3600 ;; Query time: 40 msec ;; SERVER: 192.207.126.6#53(192.207.126.6) ;; WHEN: Sun Jun 25 13:53:59 MDT 2017 ;; MSG SIZE rcvd: 101
-
It's not an error, the pkg tool uses SRV records to figure out the suitable mirror for the packages.
[2.3.4-RELEASE][admin@firewall.rdnzl.fi]/root: dig _https._tcp.pkg.pfsense.org SRV ; <<>> DiG 9.11.1 <<>> _https._tcp.pkg.pfsense.org SRV ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30052 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_https._tcp.pkg.pfsense.org. IN SRV ;; ANSWER SECTION: _https._tcp.pkg.pfsense.org. 51 IN SRV 10 10 443 files01.netgate.com. _https._tcp.pkg.pfsense.org. 51 IN SRV 10 10 443 files00.netgate.com. ;; AUTHORITY SECTION: pfsense.org. 291 IN NS ns2.netgate.com. pfsense.org. 291 IN NS ns1.netgate.com. ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Mon Jun 26 09:02:51 EEST 2017 ;; MSG SIZE rcvd: 181
-
https://forum.netgate.com/topic/115789/pkg-pfsense-org-appears-to-be-dead/2
-