|
|
| Author |
Message |
| 25 new of 205 responses total. |
willard
|
|
response 175 of 205:
| 
Sep 2 14:25 UTC 2000 |
Don't use nslookup. Use dig.
|
goose
|
|
response 176 of 205:
|
Sep 3 17:18 UTC 2000 |
What's dig?
|
willard
|
|
response 177 of 205:
|
Sep 3 17:20 UTC 2000 |
DIG(1) USER COMMANDS DIG(1)
NAME
dig - send domain name query packets to name servers
SYNOPSIS
dig [@server] domain [<query-type>] [<query-class>]
[+<query-option>] [-<dig-option>] [%comment]
DESCRIPTION
Dig (domain information groper) is a flexible command line
tool which can be used to gather information from the Domain
...
|
mcnally
|
|
response 178 of 205:
|
Sep 3 23:33 UTC 2000 |
dig is the power-user's nslookup replacement..
|
jazz
|
|
response 179 of 205:
|
Sep 4 01:57 UTC 2000 |
The right tool for the right job. Dig's great for certain things,
among them verifying large DNS databases after automated or manual changes,
but it's overkill (and confusing in the verbosity of it's output) when used
to prove something ismple, like a given nameserver's inability to pull up DNS
records for a given host.
|
willard
|
|
response 180 of 205:
|
Sep 4 02:06 UTC 2000 |
Sure, if your a moron.
|
gelinas
|
|
response 181 of 205:
|
Sep 4 03:10 UTC 2000 |
I usually use dnsquery (which I've used since it was called simply "query"),
but there are some things dig is better at. I've never seen any reason to
use nslookup.
|
don
|
|
response 182 of 205:
|
Sep 4 03:35 UTC 2000 |
I don't know if this is odd or part of an unfixed problem. I couldn't get a
connection via cyberspace.org, so I went to m-net and tried there. It gave
me an IP and an "access denied" message (due to lack of patron access). I
tried the given IP with my telnet client and got in. What that suggests to
me is that m-net uses an updated DNS while my ISP doesn't. Which doesn't make
sense, because Mindspring is huge enough and in general reliable enough to
change the records on its own DNS's.
|
gelinas
|
|
response 183 of 205:
|
Sep 4 05:03 UTC 2000 |
Right now, neither vixa.voyager.net nor puck.nether.net are admitting
any knowledge of cyberspace.org. . . . Ah:
; <<>> DiG 8.1 <<>> @PUCK.NETHER.NET cyberspace.org -t +norec
; (1 server found)
;; res options: init defnam dnsrch
;; res_send to server PUCK.NETHER.NET 204.42.254.5: Connection timed out
and
; <<>> DiG 8.1 <<>> @vixa.voyager.net cyberspace.org -t +norec
; (1 server found)
;; res options: init defnam dnsrch
;; res_send to server vixa.voyager.net 209.153.128.118: Connection timed out
|
willard
|
|
response 184 of 205:
|
Sep 4 05:04 UTC 2000 |
#180: s/your/you're/ ... sorry. That's what I get for Grexing
between naps on a lazy Sunday afternoon.
|
tpryan
|
|
response 185 of 205:
|
Sep 4 15:08 UTC 2000 |
r184, yes, I thought it was a rather moronic way of calling someone a moron.
|
jared
|
|
response 186 of 205:
|
Sep 5 00:39 UTC 2000 |
vixa is no longer a dns server.
|
prp
|
|
response 187 of 205:
|
Sep 5 03:55 UTC 2000 |
re 181: I doubt that you use dnsquery on Grex. It does not seem to
exist.
|
gelinas
|
|
response 188 of 205:
|
Sep 5 04:20 UTC 2000 |
Right; I don't normally use grex for such things, because I have other hosts
to use. Like the one on my desk at work.
|
scott
|
|
response 189 of 205:
|
Sep 5 12:20 UTC 2000 |
We might have dnsquery, but we do tend to limit abusable tools (like ping)
to staff only.
|
gelinas
|
|
response 190 of 205:
|
Sep 6 01:44 UTC 2000 |
Well, it's here now:
} Respond, pass, forget, quit, or ? for more options? !whereis dnsquery
} dnsquery: /usr/local/bin/dnsquery
}
} Respond, pass, forget, quit, or ? for more options? !which dnsquery
} /usr/local/bin/dnsquery
}
} Respond, pass, forget, quit, or ? for more options? !ls -lFg
/usr/local/bin/dnsquery } -rwxr-xr-x 1 mdw staff 131072 Sep 5
02:33 /usr/local/bin/dnsquery*
|
don
|
|
response 191 of 205:
|
Sep 9 01:26 UTC 2000 |
idled isn't working. Also, a run of newuser has been idle for 3 days.
|
don
|
|
response 192 of 205:
|
Sep 9 03:00 UTC 2000 |
It works now.
|
keesan
|
|
response 193 of 205:
|
Sep 13 15:08 UTC 2000 |
Dialed 7613000 just now. BUSY. Got in on 7615041. Don't we have lots of
unused dialin lines? Why 'busy'?
|
cmcgee
|
|
response 194 of 205:
|
Sep 14 01:11 UTC 2000 |
I got a busy signal a couple days ago too. I assumed that it meant that all
the lines were in use. As far as I remember we don't have lots of unused
lines, just one (or maybe two) that have extremely infrequent use. *shrug*
If we take those away, you'll be getting that busy signal much more
frequently. But we will be saving money.
|
tpryan
|
|
response 195 of 205:
|
Sep 14 15:57 UTC 2000 |
Could be saving money, or could be making use near impossible for
paying members. Which would lead to a loss of revenue.
|
keesan
|
|
response 196 of 205:
|
Sep 14 17:02 UTC 2000 |
How many lines do we have now?
|
scott
|
|
response 197 of 205:
|
Sep 14 18:52 UTC 2000 |
We have eleven phone lines, but it's very rare to see even 5 or 6 in use at
once.
I have no idea about the busy signal the other day. Could have been some
phone system problem.
|
rcurl
|
|
response 198 of 205:
|
Sep 14 19:03 UTC 2000 |
It's statistical. With users dialing in a hanging up independently, there
is a statistical distribution, with a finite probability of all lines
being in use. If you can give me the known average number in use at
any moment, I can calculate the probability of all being in use.
|
krj
|
|
response 199 of 205:
|
Sep 14 19:55 UTC 2000 |
There's an item for discussing the phone allocation in policy, isn't there?
Could we move this discussion there?
|
