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: > > > >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 > > > >And: > > > >r...@pm3fw:root# nslookup > >> cvsup > >Server: 127.0.0.1 > >Address: 127.0.0.1#53 > > > >Non-authoritative answer: > >Name: cvsup.mcn.chs > >Address: 10.209.142.151 > >> 10.209.142.151 > >Server: 127.0.0.1 > >Address: 127.0.0.1#53 > > > >151.142.209.10.in-addr.arpa name = cvsup.meadwestvaco.com. > >> exit > > > >Why does this happen ? And how? > > 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. Given the order of domains in your 'search' directive, > cvsup.mcn.chs is looked up first and so is the name that nslookup > reports, but cvsup.meadwestvaco.com was chosen as the 'official' name > for the reverse lookup by whoever set up your DNS. > > Your analysis is correct, in that thier are multiple names (don't ask :-(). I have control of some of the nameservers. They are bind 9 on OpenBSD, can you clarify what you mean by "offical name" are you talking about a A entry, as oposed to a CNAME entry?
-- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
