On Thu, 13 Sep 2001, Pete Turnbull wrote:
> On Sep 13, 13:05, Bill Bradford wrote:
>
> > DNS be brokie.
>
> Um, not necessarily. [...] subatomix.com is indeed a valid domain
> name, [...] whose nameserver (ns1.domaindiscover.com) will give you
> the A record and MX record. [...] However, there's no necessary
> correspondence between the domain name registrar, DNS provider for
> forward lookups, and ISP who provides the actual connection and
> address (usually also the DNS provider for reverse lookups).
Yes, that is what is going on here. I've used DomainDiscover's facilities
to point subatomix.com at the IP of my router (one of those LinkSys BEFSR
units), behind which hides my home network. The router forwards a few
ports, including 25, to my server box on the inside.
I've got a cable modem connection with DHCP-assigned IP addresses. My
situation is made possible by the fact that DHCP setup here always gives
you the same IP address. Unfortunately, the setup also prevents reverse
lookups from working.
> (1) turn off the double check,
He shouldn't have to do that just to make my mail work.
> (2) have Jeffrey's machine give its mmcable.com name when sending mail
I'll try to get that set up.
> (3) have Jeffrey's machine relay mail through mmcable's server
I don't want to do that. Their smtp servers have a nasty habit of
randomly delaying mail by somewhere between 1 and infinity days.
> (4) persuade mmcable to include his properly registered domain name in
> their DNS.
Ha! That would be the day! They are most definitely not the friendliest
people in town. I'm lucky they don't just forbid their subscribers from
running servers at all.
Someday, when I have an improved cash flow, I'll get something a little
better for my purposes. For the moment, though, I'm stuck with what I
have.
--
Jeffrey S. Sharp
jss_at_subatomix.com
Received on Fri Sep 14 2001 - 17:13:13 BST