Bug 17712
| Summary: | Some outside networks are unable to resolve the addresses listed in DNS server running on the server. | ||
|---|---|---|---|
| Product: | Base System | Reporter: | rajeshn <rajeshn> |
| Component: | i386 | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
rajeshn
2000-03-31 16:50:01 UTC
I have no idea how to solve your problem as posted, esp. since you don't include any useful configuration information. However, I see you're using 2.1.7-RELEASE. This is *incredibly* old. You should probably consider upgrading to a non-ancient version as your first step. The security holes alone are a huge problem with a release that old. See http://www.freebsd.org/ for information on getting upgraded to a newer version. Daniel This might be an outdated problem for you now, but I thought I'd put my two cents in on the PR.. Problem 1: tiki.theeddy.com (NS #3 for cybertech-usa.com and cssl-usa.com according to Network Solutions) isn't responding to nameservice queries at the moment. > server tiki.theeddy.com Default Server: tiki.theeddy.com Address: 204.186.117.1 > cybertech-usa.com Server: tiki.theeddy.com Address: 204.186.117.1 *** tiki.theeddy.com can't find cybertech-usa.com: No response from server Problem 2: tiki.theeddy.com isn't listed by dns.cssl-usa.com as an NS for cybertech-usa.com. This probably isn't critical, especially given #1. Problem 3: cybil.theeddy.com can't look up any addresses in cssl-usa.com, which is probably fairly bad for you. This is likely the source of your 'sometimes' problems, since the world will randomly pick one of the listed nameservers for cssl-usa.com, only one of which works (see #1). [snippage] Domain Name: CSSL-USA.COM Administrative Contact, Technical Contact, Zone Contact: Glamb, Larry (LG242) tes@THEEDDY.COM TheEddy Services P.O. Box 36 Upper Black Eddy, PA 18972 610 791 9931 (FAX) 610 791 9931 Billing Contact: Network Administrator (NA177-ORG) network@CT-YARDLEY.COM CyberTech International CyberTech International Corp. Attn L. Glamb Eight Neshaminy Interplex, Suite 209 Trevose, PA 19053 US 215 244 5000 Fax- 215 244 5099 Record last updated on 22-Oct-1997. Record expires on 05-Jul-2000. Record created on 04-Jul-1997. Database last updated on 18-Apr-2000 04:35:42 EDT. Domain servers in listed order: DNS.CSSL-USA.COM 151.197.92.24 CYBIL.THEEDDY.COM 151.197.92.27 TIKI.THEEDDY.COM 204.186.117.1 earth> nslookup Default Server: dns1.anet-stl.com Address: 209.145.150.10 > server cybil.theeddy.com Default Server: cybil.theeddy.com Address: 151.197.92.27 > set query=any > cssl-usa.com Server: cybil.theeddy.com Address: 151.197.92.27 *** cybil.theeddy.com can't find cssl-usa.com: Server failed In summary, this isn't really a FreeBSD problem, and the FreeBSD PR should be closed. I'd be happy to provide any other assistance I can outside this forum, though. Jason Young Access US(tm) Chief Network Engineer PR originator says this problem has gone away, but is looking into the issues above. This PR can be closed. Jason Young Access US(tm) Chief Network Engineer ----- Thank you very much for your time. We do not experience the problem now a days. I'll look into the issues listed. Thanks once again Rajesh Nair, Network Administrator, Cybertech Systems Inc. E-mail : rajesh.nair@cybertech.com -----Original Message----- From: Jason Young [mailto:jyoung@accessus.net] Sent: Tuesday, April 18, 2000 8:04 PM To: 'freebsd-gnats-submit@FreeBSD.org'; 'rajeshn@cybertech.com' Subject: Re: i386/17712: Some outside networks are unable to resolve the a ddresses listed in DNS server running on the server. This might be an outdated problem for you now, but I thought I'd put my two cents in on the PR.. [snip] State Changed From-To: open->closed Audit trail indicates problem was with user's DNS setup, not a problem with FreeBSD. Audit trail asks that the PR be closed twice. I'm closing it. |
