Re: host unreachable. -- a bit more info

2011-01-13 Thread Jay G. Scott
heh. sorry. i did read dig's man page but i thought you were going to reply and tell me my dig version was behind yours. sorry for the tardy reply. one of those weeks. j. ns5 52 > dig @146.6.211.1 +tcp arlut.utexas.edu ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_5.3 <<>> @146.6.211.1 +tcp a

Re: host unreachable. -- a bit more info

2011-01-10 Thread David Sparro
On 1/10/2011 2:04 PM, Jay G. Scott wrote: On Mon, Jan 10, 2011 at 12:41:48PM -0600, Jay G. Scott wrote: hi, thanks for the replies. however, i didn't learn much. i'm more of a network newbie than i thought. but what i can say is this: (repeating the problem) i get zillions of these msgs: J

Re: host unreachable. -- a bit more info

2011-01-10 Thread Lyle Giese
sorry about that. I don't normally use these options But it's dig @146.6.211.1 +tcp arlut.utexas.edu dig @146.6.211.1 +notcp arlut.utexas.edu But UDP is default and the second query should have been transmitted using UDP. The end result is that you have TCP and UDP port 53 openned properly in the

Re: host unreachable. -- a bit more info

2011-01-10 Thread Jay G. Scott
On Mon, Jan 10, 2011 at 12:52:16PM -0600, Lyle Giese wrote: [snip] > Jay > Please do the following two queries from the secondary server and show > us the results: > > dig @146.6.211.1 +tcp arlut.utexas.edu > > dig @146.6.211.1 -tcp arlut.utexas.edu > > Lyle Giese > LCR Computer Services, Inc.

Re: host unreachable. -- a bit more info

2011-01-10 Thread Jay G. Scott
On Mon, Jan 10, 2011 at 12:41:48PM -0600, Jay G. Scott wrote: > > hi, > > thanks for the replies. however, i didn't learn much. i'm more of > a network newbie than i thought. > > but what i can say is this: > > (repeating the problem) > i get zillions of these msgs: > Jan 10 12:36:24 ns2 name

Re: host unreachable. -- a bit more info

2011-01-10 Thread Lyle Giese
Jay G. Scott wrote: > hi, > > thanks for the replies. however, i didn't learn much. i'm more of > a network newbie than i thought. > > but what i can say is this: > > (repeating the problem) > i get zillions of these msgs: > Jan 10 12:36:24 ns2 named[3037]: client 10.4.1.6#59926: view internal: e

Re: host unreachable. -- a bit more info

2011-01-10 Thread Jay G. Scott
hi, thanks for the replies. however, i didn't learn much. i'm more of a network newbie than i thought. but what i can say is this: (repeating the problem) i get zillions of these msgs: Jan 10 12:36:24 ns2 named[3037]: client 10.4.1.6#59926: view internal: error sending response: host unreach