Re: Static IP and fully qualified domain names

2003-11-25 Thread Roman Neuhauser
# [EMAIL PROTECTED] / 2003-11-21 16:35:59 +0100: > Hi! > > This question is inspired by a recent mail on this list. > > My ISP was so nice to give me a domain name (pukruppa.net) and > assign it statically to an IP (213.146.114.24). > [So now everybody in the world can telnet pukruppa.net and cra

Re: Static IP and fully qualified domain names

2003-11-22 Thread Cordula's Web
> >My ISP was so nice to give me a domain name (pukruppa.net) and > >assign it statically to an IP (213.146.114.24). > >[So now everybody in the world can telnet pukruppa.net and crack > >my private machine :-) ] > > > >>From reading manuals one should think, that now I could give my > >machines n

Re: Static IP and fully qualified domain names

2003-11-21 Thread Scott W
Peter Ulrich Kruppa wrote: Hi! This question is inspired by a recent mail on this list. My ISP was so nice to give me a domain name (pukruppa.net) and assign it statically to an IP (213.146.114.24). [So now everybody in the world can telnet pukruppa.net and crack my private machine :-) ] From r

Re: Static IP and fully qualified domain names

2003-11-21 Thread Peter Ulrich Kruppa
On Fri, 21 Nov 2003, Matthew Seaman wrote: > On Fri, Nov 21, 2003 at 10:54:21AM -0500, Marty Landman wrote: > > At 10:42 AM 11/21/2003, Cordula's Web wrote: > > >> > > >> From reading manuals one should think, that now I could give my > > >> machines names like one.pukruppa.net, two.pukruppa.net,

Re: Static IP and fully qualified domain names

2003-11-21 Thread Marty Landman
At 12:25 PM 11/21/2003, Matthew Seaman wrote: Lets assume that the domain you're using in your intranet is 'example.com' and you've chose to use the 192.168.0.0/24 subnet for all of your IP numbering. . Wow, thanks for all the detail! I will try to put the info to use and post back how it go

Re: Static IP and fully qualified domain names

2003-11-21 Thread Matthew Seaman
On Fri, Nov 21, 2003 at 10:54:21AM -0500, Marty Landman wrote: > At 10:42 AM 11/21/2003, Cordula's Web wrote: > >> > >> From reading manuals one should think, that now I could give my > >> machines names like one.pukruppa.net, two.pukruppa.net, etc... > >> and all these would be reachable via inter

Re: Static IP and fully qualified domain names

2003-11-21 Thread Marty Landman
At 10:42 AM 11/21/2003, Cordula's Web wrote: > > From reading manuals one should think, that now I could give my > machines names like one.pukruppa.net, two.pukruppa.net, etc... > and all these would be reachable via internet - but they aren't. > The only one that can be accessed is pukruppa.net .

Re: Static IP and fully qualified domain names

2003-11-21 Thread Cordula's Web
> My ISP was so nice to give me a domain name (pukruppa.net) and > assign it statically to an IP (213.146.114.24). > [So now everybody in the world can telnet pukruppa.net and crack > my private machine :-) ] > > From reading manuals one should think, that now I could give my > machines names lik

Re: Static IP and fully qualified domain names

2003-11-21 Thread Steve Bertrand
> >From reading manuals one should think, that now I could give my > machines names like one.pukruppa.net, two.pukruppa.net, etc... > and all these would be reachable via internet - but they aren't. > The only one that can be accessed is pukruppa.net . If you have control of the DNS zone, then you

Re: Static IP and fully qualified domain names

2003-11-21 Thread Jake Stride
Probably because there is no DNS set up for the domain. Have you set up the required names on NS.KAMP.NET, NS2.KAMP.NET, NS2.KAMPNIC.NET? Unless there are DNS records they won't resolve to IP Addresses, perhaps your isp would be kind enough to do that for you too. Jake On Friday, Nov 21, 2003