Weird nslookup responce

Status
Not open for further replies.

clincha

Dabbler
Joined
May 10, 2014
Messages
15
Hey guys,

having issues with couchPotato and uninstalled it and then couldn't load any plugins because it says "No entry has been found" under available plugins. So I did a ns lookup and I got this output. Can anyone help and tell me what's happening and how to fix it?

Code:
[root@Server ~]# nslookup google.com                                            
/fusion/jkh/921/FN/FreeBSD/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/
socket.c:1890: internal_send: 192.168.1.1#53: Invalid argument                  
/fusion/jkh/921/FN/FreeBSD/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/
socket.c:1890: internal_send: 8.8.8.8#53: Invalid argument                      
/fusion/jkh/921/FN/FreeBSD/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/
socket.c:1890: internal_send: 8.8.4.4#53: Invalid argument                      
/fusion/jkh/921/FN/FreeBSD/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/
socket.c:1890: internal_send: 192.168.1.1#53: Invalid argument                  
/fusion/jkh/921/FN/FreeBSD/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/
socket.c:1890: internal_send: 8.8.8.8#53: Invalid argument                      
/fusion/jkh/921/FN/FreeBSD/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/
socket.c:1890: internal_send: 8.8.4.4#53: Invalid argument                      
/fusion/jkh/921/FN/FreeBSD/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/
socket.c:1890: internal_send: 192.168.1.1#53: Invalid argument                  
/fusion/jkh/921/FN/FreeBSD/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/
socket.c:1890: internal_send: 8.8.8.8#53: Invalid argument                      
/fusion/jkh/921/FN/FreeBSD/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/
socket.c:1890: internal_send: 8.8.4.4#53: Invalid argument                      
;; connection timed out; no servers could be reached                            
 


Thanks,

clincha
 

clincha

Dabbler
Joined
May 10, 2014
Messages
15
Kind of....

I set my NAS to have a static IP address but for some reason it gave me the above response so I changed it to dynamic IP and restarted it and it all works fine now. I am a little disappointed it isn't a static IP though
 
Status
Not open for further replies.
Top