That won't do any good.  Their DHCP servers (in Anthem) return three IP's:
a 192.168.x.x address, which routes but does not respond, plus the other 
two mentioned below.  Last September (or so), the first DNS failed.  Then
the second one failed.  I confirmed this with ethereal.  I called them,
and the CSR politely took my complaint.  Later that day, a supervisor
called me back to explain failover - if the first one fails, it will
roll over to the second name server.  "Yes," I said, "but your second name
server has failed also."  It was down for over four days.  I set up my old
Sparc box (Solaris 7 - see, I use UNIX as well as Unix) as a DNS and got 
back to work.  About once per week I would check on the name servers, and 
the primary NEVER CAME BACK UP!!!  (Never being defined as until Christmas).

There's a reason they lost their exclusive contract in Anthem.  Something
about poor QoS maybe?  You can view my notes here: http://georgetoft.com/qwest

If you read my notes, you will see the futility in dealing with them.

George


Matt Alexander wrote:
> 
> Try changing the nameserver entries to different DNS servers, such as:
> 
> nameserver 12.127.16.68
> nameserver 12.127.17.72
> 
> That should solve your problem.  Then give Qwest a nasty phone call and
> tell them to fix their name servers and to also close some of those extra
> ports as well.  Sheesh.  Both of their servers are completely unresponsive
> to me when doing lookups.
> ~M
> 
> On Wed, 15 May 2002, Frank Mandato wrote:
> 
> > Here is the resolv.conf the way it set up
> >
> >
> > domain qwest.net
> > nameserver 206.80.192.1
> > nameserver 204.147.80.81
> > search qwest.net
> >
> >
> >
> > Matt Alexander wrote:
> >
> > > What does /etc/resolv.conf say?
> > >
> > > On Wed, 15 May 2002, Frank Mandato wrote:
> > >
> > > >    I can not access any website with their FQDN, however I have no
> > > > problem getting anywhere when I use the numeric IP addresses.
> > > >
> > > >   I had to change my server name to its numeric IP address in order to
> > > > send or receive mail.
> > > >
> > > >   I am not running any DNS servers on my machine, sometimes I can use
> > > > domain names, sometimes I can't. I am with qwest ( not much longer ) and
> > > > I have a domain parked at zoneedit.com that I use on this machine as a
> > > > test bed.
> > > >
> > > >   I have no problems pinging IP addresses, but can't ping domain names.
> > > >
> > > >   My distro is RH 7.2 kernel 2.4.9 and I am using a Netgear NIC.
> > > >
> > > >   Anyone have any ideas what I did wrong??
> > > >
> > > >   TIA
> > > >
> > > >   FrankM
> > > >
> > > > ________________________________________________
> > > > See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail.
> > > >
> > > > PLUG-discuss mailing list  -  PLUG-discuss@lists.plug.phoenix.az.us
> > > > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> > > >
> > >
> > > ________________________________________________
> > > See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail.
> > >
> > > PLUG-discuss mailing list  -  PLUG-discuss@lists.plug.phoenix.az.us
> > > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >
> > ________________________________________________
> > See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail.
> >
> > PLUG-discuss mailing list  -  PLUG-discuss@lists.plug.phoenix.az.us
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >
> 
> ________________________________________________
> See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't post to the list quickly and you use Netscape to write mail.
> 
> PLUG-discuss mailing list  -  PLUG-discuss@lists.plug.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss