Anonymous_User Absent Member.
Absent Member.
4980 views

OES DNS server can't resolve itself

Hi folks,

OES NW sp1. Server is master and authoritive for the domain. Both A
and NS records in place.

Server resolves anything except itself. First time I've seen this
though I've been using NW's DNS for quite a while.


nslookup results:

C:\>nslookup job.juth.org
Server: job.juth.org
Address: 192.168.0.207

*** job.juth.org can't find job.juth.org: Non-existent domain

Any other host is fine:

C:\>nslookup eve.juth.org
Server: job.juth.org
Address: 192.168.0.207

Name: eve.juth.org
Address: 192.168.0.202

C:\>nslookup google.com
Server: job.juth.org
Address: 192.168.0.207

Non-authoritative answer:
Name: google.com
Addresses: 72.14.207.99, 64.233.167.99, 64.233.187.99

Have tried removing and readding the server's records and deleting the
domain's .db file.

Thanks.

Jim
Labels (1)
0 Likes
21 Replies
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

Make sure the server's first entry in RESOLV.CFG is itself. After
changing the file, type WS2_32 RELOAD RESOLVE at the server console to
reload the file, then test again with NSLOOKUP. Also, what happens if
you run NSLOOKUP on the server itslef?

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

On Mon, 06 Feb 2006 16:25:57 GMT, Brad Doster <bd@NSCSysOps.net>
wrote:

>Make sure the server's first entry in RESOLV.CFG is itself. After
>changing the file, type WS2_32 RELOAD RESOLVE at the server console to
>reload the file, then test again with NSLOOKUP. Also, what happens if
>you run NSLOOKUP on the server itslef?
>
>bd
>NSC Volunteer SysOp
>


First entry is the server.

The server can resolve itself OK, it just doesn't seem to be able to
pass that along to other host's requests. NSlookup on the server
resolves. If it was just one box it would be one thing, but it gives
the same answer to all hosts, win, linux and even other OES servers.

Jim
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

Hmmmm... instead of this...

C:\>nslookup job.juth.org

...try this...

C:\>nslookup job.juth.org.

The difference is simply a trailing dot after the fqdn.

Also, on a Windows machine where this is not working, please post the
output from IPCONFIG /ALL, and the machine's HOSTS file.

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

On Tue, 07 Feb 2006 15:50:43 GMT, Brad Doster <bd@NSCSysOps.net>
wrote:

>Hmmmm... instead of this...
>
>C:\>nslookup job.juth.org
>
>..try this...
>
>C:\>nslookup job.juth.org.
>
>The difference is simply a trailing dot after the fqdn.
>
>Also, on a Windows machine where this is not working, please post the
>output from IPCONFIG /ALL, and the machine's HOSTS file.
>
>bd
>NSC Volunteer SysOp
>


Same result with trailing dot.

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : juth.org
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx
Gigabit Cont
roller
Physical Address. . . . . . . . . : 00-11-11-A3-6E-E4
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.60
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.200
DNS Servers . . . . . . . . . . . : 192.168.0.207


Hosts:

# Copyright (c) 1993-1999 Microsoft Corp.
# <deleted commentts>
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost
192.168.0.60 jim01

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

Thanks for the info, but you left out the stuff above "Ethernet adapter
Local Area Connection:", i.e:

Host Name . . . . . . . . . . . . :
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . :
IP Routing Enabled. . . . . . . . :
WINS Proxy Enabled. . . . . . . . :
DNS Suffix Search List. . . . . . :

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

On Wed, 08 Feb 2006 18:41:59 GMT, Brad Doster <bd@NSCSysOps.net>
wrote:

>Thanks for the info, but you left out the stuff above "Ethernet adapter
>Local Area Connection:", i.e:
>
>Host Name . . . . . . . . . . . . :
>Primary Dns Suffix . . . . . . . :
>Node Type . . . . . . . . . . . . :
>IP Routing Enabled. . . . . . . . :
>WINS Proxy Enabled. . . . . . . . :
>DNS Suffix Search List. . . . . . :
>
>bd
>NSC Volunteer SysOp
>


Sorry, here is the unabridged version.

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : jim01
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : juth.org

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet
Adapter for
VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet
Adapter for
VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.159.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : juth.org
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx
Gigabit Cont
roller
Physical Address. . . . . . . . . : 00-11-11-A3-6E-E4
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.60
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.200
DNS Servers . . . . . . . . . . . : 192.168.0.207
24.95.227.34

Ethernet adapter {EDDE2F90-0400-4C32-AFB2-DD09B356D8F1}:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Check Point Virtual
Network Adapter
For SSL Network Extender - Packet Scheduler Miniport
Physical Address. . . . . . . . . : 54-55-43-44-52-0B

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

Thanks, Jim. I don't see any glaring red flags there, but I do find it
curious that your workstation has no primary DNS suffix. It shouldn't
matter for what we're looking at, it's just a curiousity...

Silly question... you do have an A record for the DNS server in your
DNS config, right? Once the NS record is there, it's sometimes easy to
forget to create the A record.

If the A record is already there, we need to start looking at logs...
LOAD NAMED -DL 3 -S, duplicate the problem, unload and reload NAMED
normally, then post the contents of sys:named.run in a reply here.

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

On Thu, 09 Feb 2006 16:09:39 GMT, Brad Doster <bd@NSCSysOps.net>
wrote:

>Thanks, Jim. I don't see any glaring red flags there, but I do find it
>curious that your workstation has no primary DNS suffix. It shouldn't
>matter for what we're looking at, it's just a curiousity...


Never bothered with it. BTW, I get the same results from a SUSE 10
box on an nslookup.

>Silly question... you do have an A record for the DNS server in your
>DNS config, right? Once the NS record is there, it's sometimes easy to
>forget to create the A record.


Yeah, both A and NS records.

>If the A record is already there, we need to start looking at logs...
>LOAD NAMED -DL 3 -S, duplicate the problem, unload and reload NAMED
>normally, then post the contents of sys:named.run in a reply here.
>
>bd
>NSC Volunteer SysOp


Here's the contents:

Feb 09 20:57:36.000 general: main: notice: starting BIND 9.2.0
Feb 09 20:55:10.000 general: main: info: Checking the path
sys:\etc\dns. Dir sys:\etc exists.
Feb 09 20:55:10.000 general: main: info: Checking the path
sys:\etc\dns. Dir sys:\etc\dns exists.
Feb 09 20:55:10.000 general: main: info: Changing directory to
sys:\etc\dns succeeded.
Feb 09 20:55:10.000 general: server: info: using 1 CPU
Feb 09 20:55:10.000 general: dns/db: info: Log-in to eDirectory
Feb 09 20:55:10.000 general: dns/db: debug 1: Volume is not a cluster
resource
Feb 09 20:55:10.000 network: interfacemgr: info: listening on IPv4
interface Loopback Interface 1, 192.168.0.207#53
Feb 09 20:55:10.000 general: client: debug 3: clientmgr @89e68d00:
create
Feb 09 20:55:10.000 general: client: debug 3: clientmgr @89e68d00:
createclients
Feb 09 20:55:10.000 general: client: debug 3: clientmgr @89e68d00:
create new
Feb 09 20:55:10.000 client: client: debug 3: client @87b95000: create
Feb 09 20:55:10.000 general: client: debug 3: clientmgr @89e68d00:
createclients
Feb 09 20:55:10.000 general: client: debug 3: clientmgr @89e68d00:
create new
Feb 09 20:55:10.000 client: client: debug 3: client @87b952a0: create
Feb 09 20:55:10.000 network: interfacemgr: info: DNS Server will
register with IP Address Management framework for the address:
192.168.0.207
Feb 09 20:55:10.000 general: server: debug 1: Mounting the juth.org.
zone
Feb 09 20:55:10.000 general: server: debug 1: Mounting the
168.192.IN-ADDR.ARPA. zone
Feb 09 20:55:10.000 resolver: dns/resolver: debug 3: res 8714e7e0:
create
Feb 09 20:55:10.000 general: dns/request: debug 3:
dns_requestmgr_create
Feb 09 20:55:10.000 general: dns/request: debug 3:
dns_requestmgr_create: 89e65c80
Feb 09 20:55:10.000 general: dns/request: debug 3:
dns_requestmgr_whenshutdown
Feb 09 20:55:10.000 general: server: info: no source of entropy found
Feb 09 20:55:10.000 general: server: info: ignoring config file
logging statement due to -g option
Feb 09 20:55:10.000 general: snmp: info: NCP server name is JOB
Feb 09 20:55:10.000 general: server: debug 1: load_configuration:
success
Feb 09 20:55:10.000 client: client: debug 3: client @87b95000: udprecv
Feb 09 20:55:10.000 general: dns/zone: debug 1: zone
168.192.IN-ADDR.ARPA/IN: starting load
Feb 09 20:55:10.000 general: dns/zone: debug 1: zone
168.192.IN-ADDR.ARPA/IN: Loading from File
Feb 09 20:55:10.000 general: dns/zone: debug 2: zone
168.192.IN-ADDR.ARPA/IN: number of nodes in database: 10
Feb 09 20:55:10.000 general: dns/zone: debug 1: zone
168.192.IN-ADDR.ARPA/IN: loaded
Feb 09 20:55:10.000 general: dns/zone: debug 1: zone
168.192.IN-ADDR.ARPA/IN: journal rollforward completed successfully:
up to date
Feb 09 20:55:10.000 general: dns/zone: info: zone
168.192.IN-ADDR.ARPA/IN: loaded serial 2004041826
Feb 09 20:55:10.000 general: dns/zone: debug 1: zone juth.org/IN:
starting load
Feb 09 20:55:10.000 general: dns/zone: debug 1: zone juth.org/IN:
Loading from File
Feb 09 20:55:10.000 general: dns/zone: debug 2: zone juth.org/IN:
number of nodes in database: 10
Feb 09 20:55:10.000 general: dns/zone: debug 1: zone juth.org/IN:
loaded
Feb 09 20:55:10.000 general: dns/zone: debug 1: zone juth.org/IN:
journal rollforward completed successfully: up to date
Feb 09 20:55:10.000 general: dns/zone: info: zone juth.org/IN: loaded
serial 2001122117
Feb 09 20:55:10.000 general: dns/zone: debug 1: dns_zone_maintenance:
zone juth.org/IN: enter
Feb 09 20:55:10.000 general: dns/zone: debug 1: dns_zone_maintenance:
zone 168.192.IN-ADDR.ARPA/IN: enter
Feb 09 20:55:10.000 client: client: debug 3: client @87b952a0: accept
Feb 09 20:55:10.000 general: dns/zone: debug 1: zone_timer: zone
168.192.IN-ADDR.ARPA/IN: enter
Feb 09 20:55:10.000 general: dns/zone: debug 1: zone_maintenance: zone
168.192.IN-ADDR.ARPA/IN: enter
Feb 09 20:55:10.000 notify: dns/zone: info: zone
168.192.IN-ADDR.ARPA/IN: sending notifies (serial 2004041826)
Feb 09 20:55:10.000 notify: dns/zone: debug 3: zone
168.192.IN-ADDR.ARPA/IN: sending notify to 192.168.0.202#53
Feb 09 20:55:10.000 general: dns/request: debug 3:
dns_request_createvia
Feb 09 20:55:10.000 general: dns/request: debug 3: request_render
Feb 09 20:55:10.000 general: dns/request: debug 3: requestmgr_attach:
89e65c80: eref 1 iref 1
Feb 09 20:55:10.000 general: dns/request: debug 3: mgr_gethash
Feb 09 20:55:10.000 general: dns/request: debug 3: req_send: request
89e65b80
Feb 09 20:55:10.000 general: dns/request: debug 3:
dns_request_createvia: request 89e65b80
Feb 09 20:55:10.000 general: dns/request: debug 3: req_senddone:
request 89e65b80
Feb 09 20:55:10.000 general: dns/zone: debug 1: zone_timer: zone
juth.org/IN: enter
Feb 09 20:55:10.000 general: dns/zone: debug 1: zone_maintenance: zone
juth.org/IN: enter
Feb 09 20:55:10.000 general: server: info: running
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4481:
UDP request
Feb 09 20:55:13.000 security: client: debug 3: client
192.168.0.61#4481: request is not signed
Feb 09 20:55:13.000 security: client: debug 3: client
192.168.0.61#4481: recursion available: approved
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4481:
query
Feb 09 20:55:13.000 security: client: debug 3: client
192.168.0.61#4481: query (cache) approved
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4481:
replace
Feb 09 20:55:13.000 general: client: debug 3: clientmgr @89e68d00:
createclients
Feb 09 20:55:13.000 general: client: debug 3: clientmgr @89e68d00:
create new
Feb 09 20:55:13.000 client: client: debug 3: client @87b95a80: create
Feb 09 20:55:13.000 resolver: dns/resolver: debug 1: createfetch: EV A
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
create
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
join
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fetch 87b98be0
(fctx 89ece000): created
Feb 09 20:55:13.000 client: client: debug 3: client @87b95a80: udprecv
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
start
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
try
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
cancelqueries
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
getaddresses
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
dns_resolver_prime
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
priming
Feb 09 20:55:13.000 resolver: dns/resolver: debug 1: createfetch: . NS
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
create
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
join
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fetch 87b98ae0
(fctx 89ece160): created
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
dns_resolver_prime
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
dns_resolver_prime
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
dns_resolver_prime
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
dns_resolver_prime
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
dns_resolver_prime
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
dns_resolver_prime
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
dns_resolver_prime
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
dns_resolver_prime
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
dns_resolver_prime
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
dns_resolver_prime
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
dns_resolver_prime
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: res 8714e7e0:
dns_resolver_prime
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
query
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: resquery 87b95d20
(fctx 89ece000): send
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: resquery 87b95d20
(fctx 89ece000): sent
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
start
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
try
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
cancelqueries
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
getaddresses
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
query
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: resquery 87bc8020
(fctx 89ece160): send
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: resquery 87bc8020
(fctx 89ece160): sent
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: resquery 87b95d20
(fctx 89ece000): senddone
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: resquery 87bc8020
(fctx 89ece160): senddone
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: resquery 87bc8020
(fctx 89ece160): response
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
answer_response
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
cache_message
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
cancelquery
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
done
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
stopeverything
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
cancelqueries
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
sendevents
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fetch 87b98ae0
(fctx 89ece160): destroyfetch
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
shutdown
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
doshutdown
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
stopeverything
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
cancelqueries
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece160:
destroy
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: resquery 87b95d20
(fctx 89ece000): response
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
noanswer_response
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
ncache_message
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
cancelquery
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
done
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
stopeverything
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
cancelqueries
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
sendevents
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fetch 87b98be0
(fctx 89ece000): destroyfetch
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
shutdown
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4481:
send
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4481:
sendto
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4481:
senddone
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4481:
next
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4481:
endrequest
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
doshutdown
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
stopeverything
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
cancelqueries
Feb 09 20:55:13.000 resolver: dns/resolver: debug 3: fctx 89ece000:
destroy
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4482:
UDP request
Feb 09 20:55:13.000 security: client: debug 3: client
192.168.0.61#4482: request is not signed
Feb 09 20:55:13.000 security: client: debug 3: client
192.168.0.61#4482: recursion available: approved
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4482:
query
Feb 09 20:55:13.000 security: client: debug 3: client
192.168.0.61#4482: query (cache) approved
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4482:
send
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4482:
sendto
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4482:
senddone
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4482:
next
Feb 09 20:55:13.000 client: client: debug 3: client 192.168.0.61#4482:
endrequest
Feb 09 20:55:13.000 client: client: debug 3: client @87b95a80: udprecv
Feb 09 20:55:25.000 general: dns/request: debug 3: req_timeout:
request 89e65b80
Feb 09 20:55:25.000 general: dns/request: debug 3: req_cancel: request
89e65b80
Feb 09 20:55:25.000 general: dns/request: debug 3: req_sendevent:
request 89e65b80
Feb 09 20:55:25.000 notify: dns/zone: debug 1: zone
168.192.IN-ADDR.ARPA/IN: notify to 192.168.0.202#53 failed: timed out
Feb 09 20:55:25.000 general: dns/request: debug 3:
dns_request_destroy: request 89e65b80
Feb 09 20:55:25.000 general: dns/request: debug 3: req_destroy:
request 89e65b80
Feb 09 20:55:25.000 general: dns/request: debug 3: requestmgr_detach:
89e65c80: eref 1 iref 0
Feb 09 20:55:25.000 notify: dns/zone: debug 3: zone
168.192.IN-ADDR.ARPA/IN: sending notify to 192.168.0.202#53
Feb 09 20:55:25.000 general: dns/request: debug 3:
dns_request_createvia
Feb 09 20:55:25.000 general: dns/request: debug 3: request_render
Feb 09 20:55:25.000 general: dns/request: debug 3: requestmgr_attach:
89e65c80: eref 1 iref 1
Feb 09 20:55:25.000 general: dns/request: debug 3: mgr_gethash
Feb 09 20:55:25.000 general: dns/request: debug 3: req_send: request
89e65b80
Feb 09 20:55:25.000 general: dns/request: debug 3:
dns_request_createvia: request 89e65b80
Feb 09 20:55:25.000 general: dns/request: debug 3: req_senddone:
request 89e65b80
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4471:
UDP request
Feb 09 20:55:37.000 security: client: debug 3: client
192.168.0.60#4471: request is not signed
Feb 09 20:55:37.000 security: client: debug 3: client
192.168.0.60#4471: recursion available: approved
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4471:
query
Feb 09 20:55:37.000 security: query: debug 3: client
192.168.0.60#4471: query '207.0.168.192.in-addr.arpa/IN' approved
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4471:
send
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4471:
sendto
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4471:
senddone
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4471:
next
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4471:
endrequest
Feb 09 20:55:37.000 client: client: debug 3: client @87b95a80: udprecv
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4472:
UDP request
Feb 09 20:55:37.000 security: client: debug 3: client
192.168.0.60#4472: request is not signed
Feb 09 20:55:37.000 security: client: debug 3: client
192.168.0.60#4472: recursion available: approved
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4472:
query
Feb 09 20:55:37.000 security: query: debug 3: client
192.168.0.60#4472: query 'jog.juth.org/IN' approved
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4472:
send
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4472:
sendto
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4472:
senddone
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4472:
next
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4472:
endrequest
Feb 09 20:55:37.000 client: client: debug 3: client @87b95a80: udprecv
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4473:
UDP request
Feb 09 20:55:37.000 security: client: debug 3: client
192.168.0.60#4473: request is not signed
Feb 09 20:55:37.000 security: client: debug 3: client
192.168.0.60#4473: recursion available: approved
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4473:
query
Feb 09 20:55:37.000 security: query: debug 3: client
192.168.0.60#4473: query 'jog.juth.org/IN' approved
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4473:
send
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4473:
sendto
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4473:
senddone
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4473:
next
Feb 09 20:55:37.000 client: client: debug 3: client 192.168.0.60#4473:
endrequest
Feb 09 20:55:37.000 client: client: debug 3: client @87b95a80: udprecv
Feb 09 20:55:40.000 general: dns/request: debug 3: req_timeout:
request 89e65b80
Feb 09 20:55:40.000 general: dns/request: debug 3: req_cancel: request
89e65b80
Feb 09 20:55:40.000 general: dns/request: debug 3: req_sendevent:
request 89e65b80
Feb 09 20:55:40.000 notify: dns/zone: debug 1: zone
168.192.IN-ADDR.ARPA/IN: notify to 192.168.0.202#53 failed: timed out
Feb 09 20:55:40.000 general: dns/request: debug 3:
dns_request_destroy: request 89e65b80
Feb 09 20:55:40.000 general: dns/request: debug 3: req_destroy:
request 89e65b80
Feb 09 20:55:40.000 general: dns/request: debug 3: requestmgr_detach:
89e65c80: eref 1 iref 0
Feb 09 20:55:40.000 notify: dns/zone: debug 3: zone
168.192.IN-ADDR.ARPA/IN: sending notify to 192.168.0.202#53
Feb 09 20:55:40.000 general: dns/request: debug 3:
dns_request_createvia
Feb 09 20:55:40.000 general: dns/request: debug 3: request_render
Feb 09 20:55:40.000 general: dns/request: debug 3: requestmgr_attach:
89e65c80: eref 1 iref 1
Feb 09 20:55:40.000 general: dns/request: debug 3: mgr_gethash
Feb 09 20:55:40.000 general: dns/request: debug 3: req_send: request
89e65b80
Feb 09 20:55:40.000 general: dns/request: debug 3:
dns_request_createvia: request 89e65b80
Feb 09 20:55:40.000 general: dns/request: debug 3: req_senddone:
request 89e65b80
Feb 09 20:55:55.000 general: dns/request: debug 3: req_timeout:
request 89e65b80
Feb 09 20:55:55.000 general: dns/request: debug 3: req_cancel: request
89e65b80
Feb 09 20:55:55.000 general: dns/request: debug 3: req_sendevent:
request 89e65b80
Feb 09 20:55:55.000 notify: dns/zone: debug 1: zone
168.192.IN-ADDR.ARPA/IN: notify to 192.168.0.202#53 failed: timed out
Feb 09 20:55:55.000 general: dns/request: debug 3:
dns_request_destroy: request 89e65b80
Feb 09 20:55:55.000 general: dns/request: debug 3: req_destroy:
request 89e65b80
Feb 09 20:55:55.000 general: dns/request: debug 3: requestmgr_detach:
89e65c80: eref 1 iref 0
Feb 09 20:55:55.000 notify: dns/zone: debug 3: zone
168.192.IN-ADDR.ARPA/IN: sending notify to 192.168.0.202#53
Feb 09 20:55:55.000 general: dns/request: debug 3:
dns_request_createvia
Feb 09 20:55:55.000 general: dns/request: debug 3: request_render
Feb 09 20:55:55.000 general: dns/request: debug 3: requestmgr_attach:
89e65c80: eref 1 iref 1
Feb 09 20:55:55.000 general: dns/request: debug 3: mgr_gethash
Feb 09 20:55:55.000 general: dns/request: debug 3: req_send: request
89e65b80
Feb 09 20:55:55.000 general: dns/request: debug 3:
dns_request_createvia: request 89e65b80
Feb 09 20:55:55.000 general: dns/request: debug 3: req_senddone:
request 89e65b80
Feb 09 20:56:05.000 client: client: debug 3: client
192.168.0.207#15594: new TCP connection
Feb 09 20:56:05.000 client: client: debug 3: client
192.168.0.207#15594: replace
Feb 09 20:56:05.000 general: client: debug 3: clientmgr @89e68d00:
createclients
Feb 09 20:56:05.000 general: client: debug 3: clientmgr @89e68d00:
recycle
Feb 09 20:56:05.000 client: client: debug 3: client
192.168.0.207#15594: read
Feb 09 20:56:05.000 client: client: debug 3: client @87b95000: accept
Feb 09 20:56:05.000 client: client: debug 3: client
192.168.0.207#15594: TCP request
Feb 09 20:56:05.000 security: client: debug 3: client
192.168.0.207#15594: request is not signed
Feb 09 20:56:05.000 security: client: debug 3: client
192.168.0.207#15594: recursion available: approved
Feb 09 20:56:05.000 client: client: debug 3: client
192.168.0.207#15594: query
Feb 09 20:56:05.000 general: server: info: Failed in getting question
name : Checking for StartStop / Dynamic update query
Feb 09 20:56:05.000 general: server: info: Found correct number of
counts in header
Feb 09 20:56:05.000 update: update: info: client 192.168.0.207#15594:
Novell Dynamic Update : Query received
Feb 09 20:56:05.000 client: client: debug 3: client
192.168.0.207#15594: sendto
Feb 09 20:56:05.000 client: client: debug 3: client
192.168.0.207#15594: senddone
Feb 09 20:56:05.000 client: client: debug 3: client
192.168.0.207#15594: next
Feb 09 20:56:05.000 client: client: debug 3: client
192.168.0.207#15594: endrequest
Feb 09 20:56:05.000 client: client: debug 3: client
192.168.0.207#15594: read
Feb 09 20:56:10.000 general: dns/request: debug 3: req_timeout:
request 89e65b80
Feb 09 20:56:10.000 general: dns/request: debug 3: req_cancel: request
89e65b80
Feb 09 20:56:10.000 general: dns/request: debug 3: req_sendevent:
request 89e65b80
Feb 09 20:56:10.000 notify: dns/zone: debug 1: zone
168.192.IN-ADDR.ARPA/IN: notify to 192.168.0.202#53 failed: timed out
Feb 09 20:56:10.000 notify: dns/zone: debug 1: zone
168.192.IN-ADDR.ARPA/IN: notify to 192.168.0.202#53: retries exceeded
Feb 09 20:56:10.000 general: dns/request: debug 3:
dns_request_destroy: request 89e65b80
Feb 09 20:56:10.000 general: dns/request: debug 3: req_destroy:
request 89e65b80
Feb 09 20:56:10.000 general: dns/request: debug 3: requestmgr_detach:
89e65c80: eref 1 iref 0
Feb 09 20:56:35.000 client: client: debug 3: client
192.168.0.207#15594: timeout
Feb 09 20:56:35.000 client: client: debug 3: client
192.168.0.207#15594: closetcp
Feb 09 20:56:45.000 client: client: debug 3: client 192.168.0.51#1834:
UDP request
Feb 09 20:56:45.000 security: client: debug 3: client
192.168.0.51#1834: request is not signed
Feb 09 20:56:45.000 security: client: debug 3: client
192.168.0.51#1834: recursion available: approved
Feb 09 20:56:45.000 client: client: debug 3: client 192.168.0.51#1834:
query
Feb 09 20:56:45.000 security: query: debug 3: client
192.168.0.51#1834: query 'job.juth.org/IN' approved
Feb 09 20:56:45.000 client: client: debug 3: client 192.168.0.51#1834:
replace
Feb 09 20:56:45.000 general: client: debug 3: clientmgr @89e68d00:
createclients
Feb 09 20:56:45.000 general: client: debug 3: clientmgr @89e68d00:
recycle
Feb 09 20:56:45.000 resolver: dns/resolver: debug 1: createfetch:
job.juth.org A
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
create
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
join
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fetch 87b98bc0
(fctx 8aef7020): created
Feb 09 20:56:45.000 client: client: debug 3: client @87b952a0: udprecv
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
start
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
try
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
cancelqueries
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
getaddresses
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
query
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: resquery 87b95d20
(fctx 8aef7020): send
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: resquery 87b95d20
(fctx 8aef7020): sent
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: resquery 87b95d20
(fctx 8aef7020): senddone
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: resquery 87b95d20
(fctx 8aef7020): response
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
noanswer_response
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
ncache_message
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
cancelquery
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
done
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
stopeverything
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
cancelqueries
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
sendevents
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fetch 87b98bc0
(fctx 8aef7020): destroyfetch
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
shutdown
Feb 09 20:56:45.000 client: client: debug 3: client 192.168.0.51#1834:
send
Feb 09 20:56:45.000 client: client: debug 3: client 192.168.0.51#1834:
sendto
Feb 09 20:56:45.000 client: client: debug 3: client 192.168.0.51#1834:
senddone
Feb 09 20:56:45.000 client: client: debug 3: client 192.168.0.51#1834:
next
Feb 09 20:56:45.000 client: client: debug 3: client 192.168.0.51#1834:
endrequest
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
doshutdown
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
stopeverything
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
cancelqueries
Feb 09 20:56:45.000 resolver: dns/resolver: debug 3: fctx 8aef7020:
destroy
Feb 09 20:57:34.000 general: server: info: shutting down
Feb 09 20:57:34.000 resolver: dns/resolver: debug 3: res 8714e7e0:
shutdown
Feb 09 20:57:34.000 resolver: dns/resolver: debug 3: res 8714e7e0:
exiting
Feb 09 20:57:34.000 general: dns/request: debug 3:
dns_requestmgr_shutdown: 89e65c80
Feb 09 20:57:34.000 general: dns/request: debug 3:
send_shutdown_events: 89e65c80
Feb 09 20:57:34.000 network: interfacemgr: info: no longer listening
on 192.168.0.207#53
Feb 09 20:57:34.000 general: client: debug 3: clientmgr @89e68d00:
destroy
Feb 09 20:57:34.000 general: dns/zone: debug 3: zone_shutdown: zone
juth.org/IN: shutting down
Feb 09 20:57:34.000 general: dns/zone: debug 3: zone_shutdown: zone
168.192.IN-ADDR.ARPA/IN: shutting down
Feb 09 20:57:34.000 client: client: debug 3: client @87b95000:
shutdown
Feb 09 20:57:34.000 client: client: debug 3: client @87b952a0:
shutdown
Feb 09 20:57:34.000 client: client: debug 3: client @87b95000: accept
failed: operation canceled
Feb 09 20:57:34.000 client: client: debug 3: client @87b952a0: free
Feb 09 20:57:34.000 client: client: debug 3: client @87b95000: free
Feb 09 20:57:34.000 client: client: debug 3: client @87b95a80:
shutdown
Feb 09 20:57:34.000 client: client: debug 3: client @87b95a80: free
Feb 09 20:57:34.000 general: client: debug 3: clientmgr @89e68d00:
clientmgr_destroy
Feb 09 20:57:34.000 resolver: dns/resolver: debug 3: res 8714e7e0:
detach
Feb 09 20:57:34.000 resolver: dns/resolver: debug 3: res 8714e7e0:
destroy
Feb 09 20:57:34.000 general: dns/request: debug 3:
dns_requestmgr_detach: 89e65c80: eref 0 iref 0
Feb 09 20:57:34.000 general: dns/request: debug 3: mgr_destroy
Feb 09 20:57:34.000 general: main: notice: exiting


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

Having looked at your log and compared it to one that I have with a
successful result, it looks almost identical. The only difference I
see in the request processing portion is...

From your log:
security: query: debug 3: client 192.168.0.51#1834: query
'job.juth.org/IN' approved

From mine:
security: client: debug 3: client 192.168.0.51#1298: query (cache)
approved

I don't know what causes the difference -- maybe you've adjusted some
settings for caching on your server? But I don't think above would
cause nothing to be sent back. In fact, it appears that your server is
resolving and responding to the client, but we don't know where the
response is going. So the next thing is to look at packet traces,
which you can do from your server and/or the workstation. In fact you
may need to do both... if the server is indeed sending replies back to
the correct address, why are they not being received at the
workstation?

You can download pktscan.nlm for your Novell server, and use Ethereal
or Packetyzer on the workstation, if you don't have something in place
already.

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

Hi Brad,

Finally had a moment to run ethereal. I did it from a suse 10 laptop.

The server is replying, just saying there's no such name.

No. Time Source Destination Protocol
Info
1 0.000000 192.168.0.51 192.168.0.202 NTP NTP

Frame 1 (90 bytes on wire, 90 bytes captured)
Ethernet II, Src: 192.168.0.51 (00:20:e0:96:0b:e9), Dst: 192.168.0.202
(00:01:03:2c:5d:53)
Internet Protocol, Src: 192.168.0.51 (192.168.0.51), Dst: 192.168.0.202
(192.168.0.202)
User Datagram Protocol, Src Port: ntp (123), Dst Port: ntp (123)
Network Time Protocol

No. Time Source Destination Protocol
Info
2 0.000095 192.168.0.202 192.168.0.51 NTP NTP

Frame 2 (90 bytes on wire, 90 bytes captured)
Ethernet II, Src: 192.168.0.202 (00:01:03:2c:5d:53), Dst: 192.168.0.51
(00:20:e0:96:0b:e9)
Internet Protocol, Src: 192.168.0.202 (192.168.0.202), Dst: 192.168.0.51
(192.168.0.51)
User Datagram Protocol, Src Port: ntp (123), Dst Port: ntp (123)
Network Time Protocol

No. Time Source Destination Protocol
Info
3 4.803496 192.168.0.51 192.168.0.202 ARP Who
has 192.168.0.202? Tell 192.168.0.51

Frame 3 (42 bytes on wire, 42 bytes captured)
Ethernet II, Src: 192.168.0.51 (00:20:e0:96:0b:e9), Dst: 192.168.0.202
(00:01:03:2c:5d:53)
Address Resolution Protocol (request)

No. Time Source Destination Protocol
Info
4 4.804839 192.168.0.202 192.168.0.51 ARP
192.168.0.202 is at 00:01:03:2c:5d:53

Frame 4 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 192.168.0.202 (00:01:03:2c:5d:53), Dst: 192.168.0.51
(00:20:e0:96:0b:e9)
Address Resolution Protocol (reply)

No. Time Source Destination Protocol
Info
5 8.003859 192.168.0.51 Broadcast ARP Who
has 192.168.0.207? Tell 192.168.0.51

Frame 5 (42 bytes on wire, 42 bytes captured)
Ethernet II, Src: 192.168.0.51 (00:20:e0:96:0b:e9), Dst: Broadcast
(ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)

No. Time Source Destination Protocol
Info
6 8.005267 192.168.0.207 192.168.0.51 ARP
192.168.0.207 is at 00:12:3f:87:c6:f9

Frame 6 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 192.168.0.207 (00:12:3f:87:c6:f9), Dst: 192.168.0.51
(00:20:e0:96:0b:e9)
Address Resolution Protocol (reply)

No. Time Source Destination Protocol
Info
7 8.005304 192.168.0.51 192.168.0.207 DNS
Standard query A job.juth.org

Frame 7 (72 bytes on wire, 72 bytes captured)
Ethernet II, Src: 192.168.0.51 (00:20:e0:96:0b:e9), Dst: 192.168.0.207
(00:12:3f:87:c6:f9)
Internet Protocol, Src: 192.168.0.51 (192.168.0.51), Dst: 192.168.0.207
(192.168.0.207)
User Datagram Protocol, Src Port: autodesk-nlm (2080), Dst Port: domain (53)
Domain Name System (query)
Transaction ID: 0x79a9
Flags: 0x0100 (Standard query)
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 0
Queries
job.juth.org: type A, class IN
Name: job.juth.org
Type: A (Host address)
Class: IN (0x0001)

No. Time Source Destination Protocol
Info
8 8.036965 192.168.0.207 192.168.0.51 DNS
Standard query response, No such name

Frame 8 (72 bytes on wire, 72 bytes captured)
Ethernet II, Src: 192.168.0.207 (00:12:3f:87:c6:f9), Dst: 192.168.0.51
(00:20:e0:96:0b:e9)
Internet Protocol, Src: 192.168.0.207 (192.168.0.207), Dst: 192.168.0.51
(192.168.0.51)
User Datagram Protocol, Src Port: domain (53), Dst Port: autodesk-nlm (2080)
Domain Name System (response)
Transaction ID: 0x79a9
Flags: 0x8183 (Standard query response, No such name)
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 0
Queries
job.juth.org: type A, class IN
Name: job.juth.org
Type: A (Host address)
Class: IN (0x0001)

No. Time Source Destination Protocol
Info
9 8.037236 192.168.0.51 192.168.0.207 DNS
Standard query A job.juth.org.juth.org

Frame 9 (81 bytes on wire, 81 bytes captured)
Ethernet II, Src: 192.168.0.51 (00:20:e0:96:0b:e9), Dst: 192.168.0.207
(00:12:3f:87:c6:f9)
Internet Protocol, Src: 192.168.0.51 (192.168.0.51), Dst: 192.168.0.207
(192.168.0.207)
User Datagram Protocol, Src Port: autodesk-nlm (2080), Dst Port: domain (53)
Domain Name System (query)
Transaction ID: 0x4dc5
Flags: 0x0100 (Standard query)
Questions: 1
Answer RRs: 0
Authority RRs: 0
Additional RRs: 0
Queries
job.juth.org.juth.org: type A, class IN
Name: job.juth.org.juth.org
Type: A (Host address)
Class: IN (0x0001)

No. Time Source Destination Protocol
Info
10 8.038701 192.168.0.207 192.168.0.51 DNS
Standard query response, No such name

Frame 10 (134 bytes on wire, 134 bytes captured)
Ethernet II, Src: 192.168.0.207 (00:12:3f:87:c6:f9), Dst: 192.168.0.51
(00:20:e0:96:0b:e9)
Internet Protocol, Src: 192.168.0.207 (192.168.0.207), Dst: 192.168.0.51
(192.168.0.51)
User Datagram Protocol, Src Port: domain (53), Dst Port: autodesk-nlm (2080)
Domain Name System (response)
Transaction ID: 0x4dc5
Flags: 0x8583 (Standard query response, No such name)
Questions: 1
Answer RRs: 0
Authority RRs: 1
Additional RRs: 0
Queries
job.juth.org.juth.org: type A, class IN
Name: job.juth.org.juth.org
Type: A (Host address)
Class: IN (0x0001)
Authoritative nameservers

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

Hmmm.... please export your zone and copy & paste it into a reply here.
Or if it's not something appropriate for public eyes, mail it to me at
"nscsysop at comcast dot net". If you mail it, please post here to let
me know as mail to that address is frequently spamified and I have to
go look for it.

bd
NSC Volunteer SysOp


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

On Fri, 17 Feb 2006 16:13:54 GMT, Brad Doster <bd@NSCSysOps.net>
wrote:

>Hmmm.... please export your zone and copy & paste it into a reply here.
> Or if it's not something appropriate for public eyes, mail it to me at
>"nscsysop at comcast dot net". If you mail it, please post here to let
>me know as mail to that address is frequently spamified and I have to
>go look for it.
>
>bd
>NSC Volunteer SysOp
>


Hi Brad,

Just emailed the file. Subject is DNS Strangeness.

Thanks.

Jim
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

Jim Huddle wrote:
> Hi Brad,
>
> Finally had a moment to run ethereal. I did it from a suse 10 laptop.
>
> The server is replying, just saying there's no such name.


I saw something very similar to this last night, though it was a reverse
(PTR) lookup on OES 6.5SP4a system.

I had a secondary zone and associated .arpa reverse lookup table that I
imported from a linux box and it has been there for some weeks now. The
workstations refer to the Netware DNS for everything and it was updated
from the Suse Linux box however it was inconvenient to have to go to the
suse box to make changes, so having (finally) figured out how DNS/DHCP
manager works (well mostly) I decided to bite the bullet and let Netware
do it alone. So I changed the secondary zone and it's associated .arpa
file to primary, changed the SOA information to refer to the Netware box
and restarted the DNS server. Tested the resolver and it worked fine on
both name lookup and reverse lookup from a desktop.

I added an A record and that was resolved ok. I went to create the PTR
record and it spat me out saying it already existed (apparently it
automatically creates a PTR in the .arpa file when you create an A
record (which is a good thing of course). However I found it would
resolve the hostname to ip fine, but reverse came up 'no record'.
Restarted the DNS a couple of times - no change in behaviour. So I
deleted the PTR record and recreated it manually, despite being able to
see nothing wrong with it and all the other PTR records were resolving
without a problem. Worked straight away. I put it down as a one of
aberration, but I have more records to enter next week, so I'll see if
the behaviour repeats.

I couldn't see anything wrong with the PTR record at all.

Wondering if the DNS manager is updating the PTR but not the serial on
the database or something similar, whereas it does so at once when you
manually create it?


--
Geoff Roberts
IT Support
Saint Mark's College
Port Pirie, South Australia
geoffrobx@stmarksx.ppx.catholicx.edux.aux
Remove all x's from email address....
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES DNS server can't resolve itself

That's interesting. I tried deleting/readding the A and NS records
before without any luck. Guess it couldn't hurt to try again.

This wasn't a "move" though. I simply added this box as a DNS server
and removed the previous box, also OES NW.

Jim
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.