DNS stopped propagating

[Tim Maestas]

	Without telling us what the domain is in question, we
	can only guess (and lots of people probably won't
	feel like wasting their time guessing).  Tell us the
	domain and someone will likely be able to tell you
	what is wrong.

	And yes, it is ok for secondaries and primaries to
	have the same serial.  In fact, they *should* have
	the same serial, unless the master has just been
	updated and the slaves have not zone transfered the
	zone yet.  If you have slaves with a *higher* serial
	than the master, then you have a problem, as the slaves
	will then never zone transfer the zone, thus never
	picking up changes made on the master (maybe this is
	your problem?)

-Tim


On Thu, 11 Jan 2001, Andrew Buenaventura wrote:

> 
> We are currently hosting some sites in our servers.  We told the owners of
> the domains we are hosting to point the primary DNS to our IP and the
> secondary DNS to our ISP's IP.  We requested our ISP to host the secondary
> DNS but it was only acted upon 5 days ago.  After they began hosting our
> secondary DNS, one of the domains we are hosting complained that some A and
> CNAME records are not being seen on the internet.  We did an NSLOOKUP and
> found out that there are some DNS servers that can recognize ALL the said A
> and CNAME records, some servers can only see a portion of it, while some
> can't see the domain at all.  I have already appended the SERIAL and
> restarted BIND and nothing has happened yet.  What do you think is wrong?
> Another thing, is it okay for the primary and the secondary DNS servers to
> have the same SERIAL?  
> 
>