On Fri, Mar 22, 2002 at 10:22:10PM +0100, Tony Earnshaw wrote:
| fre, 2002-03-22 kl. 22:08 skrev dman:
|
| > I just got a public IP again. However, at the moment, there is no
| > reverse entry for it. (once I figured that out I understood why SF is
| > temporarily rejecting a certain outgoing message) I also just read
| > the discussion between Terry and Phil regarding reverse DNS, which
| > made me wonder ...
|
| dman,
|
| Take a look at the ip numbers below.
|
| I don't have to tell a bright fellow like you, do I? Or who does you DNS
| for you?
| dman.ddts.net. 49 IN A 169.254.0.0
DOH! You checked at a bad time (moment). See
www.ddts.org to see how
the forward dns works in this setup.
DDTS is "Dynamic Dns Tool Service". There's a daemon that runs on my
machine to tell the nameserver what my IP is at the moment. If I'm
not "online" (for whatever reason the watchdog timer on the server
goes off) I get that unroutable IP.
Unfortunately, at least for that machine, the server seems to timeout
way too much today and yesterday. I made a script to loop infinitely,
and (checking every 15 seconds) if it sees that IP in my forward
lookup it starts spawning (1 per 15 seconds) the program that tells
the daemon to request "online" status. It was looking good for quite
a while ...
As for Terry's comment about the secondary MX, I know it's like that.
It's a 486 with 8MB RAM I left at home to masquerade for my dad and my
brother. It isn't too hard for it to get bogged down and then the
kernel starts killing things. It has more problems than a bad forward
dns entry right now. I don't know why it died this time (I added the
load average checking in exim last (first) time that happened). My
dad and brother have rebooted the machine, but they say it gets stuck
at "Configuring network interfaces". The DHCP daemon isn't running,
but it responds to pings and masquerades statically configured hosts
fine. The machine is about 300-400 miles away, so I can't even check
a log or anything. [1]
-D
[1]
I can ping it because even though the address is obtained via
dhcp, in practice it hasn't changed and I know what it is.
--
Microsoft encrypts your Windows NT password when stored on a Windows CE
device. But if you look carefully at their encryption algorithm, they
simply XOR the password with "susageP", Pegasus spelled backwards.
Pegasus is the code name of Windows CE. This is so pathetic it's
staggering.
http://www.cegadgets.com/artsusageP.htm
