On 21 August 2013, at 18:14, Colin House wrote:
> On 22/08/2013 9:34 AM, Doug Hardie wrote:
>> There appears to be a problem with dig and the +trace option in 9.2. I
>> believe its also in 9.1. The command:
>>
>> dig freebsd.org +trace
>>
>>
On Thu, 22 Aug 2013 11:14:04 +1000
Colin House articulated:
> On 22/08/2013 9:34 AM, Doug Hardie wrote:
> > There appears to be a problem with dig and the +trace option in
> > 9.2. I believe its also in 9.1. The command:
> >
> > dig freebsd.org +trace
> >
>
On 22/08/2013 9:34 AM, Doug Hardie wrote:
There appears to be a problem with dig and the +trace option in 9.2. I believe
its also in 9.1. The command:
dig freebsd.org +trace
Only yields a dumb response. No useful information is provided. Running the
same command on FreeBSD 7.2 yields a
> > There appears to be a problem with dig and the +trace option in
> > 9.2. I believe its also in 9.1. The command:
> >
> > dig freebsd.org +trace
> >
> > Only yields a dumb response. No useful information is
> provided. Running the same comm
On 21 August 2013, at 17:02, Doug Hardie wrote:
>
> On 21 August 2013, at 16:46, Frank Leonhardt wrote:
>
>> On 22/08/2013 00:34, Doug Hardie wrote:
>>> There appears to be a problem with dig and the +trace option in 9.2. I
>>> believe its also i
On 22/08/2013 00:34, Doug Hardie wrote:
There appears to be a problem with dig and the +trace option in 9.2. I believe
its also in 9.1. The command:
dig freebsd.org +trace
Only yields a dumb response. No useful information is provided. Running the
same command on FreeBSD 7.2 yields a
There appears to be a problem with dig and the +trace option in 9.2. I believe
its also in 9.1. The command:
dig freebsd.org +trace
Only yields a dumb response. No useful information is provided. Running the
same command on FreeBSD 7.2 yields a complete trace with lots of useful
ad of telnet. You may also be referring the
format of the DNS query result which known as
[2]http://en.wikipedia.org/wiki/Reverse_DNS_lookup
I DID have a connection. ??? Maybe I gave too much detail,
but the point is that the IP yielded by host/dig did not match
what "whatismyip
On Sat, Apr 10, 2010 at 9:54 AM, Walter wrote:
> A previous question to the List on how to get an IP
> address from a host speicific URL yielded the helpful
> responses of "host" and "dig." These (seemed to) work
> fine. Well, just now I got a chance to try it
A previous question to the List on how to get an IP
address from a host speicific URL yielded the helpful
responses of "host" and "dig." These (seemed to) work
fine. Well, just now I got a chance to try it out on a tiny
server I have at someone else's house, and on
On Aug 18, 2008, at 10:25 PM, Fraser Tweedale wrote:
On Mon, Aug 18, 2008 at 10:18:07PM -0500, Jeffrey Goldberg wrote:
You'll want to change line four to
echo "$LINE " `dig +short -x $LINE`
for a cleaner output.
The original works fine for me in ash. Definitely nothing wro
n IP list to
> >> generate an ip+hostname list. IOW, I want to go from this:
> >>
> >> x.x.x.x
> >> y.y.y.y
> >>
> >> to this;
> >>
> >> x.x.x.x foo.domain.tld
> >> y.y..y.y bar.domain.tld
> >>
> >>
s;
x.x.x.x foo.domain.tld
y.y..y.y bar.domain.tld
What's the best/easiest way to do this?
Easiest:
$ for i in `cat ip-list`; do
> echo -n "$i "
> dig +short -x $i
> done
Don't know why I didn't think of that.
I ended up using this:
for ip in `cat public_
o.domain.tld
> y.y..y.y bar.domain.tld
>
> What's the best/easiest way to do this?
You could pipe it through:
while read ip;do echo "${ip} `dig +short -x ${ip}`";done
___
freebsd-questions@freebsd.org mailing list
http://lists.freeb
to do this?
Easiest:
$ for i in `cat ip-list`; do
> echo -n "$i "
> dig +short -x $i
> done
Better might be to use something in p5-net-DNS so that you don't make
N separate calls to dig.
Cheers,
-j
--
Jeffrey Goldberg
On Aug 18, 2008, at 10:13 PM, Fraser Tweedale wrote:
==
#!/bin/sh
while read LINE
do
echo $LINE `dig +short -x $LINE`
done
===
You'll want to change line four to
echo "$LINE " `dig +short -x $LINE`
for a
On Mon, Aug 18, 2008 at 10:18:07PM -0500, Jeffrey Goldberg wrote:
> On Aug 18, 2008, at 10:13 PM, Fraser Tweedale wrote:
>
> > ==
> > #!/bin/sh
> > while read LINE
> > do
> > echo
; >> What's the best/easiest way to do this?
> >>
> >> Paul Schmehl ([EMAIL PROTECTED])
> >> Senior Information Security Analyst
> >> The University of Texas at Dallas
> >> http://www.utdallas.edu/ir/security/
> >
> > dig(1) - see se
.y.y bar.domain.tld
>
> What's the best/easiest way to do this?
>
> Paul Schmehl ([EMAIL PROTECTED])
> Senior Information Security Analyst
> The University of Texas at Dallas
> http://www.utdallas.edu/ir/security/
dig(1) - see section `MULTIPLE QUERIES'
note the -x
.y
to this;
x.x.x.x foo.domain.tld
y.y..y.y bar.domain.tld
What's the best/easiest way to do this?
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/
dig(1) - see section `MULTIPLE QUERIES'
note th
I know I'm missing the obvious. I want to use an IP list to generate an
ip+hostname list. IOW, I want to go from this:
x.x.x.x
y.y.y.y
to this;
x.x.x.x foo.domain.tld
y.y..y.y bar.domain.tld
What's the best/easiest way to do this?
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Securit
Hello.
I have to use socks5 server for outgoing connections
from office LAN. After updating to FreeBSD 5.4-RELEASE-p6
dig stops working via runsocks:
defbsd# runsocks dig
Bus error (core dumped)
in logs:
Aug 26 00:14:51 defbsd libsocks5[7549]: NEC NWSL Socks5 v1.0r11 library
Aug 26 00:14:51
it was said:
>It works if I ping 'hostname', but how can I find out the IP of
>'hostname' from the command line?
Hello,
Would not grep 'hostname' /etc/hosts do this?
HTH,
stheg
__
Do you Yahoo!?
Yahoo! Small Business - Try our new resources
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2005-03-28, Emanuel Strobl scribbled these
curious markings:
> Is there one? Unfortunately I can't write one myself, at least not
> in a reasonable amount of time
- --cut--
#!/usr/bin/perl -w
use strict;
use Socket;
my $host = shift or die "us
there is something called /etc/hosts I thought.
> > It works if I ping 'hostname', but how can I find out the IP of
> > 'hostname' from the command line? dig and host want to contact the DNS
> > server, also nslookup does, so I think I need a utility which uses
, but how can I find out the IP of 'hostname'
> from the command line? dig and host want to contact the DNS server, also
> nslookup does, so I think I need a utility which uses the gethostbyname(3)
> function. Is there one? Unfortunately I can't write one myself, at least n
Dear all,
my testbed lacks of Ethernet Ports so one machine has no connection to my DNS,
no problem, there is something called /etc/hosts I thought.
It works if I ping 'hostname', but how can I find out the IP of 'hostname'
from the command line? dig and host want to co
Hi all. Wondering if anyone else is having similar problems. On
5.3-RELEASE (smp if it matters), I'm getting occasional (1 out of
every 10 runs or so) seg faults from running dig. In the core dump,
it makes mention of:
pointer != NULL
ERROR
/usr/src/secure/lib/libcrypto/../../../crypto/op
TECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: dig/named - res_nsend: Protocol not supported
Luke Cowell disturbed my sleep to write:
*Why* do I need to have IPV6 enable ? Is it some configuration option
of named that I overlooked ?
Hm...it could be that named is only listening on IPv6 localhost
Luke Cowell disturbed my sleep to write:
> *Why* do I need to have IPV6 enable ? Is it some configuration option
> of named that I overlooked ?
Hm...it could be that named is only listening on IPv6 localhost (::1)
rather than IPv4 (127.0.0.1) by default, but that seems strange to me.
Try "grep lo
Hi I'm running FreeBSD 4.9 and I'm having a little difficulty with
named/dig.
%uname -a
FreeBSD polo.asap.bc.ca 4.9-RELEASE-p1 FreeBSD 4.9-RELEASE-p1 #1: Thu
Feb 5 16:23:04 PST 2004
[EMAIL PROTECTED]:/usr/src/sys/compile/POLO i386
Here's what's happening.
%dig @l
Ignore my previously stated question. What I meant to say was:
*Why* do I need to have IPV6 enable ? Is it some configuration option
of named that I overlooked ?
On Feb 6, 2004, at 9:23, Luke Cowell wrote:
Hi I'm running FreeBSD 4.9 and I'm having a little difficulty with
named/di
Hi I'm running FreeBSD 4.9 and I'm having a little difficulty with
named/dig.
%uname -a
FreeBSD polo.asap.bc.ca 4.9-RELEASE-p1 FreeBSD 4.9-RELEASE-p1 #1: Thu
Feb 5 16:23:04 PST 2004
[EMAIL PROTECTED]:/usr/src/sys/compile/POLO i386
Here's what's happening.
%dig @l
ROTECTED]]On Behalf Of JoeB
> Sent: Tuesday, January 07, 2003 8:43 PM
> To: Fuzzy
> Cc: FBSDQ
> Subject: RE: dig command for reverse dsn check
>
>
>>>>>>>>>> snip <<<<<<<<<<<<<
> Thanks
On Tuesday, January 7, 2003, at 09:42 PM, JoeB wrote:
On Tue, 7 Jan 2003, JoeB wrote:
How do I check my ISP domain name to see if it's DNS server is
configured correctly for email reverse DNS lookup?
I'd use:
dig -x ip.ad.dr.ess PTR [@name.server]
the ANSWER SECTION shows what
On Tue, 7 Jan 2003, JoeB wrote:
> How do I check my ISP domain name to see if it's DNS server is
> configured correctly for email reverse DNS lookup? I have used dig
> isp-domain-name but I can not tell from what it displays what to
look
> for to verify it's configured corr
How do I check my ISP domain name to see if it's DNS server is
configured
correctly for email reverse DNS lookup? I have used dig
isp-domain-name
but I can not tell from what it displays what to look for to verify
it's configured
correctly. The dig display is lacking descriptive v
Hello,
Thought you'd like to know that the amendments you suggested works
for me now.
Thank you very much for the time and effort! See:
$ dig . ns @c.root-servers.net
; <<>> DiG 8.3 <<>> . ns @c.root-servers.net
; (1 server found)
;; res options: init recur
Hi,
I've made the changes to rule 00618 as you've suggested, but now I get
a different error:
# dig .ns @a.root-servers.net
; <<>> DiG 8.3 <<>> .ns @a.root-servers.net
; (1 server found)
;; res_nmkquery: buffer too small
# dig .ns @b.root-servers.ne
On Sun, Oct 27, 2002 at 06:29:16PM +, Stacey Roberts wrote:
Subject: Re: dig . ns @b.root-servers.net - Connection refused. WHY?
[related to FBSD 4.7 reset itself - lots of "DENY UDP" mess]ages in
/var/log/security
From: Stacey Roberts <[EMAIL PROTECTED]>
To: Ruben
18:19:35 GMT 2002
# dig . ns @b.root-servers.net
; <<>> DiG 8.3 <<>> . ns @b.root-servers.net
; (1 server found)
;; res options: init recurs defnam dnsrch
;; res_nsend to server b.root-servers.net 128.9.0.107: Operation timed
out
Checking logs:
# tail /var/log/security
On Sun, Oct 27, 2002 at 05:18:10PM +, Stacey Roberts wrote:
> Just checked against http://www.pgp.net/wwwkeys.html to verify:
>
> pub 2048R/DC92FBD7 2002-08-03 Stacey Roberts <[EMAIL PROTECTED]>
> Key fingerprint = 04 2E 82 F6 3E 78 25 14 42 84 90 E7 B7 B1 F7 26
>
> Verbose:
> Public K
Just checked against http://www.pgp.net/wwwkeys.html to verify:
pub 2048R/DC92FBD7 2002-08-03 Stacey Roberts <[EMAIL PROTECTED]>
Key fingerprint = 04 2E 82 F6 3E 78 25 14 42 84 90 E7 B7 B1 F7 26
Verbose:
Public Key Server -- Verbose Index ``0xDC92FBD7 ''
Type bits/keyIDDate Use
t; > I don't know if this is related to post earlier today [FBSD 4.7
> > reset itself - lots of "DENY UDP" messages in /var/log/security], but
> > I've been trying to trouble shoot the "DENY" messages in
> > /var/log/security using dig:
&g
DENY" messages in
> /var/log/security using dig:
>
> # dig . ns @b.root-servers.net
>
> ; <<>> DiG 8.3 <<>> . ns @b.root-servers.net
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; res_nsend to server b.root-servers.net 128
Hello,
I don't know if this is related to post earlier today [FBSD 4.7
reset itself - lots of "DENY UDP" messages in /var/log/security], but
I've been trying to trouble shoot the "DENY" messages in
/var/log/security using dig:
# dig . ns @b.root-servers.net
;
46 matches
Mail list logo
