Re: Running public DNS server on iSeries

[Pete Helgren <Pete@xxxxxxxxxx>]

You are right, the dynamic DNS does require a client but it think it 
will run in PASE (they mention a unix client which *should* run in 
PASE).  I think PASE is required for DNS on the iSeries anyway.  They 
have a perl script and some source code for windows.

Looking at it, you might be able to write your own client.  I might even 
take a crack at it.

Not sure you'd need the client though, unless the iSeries only gets a 
dynamically assigned IP address from your ISP.

Client works great for Windows though.

Pete


Neil Palmer/DPS wrote:

> Pete,
>
> Do you use them for a static or dynamic DNS ?  Their site appears to say 
> you need a client to change the IP address, but of course the client code 
> isn't going to run on a iSeries.
>
> ...Neil
>
>
>
>
> Pete Helgren <Pete@xxxxxxxxxx> 
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 2005/05/11 12:13
>
>
>
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> cc
>
> Subject
> Re: Running public DNS server on iSeries
>
>
>
>
>
>
> We have been using everydns.net and it has been flawless.  A small 
> donation is all it takes to configure as many domains as you want.
>
> It also supports dynamic dns for those folks who can't get a static IP 
> address yet want to host a domain.
>
> If you are looking for simple, cheap and effective DNS service you 
> should check them out as well.
>
>
> Pete Helgren
>
>
> Neil Palmer/DPS wrote:
>
>  
>
> > I think the following is possible, though maybe not advisable.  Any 
> > comments?
> >
> > Have a customer switching ISP's from one who was providing DNS service to 
> >    
>
>  
>
> > one who won't (because the latter has DSL and the former is only ISDN).
> > They only have one system, the iSeries, behind a firewall.  I was 
> > wondering about running a DNS server on the iSeries for their public 
> > domain, and seting the firewall to forward DNS port 53 traffic to the 
> > internal address of their iSeries.  Is this possible?  (May be an issue 
> > there too in that the internal DNS address for their domain should 
> >    
> resolve 
>  
>
> > to a 192.168.x.x address, so maybe that's a showstopper right there). I'm 
> >    
>
>  
>
> > thinking I'd be better off signing them up with one of the free DNS 
> > service providers.
> >
> >
> > Also, DNS on port 53 uses only TCP. not UDP - is that right?
> >
> > ...Neil
> >    
>
>
>
>