It was the other server that needed my IP address to allow me access. I think I worded that badly.On 11/15/05, Nick Rout <
[EMAIL PROTECTED]> wrote:On Tue, 15 Nov 2005 14:35:59 +1300Olwen Williams <
[EMAIL PROTECTED]> wrote:> From my point of view I asked about a static IP address because I was> l
On Tue, 15 Nov 2005 14:35:59 +1300
Olwen Williams <[EMAIL PROTECTED]> wrote:
> From my point of view I asked about a static IP address because I was
> looking at doing some scripting for someone who required a static IP
> address.
>
> I think that allowing access to another server could much more
Given that IPV6 is about to burst onto the scene[1], typing in a domain
name is going to be a lot quicker than an IP address!
Steve
[1] And has been since before the millenium!
On Tue, November 15, 2005 2:35 pm, Olwen Williams wrote:
> From my point of view I asked about a static IP address bec
>From my point of view I asked about a static IP address because I was looking at doing some scripting for someone who required a static IP address. I think that allowing access to another server could much more easily be done by IP address, than other means.
On 11/15/05, Steve Holdoway <[EMAIL PR
It's never happened to me, and I do run one.
Good point, although you'll only lose mail if the new owner of your old IP
also runs a mail server. I'm updating no-ip every 5 minutes - you can
screw that down to 1 minute if you wish. I think I may run the update
process on my mail server though - it
> What does a static IP address give you that no-ip or dyndns can't? I
> certainly wouldn't pay for one!
Not much, but you might care about it. You can't run a mail server on
dyndns without risking to lose mail or have it delivered to someone else
while your DNS catches up with your new IP. You're
