Updates timeout connecting to pkg.pfsense.org.



  • Hi,

    I'm trying to update from 2.3.2 to the newest version.  However, the update keeps failing when trying to download packages from pkg.pfsense.org.  Is it supposed to be using pkg.pfsense.org?

    dig pkg.pfsense.org @ns1.netgate.com
    

    …gives:

    ; <<>> DiG 9.9.4-RedHat-9.9.4-51.el7_4.1 <<>> pkg.pfsense.org @ns1.netgate.com
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6590
    ;; 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. 201608322 3600 7200 1209600 3600
    
    ;; Query time: 74 msec
    ;; SERVER: 192.207.126.6#53(192.207.126.6)
    ;; WHEN: Thu Jan 04 14:22:22 CST 2018
    ;; MSG SIZE  rcvd: 101
    

  • LAYER 8 Global Moderator

    that is never going to work because pkg.pfsense.org is not a A record its SRV record..

    Dig for
    _http._tcp.pkg.pfsense.org

    or

    dig _https._tcp.pkg.pfsense.org

    example

    dig _http._tcp.pkg.pfsense.org SRV

    ; <<>> DiG 9.11.2 <<>> _http._tcp.pkg.pfsense.org SRV
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43779
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 1

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;_http._tcp.pkg.pfsense.org.    IN      SRV

    ;; ANSWER SECTION:
    _http._tcp.pkg.pfsense.org. 3600 IN    SRV    10 10 80 files00.netgate.com.
    _http._tcp.pkg.pfsense.org. 3600 IN    SRV    10 10 80 files01.netgate.com.

    ;; AUTHORITY SECTION:
    pfsense.org.            3600    IN      NS      ns1.netgate.com.
    pfsense.org.            3600    IN      NS      ns2.netgate.com.

    ;; Query time: 68 msec
    ;; SERVER: 192.168.3.10#53(192.168.3.10)
    ;; WHEN: Thu Jan 04 14:29:48 Central Standard Time 2018
    ;; MSG SIZE  rcvd: 180



  • Thanks for the quick reply and explanation.  I didn't realized it was using a SRV record.  I'm likely seeing a localized issue since I see now that it fails (randomly) on different packages.  Sorry for the noise.


Log in to reply