RE: nslookup strangeness

2005-12-21 Thread doug
Hi - thanks for the reply. The host in question runs named because it is also a secondary name server for the domains Safeport hosts. I also use it as the name server for our internal network. The error is that nslookup terminates after the message and that I apparently changed something as this

RE: nslookup strangeness

2005-12-20 Thread Ruben Bloemgarten
Hi Douglas, If you are using dns relay on your gateway why would you want to use named ? Also, it might be an idea to put the dns server ( i.e. the gateway) in your resolv.conf. Furthermore, neither your hosts ip4 ip (192.168.3.1) nor your non existant ip6 ip (:::) should be able to be resolved,