Re: Domain Name routing -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Yes.  DNS is what translates names to ip address.

DHCP jsut hands out IP addreses to computers that ask for them.  DHCP does
NO name to ip translation.

Either setup DNS on the as/400 or setup BIND on a linux machine.

The other option is to use your ISPs DNS server.  You would have to open the
appropriate ports on your firewall so queries can go to the internet.

Either way you will have to open up ports.  The difference is:

a) internal DNS server.  You configure your firewall to only let the DNS
server pass through on DNS queries.  It caches all requests.  You have local
users query your internal DNS server.

b) open the firewall and let all local users query your ISPs DNS server.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Justin Houchin" <justin@RELIATEK.COM>
To: <midrange-l@midrange.com>
Sent: Tuesday, July 30, 2002 11:20 AM
Subject: RE: Domain Name routing


> No I do not have an internal DNS Server. Do I need to set one up? Should
> I setup the 400 as a DNS Server?

This mailing list archive is Copyright 1997-2025 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.