[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] DNS Expert - Proficiency in NameServerAdministration



Jeff Lasman wrote:
> 
> Sounds like an open-ended question if I ever heard one <smile>.
> 
> If you're looking to ask questions, ask away.

Well then, if I may...

We have a Qube on site to handle webserving and mail.  I also want it
to provide local DNS.  Our ISP provides primary DNS for the site; we
are on a permanent connection to them.  When I say "local DNS", I mean 
that I don't want the whole world to be able to resolve dogbert.san.com,
(the machine I'm typing on) but I do want them to be able to get at 
www.san.com, (the Qube) and our ISP does that.  However, within these 
four walls I do want "catbert" to be able to query the Qube and get the 
IP address of "dogbert".

I've set up the Qube as a "secondary" DNS server, but it doesn't all
seem to be doing what I want it to.  The Qube is unable to resolve
either dogbert.san.com or just plain dogbert.  A Linux machine can
resolve both.  An NT box can resolve dogbert.san.com but not just 
plain dogbert.

If I make the Qube a primary server, the ISP's DNS server and the Qube 
go haywire and generate vast amounts of traffic, but I do get things
resolving nicely.

I've got the client machines configured to query first the Qube, then the
ISP's DNS server.

Where am I going wrong?  Have I got this all completely wrong?