|
We have been using a 170 for a secondary DNS server in our backup site. Yes it is hit occasionally and works. It is NAT'd behind the firewall with a public IP translated to a private IP. You need to open up both UDP and TCP port 53. Chris Bipes Information Services Director CrossCheck, Inc. -----Original Message----- 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? >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.