More CName questions...

[Kelly Witherbee]

Hello again,

A few days ago I posted a question about cnames and customers not getting to
our sites.  Thanks to all the good advice!  We changed our serial numbers on
all our zone records and asked the person who hosts our secondary dns server
to get rid of our old info so the server would pick up our new serial
numbers.  I would like to check to make sure that the numbers are now in
sync, but when I do a dig of type SOA I only get the serial number of our
server not of our secondary (even though the name of the secondary does show
up).  What am I doing wrong?

Thanks,
Kelly

-----Original Message-----
From: Joe Simmons [mailto:joe at gryphon.net]
Sent: Wednesday, February 07, 2001 1:04 PM
To: Kelly Witherbee
Subject: Re: Customers can't get to sites set up as cnames


Well, both servers are now reporting the same serial number, so I'm assuming
you've gotten this fixed.  The 21 was showing up in the output of a dig
querying the server for an SOA.

Joe
----- Original Message -----
From: "Kelly Witherbee" <kwitherbee at recruitingsoftware.com>
To: "Joe Simmons" <joe at gryphon.net>; <bind-users at isc.org>
Sent: Wednesday, February 07, 2001 11:59 AM
Subject: RE: Customers can't get to sites set up as cnames


> Joe,
>
> Thanks for the help...
>
> NS1.RSLLC.com is indeed our primary server.  I asked my senior guy if this
> was the case and he said that we do increase the serial number everytime
we
> make an addition.  In fact, in my zone file, I show a serial number of
> 20010020601...So why do you see a SN of 21?  How did you find that number?
>
> Thanks again...looking forward to more info.
>
> Kelly
>
>
> -----Original Message-----
> From: Joe Simmons [mailto:joe at gryphon.net]
> Sent: Wednesday, February 07, 2001 12:41 PM
> To: Kelly Witherbee; bind-users at isc.org
> Subject: Re: Customers can't get to sites set up as cnames
>
>
> 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
> >
> >
> >
> >
>
>