Re: Odd name lookup behavior

2009-11-19 Thread Dave Anderson
On Thu, 19 Nov 2009, stan wrote: >On Thu, Nov 19, 2009 at 03:08:25PM -0500, Dave Anderson wrote: >> On Thu, 19 Nov 2009, stan wrote: >> >> >On Thu, Nov 19, 2009 at 11:24:44AM -0500, Dave Anderson wrote: >> >> On Thu, 19 Nov 2009, stan wrote: >> >> >> >> >On Wed, Nov 18, 2009 at 11:03:27PM -0500, D

Re: Odd name lookup behavior

2009-11-19 Thread Ted Unangst
Q: what's more annoying than top posting? A: full quoting bottom posters. On Nov 19, 2009, at 12:57 PM, stan wrote: On Thu, Nov 19, 2009 at 03:08:25PM -0500, Dave Anderson wrote: On Thu, 19 Nov 2009, stan wrote: On Thu, Nov 19, 2009 at 11:24:44AM -0500, Dave Anderson wrote: On Thu, 19 Nov

Re: Odd name lookup behavior

2009-11-19 Thread stan
On Thu, Nov 19, 2009 at 03:08:25PM -0500, Dave Anderson wrote: > On Thu, 19 Nov 2009, stan wrote: > > >On Thu, Nov 19, 2009 at 11:24:44AM -0500, Dave Anderson wrote: > >> On Thu, 19 Nov 2009, stan wrote: > >> > >> >On Wed, Nov 18, 2009 at 11:03:27PM -0500, Dave Anderson wrote: > >> >> On Wed, 18 N

Re: Odd name lookup behavior

2009-11-19 Thread Dave Anderson
On Thu, 19 Nov 2009, stan wrote: >On Thu, Nov 19, 2009 at 11:24:44AM -0500, Dave Anderson wrote: >> On Thu, 19 Nov 2009, stan wrote: >> >> >On Wed, Nov 18, 2009 at 11:03:27PM -0500, Dave Anderson wrote: >> >> On Wed, 18 Nov 2009, stan wrote: >> >> >> >> >On Wed, Nov 18, 2009 at 05:00:02PM -0500, D

Re: Odd name lookup behavior

2009-11-19 Thread stan
On Thu, Nov 19, 2009 at 11:24:44AM -0500, Dave Anderson wrote: > On Thu, 19 Nov 2009, stan wrote: > > >On Wed, Nov 18, 2009 at 11:03:27PM -0500, Dave Anderson wrote: > >> On Wed, 18 Nov 2009, stan wrote: > >> > >> >On Wed, Nov 18, 2009 at 05:00:02PM -0500, Dave Anderson wrote: > >> >> On Wed, 18 N

Re: Odd name lookup behavior

2009-11-19 Thread Dave Anderson
On Thu, 19 Nov 2009, stan wrote: >On Wed, Nov 18, 2009 at 11:03:27PM -0500, Dave Anderson wrote: >> On Wed, 18 Nov 2009, stan wrote: >> >> >On Wed, Nov 18, 2009 at 05:00:02PM -0500, Dave Anderson wrote: >> >> On Wed, 18 Nov 2009, stan wrote: >> >> >> >> >Can anyone xplain this behavior to me? >> >

Re: Odd name lookup behavior

2009-11-19 Thread stan
On Wed, Nov 18, 2009 at 11:03:27PM -0500, Dave Anderson wrote: > On Wed, 18 Nov 2009, stan wrote: > > >On Wed, Nov 18, 2009 at 05:00:02PM -0500, Dave Anderson wrote: > >> On Wed, 18 Nov 2009, stan wrote: > >> > >> >Can anyone xplain this behavior to me? > >> > >> Without access to your nameservers

Re: Odd name lookup behavior

2009-11-18 Thread Dave Anderson
On Wed, 18 Nov 2009, Bryan Irvine wrote: >> You apparently have a system with multiple names and a single IP >> address. Both cvsup.mch.chs and cvsup.meadwestvaco.com are assigned >> address 10.209.142.151, but the reverse-lookup entry can't return both >> names. > > >You made that up. Yes it can

Re: Odd name lookup behavior

2009-11-18 Thread Bryan Irvine
> You apparently have a system with multiple names and a single IP > address. Both cvsup.mch.chs and cvsup.meadwestvaco.com are assigned > address 10.209.142.151, but the reverse-lookup entry can't return both > names. You made that up. Yes it can. If it's configured to do so. I'm guessing tha

Re: Odd name lookup behavior

2009-11-18 Thread Dave Anderson
On Wed, 18 Nov 2009, stan wrote: >On Wed, Nov 18, 2009 at 05:00:02PM -0500, Dave Anderson wrote: >> On Wed, 18 Nov 2009, stan wrote: >> >> >Can anyone xplain this behavior to me? >> >> Without access to your nameservers it's not possible to be sure, but see >> below -- this looks normal to me. >>

Re: Odd name lookup behavior

2009-11-18 Thread stan
On Wed, Nov 18, 2009 at 11:21:41PM +0100, Robert wrote: > On Wed, 18 Nov 2009 15:06:28 -0500 > stan wrote: > > > Can anyone xplain this behavior to me? > > > > Given the following resolv.conf file: > > > > r...@pm3fw:root# cat /etc/resolv.conf > > lookup file bind > > search mcn.chs kapstonepap

Re: Odd name lookup behavior

2009-11-18 Thread stan
On Wed, Nov 18, 2009 at 11:21:41PM +0100, Robert wrote: > On Wed, 18 Nov 2009 15:06:28 -0500 > stan wrote: > > > Can anyone xplain this behavior to me? > > > > Given the following resolv.conf file: > > > > r...@pm3fw:root# cat /etc/resolv.conf > > lookup file bind > > search mcn.chs kapstonepap

Re: Odd name lookup behavior

2009-11-18 Thread stan
On Wed, Nov 18, 2009 at 05:00:02PM -0500, Dave Anderson wrote: > On Wed, 18 Nov 2009, stan wrote: > > >Can anyone xplain this behavior to me? > > Without access to your nameservers it's not possible to be sure, but see > below -- this looks normal to me. > > >Given the following resolv.conf file

Re: Odd name lookup behavior

2009-11-18 Thread Robert
On Wed, 18 Nov 2009 15:06:28 -0500 stan wrote: > Can anyone xplain this behavior to me? > > Given the following resolv.conf file: > > r...@pm3fw:root# cat /etc/resolv.conf > lookup file bind > search mcn.chs kapstonepaper.com pm3.charleston.meadwestvaco.com > nameserver 127.0.0.1 > nameserver

Re: Odd name lookup behavior

2009-11-18 Thread Dave Anderson
On Wed, 18 Nov 2009, stan wrote: >Can anyone xplain this behavior to me? Without access to your nameservers it's not possible to be sure, but see below -- this looks normal to me. >Given the following resolv.conf file: > >r...@pm3fw:root# cat /etc/resolv.conf >lookup file bind >search mcn.chs ka

Odd name lookup behavior

2009-11-18 Thread stan
Can anyone xplain this behavior to me? Given the following resolv.conf file: r...@pm3fw:root# cat /etc/resolv.conf lookup file bind search mcn.chs kapstonepaper.com pm3.charleston.meadwestvaco.com nameserver 127.0.0.1 nameserver 10.209.128.20 nameserver 10.209.128.26 nameserver 10.209.142.158 A