On Mon, 7 Nov 2016 20:14:42 -0800 Bart wrote: BVA> My Internet provider (Comcast) does not provide any addresses BVA> for these two DNS names: BVA> BVA> $ dig +short twoa.net-snmp.org BVA> $ dig +short onea.net-snmp.org BVA> $ dig onea.net-snmp.org BVA> BVA> ; <<>> DiG 9.10.3-P4 <<>> onea.net-snmp.org BVA> ;; global options: +cmd BVA> ;; Got answer: BVA> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59379 BVA> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, BVA> ADDITIONAL: 1 BVA> BVA> ;; OPT PSEUDOSECTION: BVA> ; EDNS: version: 0, flags:; udp: 512 BVA> ;; QUESTION SECTION: BVA> ;onea.net-snmp.org. IN A BVA> BVA> ;; Query time: 532 msec BVA> ;; SERVER: 192.168.1.1#53(192.168.1.1)
The last line here shows that dig is using your local router as a resolver. Can you log in to it and see what it is set to use for DNS? I also have Comcast, and my router gets 75.75.75.75 and 75.75.76.76 as DNS servers. # host 75.75.75.75 75.75.75.75.in-addr.arpa domain name pointer cdns01.comcast.net. # host 75.75.76.76 76.76.75.75.in-addr.arpa domain name pointer cdns02.comcast.net. Telling dig to use either of those gets the correct result: # dig onea.net-snmp.org @75.75.75.75 ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.37.rc1.el6_7.2 <<>> onea.net-snmp.org @75.75.75.75 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3691 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;onea.net-snmp.org. IN A ;; ANSWER SECTION: onea.net-snmp.org. 14400 IN A 127.0.0.1 ;; Query time: 133 msec ;; SERVER: 75.75.75.75#53(75.75.75.75) ;; WHEN: Tue Nov 8 08:18:59 2016 ;; MSG SIZE rcvd: 51 # dig onea.net-snmp.org @75.75.76.76 ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.37.rc1.el6_7.2 <<>> onea.net-snmp.org @75.75.76.76 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57010 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;onea.net-snmp.org. IN A ;; ANSWER SECTION: onea.net-snmp.org. 14400 IN A 127.0.0.1 ;; Query time: 698 msec ;; SERVER: 75.75.76.76#53(75.75.76.76) ;; WHEN: Tue Nov 8 08:19:17 2016 ;; MSG SIZE rcvd: 51 I also get the correct answer from google's dns (8.8.8.8, 8.8.4.4), work, and both my hosting providers. So as far as I can tell, the failure point is your router's DNS resolution. Robert ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
