Re: nslookup & bind problem on internal network

2004-02-19 Thread CW Harris
On Thu, Feb 19, 2004 at 12:29:56AM +, Mark C wrote: > On Thu, 2004-02-19 at 00:11, CW Harris wrote: > > > As a guess-- did you define your internal network to be funkypenguin.net > > and authoritative for the domain? Thus there is no DNS path out of your > > LAN to the real authority for funk

Re: nslookup & bind problem on internal network

2004-02-18 Thread Brett Carrington
On Thu, Feb 19, 2004 at 12:29:56AM +, Mark C wrote: > On Thu, 2004-02-19 at 00:11, CW Harris wrote: > > > As a guess-- did you define your internal network to be funkypenguin.net > > and authoritative for the domain? Thus there is no DNS path out of your > > LAN to the real authority for funk

Re: nslookup & bind problem on internal network

2004-02-18 Thread Mark C
On Thu, 2004-02-19 at 00:11, CW Harris wrote: > As a guess-- did you define your internal network to be funkypenguin.net > and authoritative for the domain? Thus there is no DNS path out of your > LAN to the real authority for funkypenguin.net? > > Give us more info on how you have your domain s

Re: nslookup & bind problem on internal network

2004-02-18 Thread CW Harris
On Wed, Feb 18, 2004 at 11:10:18PM +, Mark C wrote: > Hi, > > I've just set up bind for my internal network, and running: > > 'nslookup funkypenguin.net' returns: > > Note: nslookup is deprecated and may be removed from future releases. > Consider using the `dig' or `host' programs instead

nslookup & bind problem on internal network

2004-02-18 Thread Mark C
Hi, I've just set up bind for my internal network, and running: 'nslookup funkypenguin.net' returns: Note: nslookup is deprecated and may be removed from future releases. Consider using the `dig' or `host' programs instead. Run nslookup with the `-sil[ent]' option to prevent this message from