Customers can't get to sites set up as cnames

[Kelly Witherbee]

It's definatly an NT ported version of Bind, but the server itself is NT,
not 2000.  I'll check in to that, but we've had the secondary DNS server at
Neptune for quite some time (ie...before this started to happen).

Thanks!

Kelly

-----Original Message-----
From: Chris Babcock [mailto:cbabcock at surveysavvy.com]
Sent: Wednesday, February 07, 2001 12:57 PM
To: Joe Simmons
Cc: Kelly Witherbee; bind-users at isc.org
Subject: Re: Customers can't get to sites set up as cnames


The server at NS1.RSLLC.COM also appears to be a windows server of some
flavor.  Windows 2000 DNS by default does not allow zone transfers.  You
set NS1 to permit zone transfers to the secondary server at
NEPTUNE.UNN.COM.

On Wed, 7 Feb 2001, Joe Simmons wrote:

>
> Kelly:
>
> The problem is your two nameservers aren't giving out the same
information.
> One server,  NEPTUNE.UNN.COM, has a SN of 2820253617 and the other,
> NS1.RSLLC.COM has a SN of 21.  I'm guessing from the behavior that you are
> describing that NS1.RSLLC.COM is your primary... if that is the case, your
> secondary will never pick up the new zone.  You need to increase your
serial
> number on the primary to be higher than 2820253617.
>
> Joe
> I speak for no one.
>
> ----- Original Message -----
> From: "Kelly Witherbee" <kwitherbee at recruitingsoftware.com>
> To: <bind-users at isc.org>
> Sent: Wednesday, February 07, 2001 10:11 AM
> Subject: Customers can't get to sites set up as cnames
>
>
> >
> > Hello,
> >
> > I'm a newbie DNS person looking for some help.  We have a web-based
> product
> > that we set up for customers and the URL for each individual customer is
> > customer.domain.ext.  These are set up as cnames to our main site,
> > www.recruitingcenter.net.  In the past, our new customers have had no
> > problems getting to their sites.  Starting recently, they've had
> > intermittent problems accessing these "virtual" domains.  We have
probably
> > close to 100 cnames set up under the recruitingcenter.net domain.  Old
> > customers don't have any problems (example:
> > techpartners.recruitingcenter.net), but new customers can *sometimes*
see
> > their sites and sometimes not (example:  flextime.recruitingcenter.net).
> Of
> > course, customers on AOL can't get to our newest ones...but that's
really
> no
> > big shocker.  I am guessing that the problem is that their ISPs haven't
> > cleared their DNS cache in a while, but the thing that gets me is that
we
> > have never had this problem in the past.  Do we have too many cnames set
> up?
> > Help!
> >
> > Thanks,
> > Kelly
> >
> >
> >
> >
>
>
>