Greetings list, Bind 8 issue:

[Michael Kjorling]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, I would say that it's rather obvious that this is _some_ kind of
DNS problem. In this case, most likely a mismatch between forward and
reverse DNS. (What a reverse lookup returns should be lookupable and
yield the original IP address. A lot of programs do checks like that.)

Since when you add the offending IPs to /etc/hosts (thus making them
resolve to something) everything works fine, why don't you just add
them to your DNS servers and make sure that 10.222.206.in-addr.arpa is
properly delegated to you?


Michael Kjörling


On Oct 18 2001 10:03 -0400, Drew J. Weaver wrote:

>          206.222.10.x resolves, they all have reverses[I think its worth
> noting that they have NEVER had forwards(i.e. a records et cetera) and this
> is a recent problem that only started about a week ago] If I put the
> 206.222.10.x range in /etc/hosts on the mail server it works perfectly, but
> obviously that is not a solution it's the sysadmin's duct tape. I've been
> mulling over my named.conf and the zones for the set of reverses for the
> last few days and I see nothing wrong with any of it.
>
>          Any insight here would be most helpful, thank you for your time and
> consideration.
>
>          -Drew

- -- 
Michael Kjörling  --  Programmer/Network administrator  ^..^
PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e   \/
Internet: michael at kjorling.com -- FidoNet: 2:204/254.4

"There is something to be said about not trying to be glamorous
and popular and cool. Just be real -- and life will be real."
(Joyce Sequichie Hifler, September 13 2001)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Public key is at http://michael.kjorling.com/contact/pgp.html

iD8DBQE7zuVgKqN7/Ypw4z4RAjVhAKCE1Uin48xyn/2xYFa42UQN6+jbBQCffrBY
35PibbTfm8roToJC0BstB7w=
=/U7U
-----END PGP SIGNATURE-----