Cisco network Registrar 6.1.2

hdepre · ‎07-28-2005

Hello,

We have a problem withour server Cisco Network Registrar backup utilisant "secondary zone").

OS: Windows 2000 SP4

Cisco network Registrar 6.1.2 (jan 2005)

After a non specified time, the server does not respond any more on requests DNS (ns= lookup is local on the server and does even not function anymore. A reload, start/stop of the service does not solve the problem, only a reboot completely solve the problem.

logs where it is working:

X14395: ----- TRANSMITTED -- X14395 -----

X14395: Transmitted to 192.168.205.102 over UDP (size$1)

X14395: <-

X14395: <- HEADER SECTION:

X14395: <- id = 61295

X14395: <- qr = 1 opcode = QUERY (0) aa = 0 tc = 0 rd = =

1

X14395: <- ra = 1 z = 0 (unused) rcode = NOERROR (0)

X14395: <- qdcount = 1 ancount = 2 nscount = 4 adcount = 4

X14395: <- QUESTIONS (1):

X14395: <- php.my-siemens.com IN A

X14395: <- ANSWERS (2):

X14395: <- php.my-siemens.com 300 IN CNAME equinox.erlm.siemens.de

X14395: <- equinox.erlm.siemens.de 3600 IN A 217.194.35.15

X14395: <- AUTHORITY RECORDS (4):

X14395: <- erlm.siemens.de 3600 IN NS syros.erlm.siemens.de

X14395: <- erlm.siemens.de 3600 IN NS emporio.erlm.siemens.de

equinox.erlm.siemens.de 3600 IN A 217.194.35.15

When the problem is there:

/2005 14:31:06 name/dns/1 Info Server 0 03593

X414570: ----- TRANSMITTED -- X414570 -----

X414570: Transmitted to 207.46.138.20 over UDP (size2)

X414570: <-

X414570: <- HEADER SECTION:

X414570: <- id = 18341

X414570: <- qr = 0 opcode = QUERY (0) aa = 0 tc = 0 rd ==

0

X414570: <- ra = 0 z = 0 (unused) rcode = NOERROR (0)

X414570: <- qdcount = 1 ancount = 0 nscount = 0 adcount = 0

X414570: <- QUESTIONS (1):

X414570: <- search.msn.com IN A

X414570: <- ANSWERS (0):

X414570: <- AUTHORITY RECORDS (0):

X414570: <- ADDITIONAL RECORDS (0):

X414570: <-

X414570: ----- END OF TRANSMITTED -- X414570 -----

There are no ANSWERS (0):"

The server master is working fine, the backup he is using the principle

de "secondary zone". We see in the logs the synchronisation is working between the 2 servers.

Many thanks

wong34539 · ‎08-03-2005

The problem may be due to database corruption. You can try doing the following steps to resolve this issue.

1. You can validate the database. Here are the steps to do that:

a. stop all servers.

b. change directory to network registrar\data\db

c. run this command: dbcheck -a mcddb

2. Do a keybuild.

run this command: keybuild mcddb

3. Restart your servers.

4. Rebuild your resource record indexes in DNS.

here is the command to do that:

dns rebuildRR-Indexes

5. If the above measures fail to help, backup your database before trying

further diagnostics.

6. Then try dropping the zone having difficulty and re-add it.

In most cases this will resolve the problem. Hope this helps.