It's very difficult to get one's own DNS working correctly when you can't
convince your upstream there is a problem... *sigh* If anyone has tested,
we have no reverse DNS for our two net blocks. I'm waiting to see how many
times I have to tell the story. If anyone has a good suggestion for
bringing this subject up with an upstream, I would be happy to
listen...it's never worked for me and I've argued with CRL, AlterNet and
our current upstream (3 different jobs).
At 11:53 AM 1/10/98 -0800, you wrote:
>Mitch Wagers wrote:
>>
>> That was somewhat inclusive, because not all MX records point to the same
>> domain. The point is you don't have www and mail hosts pointed at the same
>> machine unless of course they run all of that software on one machine.
None
>> the less, if you create an MX record for domain.com that points to
>> mail.domain.com and have an A record for mail.domain.com and an A record
for
>> domain.com that points to a webserver, your mail will be routed correctly
>> and you can type "http://domain.com" to get the web site.
>
>We have found LOTS of mailers are broken and don't use MX records
>correctly. For this reason we always make sure the IN A is the
>mail server.
>
>--
>Dale E. Reed Jr. (daler@iea.com)
>_________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.iea-software.com
>
> ----------------------------------------------------------
> NTISP Mailing List listserver@emerald.iea.com
>
>