problems with a certain domain

[Chapman, Matt]

I am not responsible for the domain but I am having to deal with the
mistakes it has.  I have forwarded some dlint stuff to the hostmaster
but nothing yet.  I just thought it was weird that one name server was
able to send mail to it and another was not and they each had different
output from dig.

-matt chapman

> -----Original Message-----
> From: Pete Ehlke [mailto:pde at ehlke.net]=20
> Sent: Thursday, April 18, 2002 10:51 AM
> To: Chapman, Matt
> Cc: bind-users at isc.org
> Subject: Re: problems with a certain domain
>=20
>=20
> On Thu, Apr 18, 2002 at 10:15:23AM -0400, Chapman, Matt wrote:
> >=20
> > When I do a dig from my 9.1.3 box I get the following for=20
> the domain:
> >=20
> > ;; AUTHORITY SECTION:
> > cityoforlando.net.      170371  IN      NS
> > GATEKEEPER.CI.ORLANDO.FL.US.
> > cityoforlando.net.      170371  IN      NS     =20
> NS1.CI.ORLANDO.FL.US.
> >=20
> > When I do it from another server I own that is on a totally=20
> different=20
> > network I get the correct entries:
> >=20
> > cityoforlando.net.      37459   IN      NS=20
> beautiful.ci.orlando.fl.us.
> >=20
> > I apologize for the length of this message.  But I also=20
> want to note=20
> > that running dlint against the domain cityoforlando.net reports a=20
> > bunch of errors.  I can query the MX record from the last=20
> server but=20
> > not the first and that is the biggest issue for me.  Mail is not=20
> > working to this domain.  As far as I can tell all other domains are=20
> > fine.  Is 9.1.x more strict in it's dealings with other DNS=20
> servers? =20
> > Any ideas would be great.
> >=20
>=20
> Are you responsible for this domain? The first thing that=20
> needs to be corrected is that the two servers to which this=20
> domain is delegated from gtld-servers.net show the same=20
> serial number, but return different data. Either they're=20
> being updated individually and the administrator changed the=20
> data on one and not the other, or the administrator updated=20
> the zone file and failed to increment the zone serial number.
>=20
> The second thing that needs to be addressed is the mismatch=20
> between what you say is the "correct" NS record and the=20
> delegation from the .net servers.=20
>=20
> There may be other issues with this zone, but correcting=20
> those two errors will get you on the right path.
>=20
> -Pete
> --=20
> "religious fanatics are not part of my desired user base."=20
> - djb at cr.yp.to
>=20