Profile

unixronin: Galen the technomage, from Babylon 5: Crusade (Default)
Unixronin

December 2012

S M T W T F S
      1
2345678
9101112131415
16171819202122
23242526272829
3031     

Most Popular Tags

Expand Cut Tags

No cut tags
Friday, June 17th, 2005 09:12 am

Interestingly, our dynamic IP appears not to be as dynamic as Verizon indicated.  We were told that IP addresses were reassigned every 48 hours.  We're currently at about 60 hours without, I believe, a change of IP.

It'll be cool if it turns out to be "effectively static once assigned".

(Which is to say, 48-hour minimum lease time but they won't actually expire the lease while our connection is active.)


Footnote:  I have got to get a new chair that gives me decent back support.  The only thing I have to sit on right now is a wooden stool and it's killing my back.

Friday, June 17th, 2005 07:59 am (UTC)
According to the MCSE "boot camp" course that I took, what you're seeing is actually normal; what theortetically happens is that the device that requests the address from the DHCP server (usually your PC or the router; rarely, the bridge itself) actually tries to renew its lease every 0.5x of the published lease period, so that if you have a theoretical expiration of 48 hours, it will request renewal every 24. The only time you'd actually get a new IP is if you actually were disconnected (PC or router turned off) at the expiration of a lease - in your case, you'd pretty much have to be off-line with the PC or router off/disconnected for more than 24 hours to guarantee a change in IP. Of course, if they have trouble at their end that results in an outage of their DHCP server, all bets are off.

The fixed IP that you can (sometimes) purchase (usually for an extra fee, but some ISPs offer it as part of the core package) is simply a guarantee that they won't assign that IP to anyone else, and that it will accept your router's/PC's demand for that specific IP, rather than forcing DHCP.
Friday, June 17th, 2005 08:25 am (UTC)
That sounds like my experience.

And the "static" IP that I have is assigned by DHCP and is on several mail blacklists. sigh..
Friday, June 17th, 2005 08:40 am (UTC)
Well, if it's a personal account, it actually shouldn't matter much, since in theory you should be going through your ISP's mail servers, rather than running your own or trying to do direct-to-MX mailing. There is at least one DNSBL that specifically lists all known DHCP blocks - because they're DHCP, and shouldn't be running servers - from as many ISPs as they can get the information about.

Of course, if you're having legitimate problems, you'll need to take it up with your ISP (ComCast? XO? UUNet?), who have probably been ignoring spam reports for years... :(
Friday, June 17th, 2005 08:42 am (UTC)
nono, you misunderstand. I'm being sold a "static" ip that is assigned by DHCP, and some blacklists have it because of that fact, so I have to relay through my upstream mail server. I'm aware of the issue you described.
Friday, June 17th, 2005 08:42 am (UTC)
Oh. And...

kitty! :)
Friday, June 17th, 2005 08:43 am (UTC)
Verizon, unfortunately, does not offer static (or assigned) IP on residential service, PERIOD.

In the past, on real ISPs, we've typically had a /28 or /29 subnet allocated to us, with reverse lookup delegated to our nameserver.
Friday, June 17th, 2005 09:44 am (UTC)
Ummm... you need to mess with your dnsalias stuff. Right now it's giving out a non-routable address...

I've found that having a permanent colo (or at least a shared server) somewhere for mail and such tends to work very well... or barring that, maybe a Fastmail account... yes, it costs a bit more, unless you can cut a sweetheart deal with somebody... but if you can wangle a colo on a real T-1 or something (NOT DSL or cable) then you can get to it anytime, anywhere, whether or not Verizon commits an oops.... which they will...
Friday, June 17th, 2005 09:55 am (UTC)
I know. It hasn't been updated since we moved. I'll have babylon5 up in a couple more days and move the ddclient config over to yama.
Friday, June 17th, 2005 09:50 am (UTC)
I have got to get a new chair that gives me decent back support.  The only thing I have to sit on right now is a wooden stool and it's killing my back.

Hmmm.... Interesting. I see that no one has hollered at you, about your back...as yet. Just geeky type comments. All of which are wonderful. But... If you don't get yourself a good chair, you're gonna' be flat on your back. :-( And not enjoying all the geeky stuff, much.

Friday, June 17th, 2005 09:55 am (UTC)
We intentionally did not bring my old office chair with us because it was shot. A new one is on the to-do list.