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 a
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,
David Jenkins wrote:
On Wed, 24 November, 2004 0:47, Nicolas said:
Hello,
I've set up a FreeBSD box to provide my home network a NAT access to
the
Internet and a DNS caching-only server with bind 8.3.7 (among other
things).
It's working perfectly but today I noticed something that I do not
understa
On Wed, 24 November, 2004 0:47, Nicolas said:
> Hello,
>
> I've set up a FreeBSD box to provide my home network a NAT access to
> the
> Internet and a DNS caching-only server with bind 8.3.7 (among other
> things).
>
> It's working perfectly but today I noticed something that I do not
> understand.
* Kirk Strauser <[EMAIL PROTECTED]> [2004-04-15 10:56]:
> At 2004-04-15T13:58:52Z, "Shaun T. Erickson" <[EMAIL PROTECTED]> writes:
>
> > nslookup?
>
> Don't use nslookup. It's a Bad Thing.
I really don't want to hijack this thread, but you've peaked my
curiosity; can you elaborate?
--
Joshu
At 2004-04-15T18:35:47Z, Jerry McAllister <[EMAIL PROTECTED]> writes:
> I haven't heard that there is any specific evil involved, just that
> somewhere in the high court of those who pass judgement on such things, it
> has been decided to phase out nslookup in favor of new utilities.
Nope. nsloo
>
> At 2004-04-15T13:58:52Z, "Shaun T. Erickson" <[EMAIL PROTECTED]> writes:
>
> > nslookup?
>
> Don't use nslookup. It's a Bad Thing.
>
I haven't heard that there is any specific evil involved, just that
somewhere in the high court of those who pass judgement on such things,
it has been dec
At 2004-04-15T13:58:52Z, "Shaun T. Erickson" <[EMAIL PROTECTED]> writes:
> nslookup?
Don't use nslookup. It's a Bad Thing.
--
Kirk Strauser
"94 outdated ports on the box,
94 outdated ports.
Portupgrade one, an hour 'til done,
82 outdated ports on the box."
pgp0.pgp
Description: PGP si
On Thu, Apr 15, 2004 at 08:56:29AM -0500, Brian Henning wrote:
> is there a bsd tool that gives the domain name of an IP address?
>
> I know this will give me an ip of one of the google web servers.
> traceroute www.google.com
dig -x 12.34.56.78
- or -
host 12.34.56.78
Note that rath
Brian Henning wrote:
is there a bsd tool that gives the domain name of an IP address?
host?
nslookup?
-ste
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL
On Sun, Jan 25, 2004 at 11:13:06AM -0800, Matthew Fremont wrote:
> The nameserver is working properly, and commands like
> dig(1), host(1), telnet(1), and ftp(1), are able to
> sucessfully resolve names. The problem appears to be
> isolated to nslookup(8).
>
> If memory serves me correctly, at som
11 matches
Mail list logo
