DNS Issues - Missing Record (but not missing)

[mcrompton01]

Hi,

I was hoping someone would be able to help us, we have been plauged by a DNS issue and cannot find a solution that works. It can take up to 40 minutes for students/staff to logon at random times during the day (not able to track igt to one user and no errors/warnings shown in the event log).

We have 2 DNS servers that have a active directory integrated zone on called PDC and the other RDC.

We have ran the following commands (the results of which can be seen in the attached files):
dcdiag /s:kng-pdc-001 /test:DNS
dcdiag /s:kng-rdc-002 /test:DNS

We have lots of missing records on the RDC however, when you look in DNS on that server they are all present, the settings on each server are identical....

We have tried a server restart, Netlogon restart, DNS restart, adding and deleting records manually and nothing works.

We are starting to tear our hair out and I've not got much left anyway.

Cheers and thanks in advance.
Mark

KNG-PDC-001.txt
KNG-RDC-001.txt

[mcrompton01]

[Update]
This only shows when running dcdiag from a workstation (with the windows 7 admin pack installed). when run from the offending server it reports fine no errors.

[RageRiot]

This wont help but It might be the active directory portion of DNS thats seems faulty. I'll keep an eye on this thread as it might prove useful to know the cause and solution should you find it.

I'm still very new to windows server / AD / DNS, etc

[Michael]

Thinking about it, you shouldn't have to be manually creating/deleting records if the servers are replicating correctly. I would double check this and ensure your Forward and Reverse Lookup Zones can transfer to each other.

Also, do the name servers on both Forward and Reverse Lookup Zones look correct?

[HallX]

Thinking about it, you shouldn't have to be manually creating/deleting records if the servers are replicating correctly.

I agree. Would it be worth removing DNS completely from RDC and pointing all your clients to PDC? After 24 hours or so, add the DNS role again to RDC.

[glennda]

Yes - you can also setup DHCP to for DNS updates when it leases a client an address. This tends to ensure that the clients are requesting updates.

But there are various tests people have mentioned which can help solve the replication between them

[mcrompton01]

Thanks for the replies, we mamually deleted and removed the records as a test and nothing more, it was suggested on technet.

@glennda - could you elaborate, do you know what settings are required to do this.

Replication is working fine and no errors/warning, so we are happy with it. We have forced each server to update and again no problems.

It has crossed my mind to remove dns from RDC then add it back in again later. Like I say the messages are only displayed on the client, when running the command on the servers does not produce any error message.

One last question, do/should I be using option 015 on the dhcp server or should the clients work it out for themselves?

Will keep you posted about install/uninstall.

[glennda]

Open dhcp then properties select dns choose something like update dns even when clients don't request

It's something like that

[mcrompton01]

Cheers Glennda for that butthat option is already ticked. I think I'll be uninstalling/reinstalling dns after school tomorrow.

Thanks again

[glennda]

Cheers Glennda for that butthat option is already ticked. I think I'll be uninstalling/reinstalling dns after school tomorrow.

Thanks again

If that is not updating the dns then could it not be dhcp causing an issue? Although the clients should still update the dns