Re: [cobalt-users] IP addys

["Greg" <greg@xxxxxxxxxxxx>]

Thanks for taking so much time on this... It is the way they are displayed
on the admin panels on the RaQ3 and I don't have any control over it, like
padding or stripping. If there's any doubt that this may cause problems
later, I won't do it... it's just not that big of a deal to scroll up or
down a little.

Thanks again for taking the time,
Greg


----- Original Message -----
From: "Jeff Lasman" <jblists@xxxxxxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Tuesday, March 14, 2000 9:11 AM
Subject: Re: [cobalt-users] IP addys


> This doesn't work either.
>
> How do I know?  I tried it.
>
> I've got a RaQ2 that's got 209.126.157.77 assigned to it.  I haven't got
> anything answering yet for that domain.  When I traceroute to it, the
> traceroute fails at the router.
>
> I set up a new domain, hostname of www, and domain name of
> jeff.nobaloney.net.  The IP# I used was 209.126.157.077 (note the leading
> zero in the last set of numbers).
>
> I tried to traceroute to the box, using 209.126.157.77 (note, no leading
> zero in the last set of numbers); again, it failed at the router.
>
> I set up another new domain, this time hostname of www, and domain name of
> mike.nobaloney.net.  This time I used 209.126.157.77 (note there's no
> leading zero in the last set of numbers).
>
> I tried another traceroute to 209.126.157.77 (no leading zero).  This one
> succeeded to the box.
>
> I deleted the domain mike.baloney.net, and tried a traceroute (using the
> Windows NT tracert client) to 209.126.157.077 (with the leading zero).  It
> made it all the way to the box (which is still hosting the domain
> jeff.nobaloney.net, with the IP# 209.126.157.077).
>
> I then deleted that domain; then I couldn't traceroute either way.
>
> So I suppose if everyone knows to type in your IP# WITH the leading zero,
> it'll work as long as software implemenations don't change.
>
> However, it's incorrect usage, it's against the RFCs, there's no
> expectation that any system will ever find you, and since nameservers will
> resolve to 209.126.157.77 and NOT to 209.126.157.077, most systems won't
> ever find you.
>
> I wouldn't do it.  If you need to keep a list of domains that lines up
> right, there are two ways to do it. One is to use a completely different,
> hidden, field, for your key field.  Create the field automatically,
> removing the decimals and adding leading zeros when necessary.  Another
way
> to do it is the way I do it: I use MS Access to keep track of domains and
> IP#s.  But when i put them into the box, I DON'T  use the leading zeros.
>
> Jeff
>
> At 11:28 AM 3/14/00 -0800, you wrote:
> >Mostly I want to know just when setting up during admin time. I want the
IP
> >addys to sort correctly, so leading zeros are needed...
> >
> >Currently
> >123.456.789.100
> >123.456.789.102
> >123.456.789.103
> >123.456.789.98
> >123.456.789.99
> >
> >And I would like
> >123.456.789.098
> >123.456.789.099
> >123.456.789.100
> >123.456.789.101
> >123.456.789.102
>
> --
> Jeff Lasman <jblists@xxxxxxxxxxxxx>
>
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users