|
On 14/04/2006, at 7:30 AM, James H H Lampert wrote:
Something is definitely wonky. Is there some other DNS resolution protocol besides UDP on Port 53?
TCP can be used also.
Is there some other setting that would screw up DNS?
Your default route could be wrong.
Is there some setting in our Linksys router's firewall that would allow PCs to do DNS resolution, but not the 400s?
Use NSLOOKUP on OS/400 to verify the DNS behaviour. Type NSLOOKUP on command line. Press Enter. Type Help, press Enter. Read. Something like: NSLOOKUP<enter> www.google.com<enter> should show something like: > www.google.com Server: gryphon.flybynight.com.au Address: 192.168.0.1 Nonauthoritative answer: Name: www.l.google.com Addresses: 66.102.7.104, 66.102.7.147, 66.102.7.99 Aliases: www.google.comor give you hopefully helpful error messages. NOTE: Your DNS server name and IP address will be different from mine but the answer should be the same.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.
midrange.com
