-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 J.P. Trosclair wrote:
> SBC Global's ns1.swbell.net does answer with the appropriate IP address, > but neither our companies name servers or my local dns on my home > network can resolve adsl-99-29-103-142.dsl.hstntx.sbcglobal.net. I > restarted named on my local network (cleared it's cache) and now it > resolves. This behavior can be expected when dealing with dynamic dns > updates, in other words, the updates do not propagate across the > internet instantly. Oh, dear! I'm not sure what, if anything, I can do about this, but thanks to you all for the response(s). Maybe a non-caching name server might help. I'm thinking it's getting to be time to turn reject_unknown_sender_domain into a full reject instead of just a warning, but if DNS isn't working quite right. Glad to know it isn't Postfix, though... - -- Glenn English g...@slsware.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknflfgACgkQ04yQfZbbTLa7mgCgnfbeDypMg9Etd9FwwYroZe5z OIYAoI3UDQrQb9EvaOKkjz3OXP/hqHxW =zEXd -----END PGP SIGNATURE-----
