Hello,

Our DNS server runs on a NW 6.5 SP4 server, and uses named.nlm ver
6.04.13, dated 9/2/2005 (not the original version - changed during
course of troubleshooting). It is used to resolve a handful of
internal addresses, and mostly forwards to our ISP's name servers.

Most forwarded lookups are taking way too long, and we have even had a
few instances of undeliverable mail that I think may be attributed to
lookup delays. It is not unusual to have to try the same url in a
browser two or three times before it loads. If I configure a
workstation to use the name servers from the forwarding list, instead
of the internal name server, the problem disappears.

This is a problem that we have not always had. I think it may have
started when we upgraded from NW6 to NW6.5. On the off chance that
this is a configuration issue, here are some environmental details:

Server name and ipa of the box that named.nlm runs on: CIN ,
10.10.10.20

There is a single internal domain setup in DNS, (reliablecastings.com)

Not sure if this is OK, but there are two A records set up that both
point to 10.10.10.20. One is for "cin", and the other one is for
"internal", which is associated with the NDS DNS object.

"www" is setup with an A record pointing to our isp hosted website.


NSLOOKUP(s) FROM THE DNS SERVER CONSOLE

] server 10.10.10.20
Default DNS server: CIN
Address: 10.10.10.20

] nslookup cin.reliablecastings.com
cin.reliablecastings.com QUERY FAILED
*** Can't find address for server cin.reliablecastings.com: Timed Out
Server: CIN
Address: 10.10.10.20
nslookup QUERY FAILED
*** CIN can't find nslookup: Non-existant domain

] server 216.68.4.10
Default DNS server: ns1.zoomtown.com
Address: 216.68.4.10

] nslookup www.hartford.com
www.hartford.com QUERY FAILED
*** Can't find address for server www.hartford.com: Timed Out
Server: ns1.zoomtown.com
Address: 216.68.4.10
nslookup QUERY FAILED
*** ns1.zoomtown.com can't find nslookup: Non-existant domain


NSLOOKUP(s) FROM A WORKSTATION

] server 10.10.10.20
Default server: internal.reliablecastings.com
Address: 10.10.10.20

] nslookup cin.reliablecastings.com
Server: cin.reliablecastings.com
Address: 10.10.10.20
*** cin.reliablecastings.com can't find nslookup: Non-existant domain

] server 216.68.4.10
Default server: ns1.zoomtown.com
Address: 216.68.4.10

] nslookup www.hartford.com
Server: www.hartford.com
Address: 69.94.104.92

DNS request timed out
timeout was 2 seconds
*** Request to www.hartford.com timed-out

COMMENTS:
Name resolution works from inside of a browser at the workstation. If
I type in "cin" in the address bar, I am immediately taken to the
server's administration page.

What's up with the NSLOOKUP for "hartford.com" at the workstation? It
comes back with the numerical ipa, but then says that the request
timed out!

resolve.cfg has exactly two lines in it:
domain reliablecastings.com
nameserver 10.10.10.20

STUFF FROM NAMED.RUN - NSLOOKUP, FROM WORKSTATION, ON "HARTFORD.COM"
(Unfortunately, the details of my request were interspersed with other
requests. I did my best to include just my request here, but I'm not
sure if I left something out or not. Look at the second line, were it
says 'www.hartford.com.reliablecastings.com/IN'- can that be right, or
is that simply the first try to match to an internal address, in other
words, before it is forwarded?


May 22 14:13:54.000 security: query: debug 3: client 10.10.10.30#1902:
query 'www.hartford.com.reliablecastings.com/IN' approved
May 22 14:13:54.000 client: client: debug 3: client 10.10.10.30#1902:
send
May 22 14:13:54.000 client: client: debug 3: client 10.10.10.30#1902:
sendto
May 22 14:13:54.000 client: client: debug 3: client 10.10.10.30#1902:
senddone
May 22 14:13:54.000 client: client: debug 3: client 10.10.10.30#1902:
next
May 22 14:13:54.000 client: client: debug 10: client 10.10.10.30#1902:
ns_client_detach: ref = 0
May 22 14:13:54.000 client: client: debug 3: client 10.10.10.30#1902:
endrequest
May 22 14:13:54.000 client: client: debug 3: client @54905000: udprecv
May 22 14:13:54.000 client: client: debug 3: client 10.10.10.30#1903:
UDP request
May 22 14:13:54.000 client: client: debug 5: client 10.10.10.30#1903:
using view '_default'
May 22 14:13:54.000 security: client: debug 3: client
10.10.10.30#1903: request is not signed
May 22 14:13:54.000 security: client: debug 3: client
10.10.10.30#1903: recursion available: approved
May 22 14:13:54.000 client: client: debug 3: client 10.10.10.30#1903:
query
May 22 14:13:54.000 client: client: debug 10: client 10.10.10.30#1903:
ns_client_attach: ref = 1
May 22 14:13:54.000 security: client: debug 3: client
10.10.10.30#1903: query (cache) approved
May 22 14:13:54.000 client: client: debug 3: client 10.10.10.30#1903:
replace
May 22 14:13:54.000 general: client: debug 3: clientmgr @46f4fd40:
createclients
May 22 14:13:54.000 general: client: debug 3: clientmgr @46f4fd40:
recycle
May 22 14:13:54.000 resolver: dns/resolver: debug 1: createfetch:
www.hartford.com A
May 22 14:13:54.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
create
May 22 14:13:54.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
join
May 22 14:13:54.000 resolver: dns/resolver: debug 3: fetch 584861e0
(fctx 5985ac60): created
May 22 14:13:54.000 client: client: debug 3: client @4dc0f280: udprecv
May 22 14:13:54.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
start
May 22 14:13:54.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
try
May 22 14:13:54.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
cancelqueries
May 22 14:13:54.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
getaddresses
May 22 14:13:54.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
query
May 22 14:13:54.000 resolver: dns/resolver: debug 3: resquery 4512d500
(fctx 5985ac60): send
May 22 14:13:54.000 resolver: dns/resolver: debug 3: resquery 4512d500
(fctx 5985ac60): sent
May 22 14:13:54.000 resolver: dns/resolver: debug 3: resquery 4512d500
(fctx 5985ac60): senddone
May 22 14:13:56.000 resolver: dns/resolver: debug 3: resquery 4512d500
(fctx 5985ac60): response
May 22 14:13:56.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
answer_response
May 22 14:13:56.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
cache_message
May 22 14:13:56.000 database: dns/cache: debug 1: no_references:
delete from rbt: 41d33140 ns.serverhost.NET
May 22 14:13:56.000 database: dns/cache: debug 1: no_references:
delete from rbt: 41d33140 ns2.serverhost.NET
May 22 14:13:56.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
cancelquery
May 22 14:13:56.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
done
May 22 14:13:56.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
stopeverything
May 22 14:13:56.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
cancelqueries
May 22 14:13:56.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
sendevents
May 22 14:13:56.000 resolver: dns/resolver: debug 3: fetch 584861e0
(fctx 5985ac60): destroyfetch
May 22 14:13:56.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
shutdown
May 22 14:13:56.000 client: client: debug 3: client 10.10.10.30#1903:
send
May 22 14:13:56.000 client: client: debug 3: client 10.10.10.30#1903:
sendto
May 22 14:13:56.000 client: client: debug 3: client 10.10.10.30#1903:
senddone
May 22 14:13:56.000 client: client: debug 3: client 10.10.10.30#1903:
next
May 22 14:13:56.000 client: client: debug 10: client 10.10.10.30#1903:
ns_client_detach: ref = 0
May 22 14:13:56.000 client: client: debug 3: client 10.10.10.30#1903:
endrequest
May 22 14:13:56.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
doshutdown
May 22 14:13:56.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
stopeverything
May 22 14:13:56.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
cancelqueries
May 22 14:13:56.000 resolver: dns/resolver: debug 3: fctx 5985ac60:
destroy

All help is greatly appreciated!

Jeff Palmer