No DNS-resolution after going to "unbound"

[Robert Huff]

On 3/25/2014 6:38 AM, Trond Endrestøl wrote:

> On Tue, 25 Mar 2014 11:33+0100, Ewald Jenisch wrote:

>> So I went ahead and proceeded as per
>> https://wiki.freebsd.org/WhatsNew/FreeBSD10 which in turn points to
>> http://blog.des.no/2013/09/local-caching-resolver-in-freebsd-10/ i.e.
>
>> # ping www.cisco.com
>> ping: cannot resolve www.cisco.com: Host name lookup failure
>> #
>>
>>
>> # drill www.cnn.com
>> ;; ->>HEADER<<- opcode: QUERY, rcode: SERVFAIL, id: 46336
>> ;; flags: qr rd ra ; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
>> ;; QUESTION SECTION:
>> ;; www.cnn.com. IN      A
>>
>> ;; ANSWER SECTION:
>>
>> ;; AUTHORITY SECTION:
>>
>> ;; ADDITIONAL SECTION:
>>
>> ;; Query time: 126 msec
>> ;; SERVER: 127.0.0.1
>> ;; WHEN: Tue Mar 25 11:29:39 2014
>> ;; MSG SIZE  rcvd: 29
>> #

	I get nearly identical symptoms with a rather different setup.
	System: CURRENT/r263263
	Unbound: disabled (as far as I can tell)
	Nameservice: using bind99 from ports.  This worked two days ago and 
then yesterday - blammo!
	This system is the default nameserver for the LAN, and queries from 
other clients seem to be accepted and answered.  Only the machine itself 
is blind.
	Other independent network services seem unaffected, and I can telnet to 
port 53 on my ISP's public nameservers.

	Respectfully,


			Robert Huff