Windows 2012 R2 DNS ListenAddresses Null Value

We are having DHCP / DNS update issues and all recommned setting from Microsoft have not helped. On our DNS servers which are also DC's the ListenAddresses is set to a Null Value? Is this the default and if so should I try to change it as recommended in the following article?
LVL 21
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I have this for all my DC's as well, the listenaddress value is null. I have no problem with dynamic DNS registration.

I came across this same article myself when investigating a dynamic DNS registration problem with DHCP, but it seemed irrelevant so I ignored it.

As an alternative possible solution, I would recommend looking to your DHCP logs. If you do not have logging enabled then enable it. What I found was that dynamic DNS registrations were failing because somebody set up a DHCP scope for BYOD devices that had a multitude of DNS suffixes for which I had no DNS zone. So thousands of BYOD devices were trying to register for a DNS zone that did not exist (bobs-mpb.home.local, janes-ipad.local, etc.). This led to the DNS update queue maxing out on the DHCP server (I think the default queue size is 2000) which led to DNS registrations failing intermittently for legitimate devices.

The fix is simple (for my scenario), disable dynamic DNS registrations for scopes that these people had setup for dynamic registration via the scope properties (DNS tab).

The particular errors I was seeing in DHCP were of course ID 31 but also ID 34 "DNS update requests queue limit exceeded". I think DNS gets blamed a lot, but as long as you have your DHCP service account in the DnsUpdateProxy group and your scopes are correctly configured you should be fine.

Interestingly in server 2016 you can now apply DNS suffix rules around DHCP dynamic DNS updates which is super cool.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
compdigit44Author Commented:
thank you very much I do have DHCP logging enabled but it just says DNS update filed with the host name and not much more valuable information.
Does the DNS suffixes for the fails match your internal DNS zones?
Have you configured the DHCP service account, an have you configured all of your DHCP servers to use the same DHCP service account?
Is your DHCP service account a member of the DnsUpdateProxy group? (see here).
compdigit44Author Commented:
Yes everything is configured corrected and did open a case with MS support who confirmed our setup is correct. We are now looking at more of a network connection issue
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.