Rebooting stops resolving for a while

User, Public public at seajay.com
Tue Jan 6 12:13:02 UTC 2004


Bill,
He is using an example IP address with 55.55.55.55.  At least that is
what I concluded.  As for his problem?  I don't know.
Chris



Christopher P. Jenkins, Senior Consultant

Concordant, Inc.

P:  508-820-3080

F:  508-820-4367

C:  508-241-7415

E:  chris.jenkins at concordantinc.com


-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
Behalf Of bill
Sent: Monday, January 05, 2004 5:39 PM
To: Gary Mayor
Cc: comp-protocols-dns-bind at isc.org
Subject: Re: Rebooting stops resolving for a while

>=20
> Hi,
> When I reboot my server sometimes my domains and mail servers are not=20
> available for an unknown amount of time but after several hours=20
> everything returns to normal and everything can be accessed. The
strange=20
> thing is if after a reboot I try to access the domain or mail server=20
> from my machine at home it doesn't work but if I go somewhere on the
net=20
> and try a ping test from somewhere else in the world it always works.=20
> Can someone take a look at my main zone file and and a client zone
file=20
> and tell me if anything doesn't look right.
>=20
> Main Zone File
> $ttl 38400
> mydomain.com.	IN	SOA	55.55.55.55. mydomain.com. (
> 			2003111224
> 			10800
>                          3600
>                          604800
>                          38400 )
> mydomain.com.	IN	A	55.55.55.55
> mail.mydomain.com. IN	A	55.55.55.55
> smtp.mydomain.com. IN	A	55.55.55.55
> www.mydomain.com.  IN	A	55.55.55.55
> ftp.mydomain.com.  IN	A	55.55.55.55
> mydomain.com.	IN	NS	ns1.mydomain.com.
> mydomain.com.	IN	NS	ns2.mydomain.com.
> mydomain.com.	IN	MX	5 mail.mydomain.com.
> mail.mydomain.com. IN	PTR	mydomain.com
>=20
> Client Zone File
> $ttl 38400
> clientdomain.com.	IN	SOA	abertron01. gary at abertron.co.uk.
(
> 			2003111245
> 			10800
>                          3600
>                          604800
>                          38400 )
> clientdomain.com.		IN	A	55.55.55.55
> mail.clientdomain.com.		IN	A	55.55.55.55
> www.clientdomain.com.		IN	A	55.55.55.55
> ftp.clientdomain.com.		IN	A	55.55.55.55
> clientdomain.com.		IN	NS	ns1.mydomain.com.
> clientdomain.com.		IN	NS	ns2.mydomain.com.
> clientdomain.com.		IN	MX	5 mail.mydomain.com.
>=20
> Basically nothing works from from home computer after I reboot the=20
> server but I seem to be able to access the server from elsewhere after
a=20
> reboot so what on earth is going on here.
>=20
> I'm totaly confused any ideas.
>=20
> Thanks
>=20
> Gary Mayor

	Well....

	Net 55 is assigned to the US Army.  None of their DNS reverse
	maps to the delegation "clientdomain.com".  Have you hijacked
	their address space or are you using it with permission?

	For that matter, the domain, "clientdomain.com" is registered
	to John Deneen, of Villanova, PA.  It does not appear that he
	has delegated any responsibility for this domain to you.  Have
	you hijacked this also?

	I would suggest that you correct your DNS entries to use your=20
	own delegations and cease and desist using others delegations.
	Things will work so much better for everyone.

--bill=09



More information about the bind-users mailing list