On Sun, 29 Oct 2000, Zero Piraeus wrote:
> Hey:
>
> Just to let everyone who's offered any input know that my ISP have
> finally accepted that the fault is theirs. They had the CNAME entry set
> to the IP of an account I used to have with them a few months ago.
>
> They now reckon to have sorted it, and I'll know whether that's the case
> when their DNS servers refresh at 0400GMT tonight.
They can't do an immediate update? Sounds like a firm with too much red
tape and procedure, and not enough know-how. When we setup mail or
other DNS records for a client, we refresh our servers immediately. Now
of course, other nameservers not under our control may cache previous
data and not update immediately, but we keep the appropriate SOA values
set to try to keep the cache time to no more than an hour.
> Thanks to everyone who offered help - especially Jerry, whose advice led
> me to start messing about with "telnet <host> 25", "host", "traceroute"
> and "nslookup" until I discovered their error. You might be interested
> to know, Jerry, that the looping when I'm disconnected, rather than
> timing out, is apparently a matter of policy on their part.
Well, if you are on a dialup, thats actually quite normal and not so
much due to policy but simply how IP routing works.
The 'global' routes for the network your address is part of certainly
remain up (since the rest of your ISP is in there), but your ISP has no
route to you (due to your not being connected and all). So it routes to
your ISP, which then probably routes it to the closest router or modem
rack to you, which then doesnt know how to get to you, and it follows
the default route back out (and begins the loop, since that router
sends it right back trying to get to you).
>
> -[z].
>
> --
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
--
