DNS stopped propagating

[Mark.Andrews at nominum.com]

$ORIGIN earthandstyle.com.
@			1D IN SOA	localhost. noc\@infinitymalls.com (
					2000112005	; serial
					8H		; refresh
					4H		; retry
					5w6d16h		; expiry
					1D )		; minimum

	The origin field should be the name of the machine that is
	the master for the zone, i.e. localhost is wrong.

	The mail contact should be noc.infinitymalls.com.  The
	period at the end of the first label becomes a '@' when
	you send mail.  Also the address needs to be entered as a
	fully qualified domainname. i.e. "noc.infinitymalls.com."
	not "noc.infinitymalls.com", note the final period as what
	you have in the zone now is interpereted as
	"noc at infinitymalls.com.earthandstyle.com".

			1D IN NS	203.177.19.12.

	NS records refer to hostnames not IP addresses, also all
	the nameservers should be listed.  This will be causing
	most of your problems.

			1D IN A		203.177.19.6
			1D IN MX	5 soran1.pacific.net.ph.
			1D IN MX	10 soran.pacific.net.ph.
ftp			1D IN CNAME	www
smtp			1D IN A		210.23.234.90
www			1D IN A		203.177.19.6
pob1			1D IN CNAME	po
po			1D IN A		210.23.234.81
@			1D IN SOA	localhost. noc\@infinitymalls.com (
					2000112005	; serial
					8H		; refresh
					4H		; retry
					5w6d16h		; expiry
					1D )		; minimum

;; Received 11 answers (11 records).
;; FROM: drugs.dv.isc.org to SERVER: 203.177.19.12
;; WHEN: Thu Jan 11 22:05:27 2001
> 
> my sincerest apologies to you Tim and to all the members of this list.  the
> domain is earthandstyle.com.  the fqdns that i am having problems with are
> the ff:
> 
> po.earthandstyle.com and pob1.earthandstyle.com with an IP of 210.23.234.81 
> 
> smtp.earthandstyle.com with an IP of 210.23.234.90 
> 
> these three are hosted in another ISP.
> 
> www.earthandstyle.com is hosted in our servers and other ISPs can't also see
> this
> 
> -----Original Message-----
> From: Tim Maestas
> To: Andrew Buenaventura
> Cc: 'bind-users at isc.org'
> Sent: 1/11/01 2:03 PM
> Subject: Re: DNS stopped propagating
> 
> 
> 
> 	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?  
> > 
> > 
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com