[UCLA-LUG] Weird DNS alias problem

[chris]

you don't want to use nis for hosts.  it sucks ass.  if you absolutely
have to use nis for hosts, reverse it to something like

 hosts: files dns nis

and when you say that ping/traceroute works slowly what do you mean? 
network time?  or time for it to resolve the hostname and then start doing
something?

-chris

On Thu, 18 Nov 1999, Glenn Glazer wrote:

> Well, some progress to report.
> 
> Tried both adding 128.97.128.1 to /etc/resolv.conf and the line below to
> nsswitch.conf.  The previous hosts line said: 
>      hosts:     nis [NOTFOUND=return] files
> that is, consult files iff nis is down.  (BTW, we use nis, not nis+)
> 
> Now, pings work mostly, but verrrry slowly (like 15 seconds to ping
> www.math.ucla.edu).  Ditto netscape.  Netscape takes a long time to find
> the site, but once it does, the page loads nearly instantaneously.
> traceroute also works, but slowly.  Oddly, it takes about the same amount
> of time to ping www.nic.ad.jp as it does to ping www.math.ucla.edu.  
> 
> Best,
> 
> Glenn
> 
> At 01:16 PM 11/18/99 -0800, you wrote:
> >Typically when you can use nslookup but still can't resolve host
> >names with other things it points to the nsswitch.conf file not being right.
> >
> >If you look in the nsswitch.conf file there should be an entry like this
> >hosts:	files dns nisplus
> >
> >E
> >
> >On Thu, Nov 18, 1999 at 12:06:07PM -0800, Dimi Shahbaz wrote:
> >> Pretty sure the problem is not /etc/resolv.conf now... just in case, try
> >> adding  128.97.128.1 as well.  let me know if that doesn't work either.
> >> 
> >> -----
> >> Your attention please everyone, if I could just say a few words... I would 
> >be a better public speaker. 
> >>   -- Homer Simpson
> >> 
> >> On Thu, 18 Nov 1999, Glenn Glazer wrote:
> >> 
> >> > Okay, I added 131.179.128.30 and even moved it to the top of the list
> >> > (under the domain), but no luck.
> >> > 
> >> > Any other thoughts?
> >> > 
> >> > At 08:21 AM 11/18/99 -0800, you wrote:
> >> > >My /etc/resolv.conf looks like this:
> >> > >
> >> > >domain	math.ucla.edu
> >> > >nameserver	128.97.4.254		;julia.math.ucla.edu, dept. nameserver
> >> > >nameserver	128.97.12.3                   ;malibu.pic.ucla.edu, dept.
> >> > nameserver
> >> > >nameserver	164.67.128.11		;kodiak.ucla.edu, ucla nameserver
> >> > >
> >> > >(the ;comments are not actually in the file).
> >> > >
> >> > >I will add Mailman (131.179.128.30) and see if that helps.  I will mail 
> >back 
> >> > >if the problem persists.
> >> > >
> >> > >Another point is that the problem is intermittent.  That is, sometimes 
> >a new 
> >> > >IP alias works and sometimes a (different) new alias won't.  Further, I 
> >can 
> >> > >always pull up any website in the math or pic domains.
> >> > >
> >> > >Best,
> >> > >
> >> > >Glenn
> >> > >
> >> > >At 08:08 PM 11/17/99 -0800, you wrote:
> >> > >>Here is a sample /etc/resolv.conf file:
> >> > >> 
> >> > >>nameserver 131.179.128.30
> >> > >>nameserver 128.97.128.1
> >> > >> 
> >> > >>The first is the ucla nameserver, the second is the CS department
> >> > >>nameserver.  (Of course, both resolve all hostnames to ip's, not just 
> >that
> >> > >>departments...)  Anyway, do you have something like that in your
> >> > >>/etc/resolv.conf ?  If you dont, try putting at least the top line
> there.
> >> > >> 
> >> > >>HTH
> >> > >>Dimi
> >> > >>
> >> > >>
> >> > >>-----
> >> > >>Your attention please everyone, if I could just say a few words... I 
> >would 
> >> > >>be a better public speaker. 
> >> > >>  -- Homer Simpson
> >> > >>
> >> > >>On Wed, 17 Nov 1999, Glenn Glazer wrote:
> >> > >>
> >> > >>> So, I have my system going fine except one problem.  Whenever I type 
> >in a
> >> > >>> website that Netscape doesn't have cached, Netscape tells me that it 
> >can't
> >> > >>> find the server.  However, if I do a nslookup, the lookup works and if
> >> > >>> enter the IP addr instead of the website alias name (e.g., 
> >www.foo.bar),
> >> > >>> then Netscape finds it no problem!  Clearly, I do not want to do
> my own
> >> > >>> lookups for every new website I go to!
> >> > >>> 
> >> > >>> Also pinging a new site doesn't work, but if I do the lookup and
> then a
> >> > >>> traceroute, then the ping works.  Further, other machines on the 
> >network
> >> > >>> (math.ucla.edu) seem to be working fine, so the issue seems local.
> >> > >>> 
> >> > >>> Any suggestions?  I've tried messing about with the /etc/resolv.conf,
> >> > >>> /etc/nsswitch.conf and poking through /var/adm/messages to no avail.  
> >> > >>> 
> >> > >>> Best,
> >> > >>> 
> >> > >>> Glenn
> >> > >>> 
> >> > >>> _______________________________________________
> >> > >>> UCLALUG Linux mailing list - Linux@linux.ucla.edu
> >> > >>> http://linux.ucla.edu/mailman/listinfo/linux
> >> > >>> 
> >> > 
> >> > 
> >> > _______________________________________________
> >> > UCLALUG Linux mailing list - Linux@linux.ucla.edu
> >> > http://linux.ucla.edu/mailman/listinfo/linux
> >> > 
> >> 
> >> 
> >> _______________________________________________
> >> UCLALUG Linux mailing list - Linux@linux.ucla.edu
> >> http://linux.ucla.edu/mailman/listinfo/linux
> >
> >-- 
> >Erik Hovland
> >USC Linux User Group President
> >http://sclug.usc.edu/~ehovland/
> >GnuPG public key: http://sclug.usc.edu/~ehovland/ehovland.gpg
> >
> >_______________________________________________
> >UCLALUG Linux mailing list - Linux@linux.ucla.edu
> >http://linux.ucla.edu/mailman/listinfo/linux
> 
> 
> _______________________________________________
> UCLALUG Linux mailing list - Linux@linux.ucla.edu
> http://linux.ucla.edu/mailman/listinfo/linux
>