Warning: DNS Server: [computername] IP: <Unavailable> Failure:Missing glue A record

Ran a dcdiag /c /f:dcdiag.log and received the following warnings.

DC: sc.mydomain.corp
Domain: mydomain.corp                  
TEST: Delegations (Del)
Warning: DNS server: dc1.sub.mydomain.corp. IP: <Unavailable> Failure:Missing glue A record
Warning: DNS server: dc2.sub.mydomain.corp. IP: <Unavailable> Failure:Missing glue A record
Warning: DNS server: dc4.sub.mydomain.corp. IP: <Unavailable> Failure:Missing glue A record
Warning: DNS server: exdc1.sub.mydomain.corp. IP: <Unavailable> Failure:Missing glue A record

Info:
sc.mydomain.corp is my root domain controller
dc1, dc2,dc4, exdc1.sub.mydomain.corp are DCs in a subdomain.

I verified that each DC can resolve each other.
I ran dnslint /ad /s localhost and it stated there were no glue records missing

Ran the same dcdiag command on the other root DC and got the same errors. Ran the same dcdiag command on the DCs it stated were missing glue A records and it returned no errors

I see in TechNet, that error means The configured delegation is missing glue A record. It does not state how this occurs or how to resolve it. (http://technet.microsoft.com/en-us/library/cc776854.aspx)

Curious what else I could check that could be causing these errors, or warnings. Have seen other posts here about a DC that had been deleted. This is not the case as all these DCs are active.
LVL 1
strausyAsked:
Who is Participating?

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

x
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.

Chris DentPowerShell DeveloperCommented:

Find the Delegation in the parent zone, then open it's Properties. If  the Name Servers have IP addresses listed with IPAddress* then they are resolved separately instead of Glue being present.

You can fix it in the GUI by removing the Name Server and re-adding it, providing the IP address should add it back without the *.

Or you can use DNSCMD to fix it like:

DNSCMD /RecordAdd mydomain.corp dc1.sub.mydomain.corp. A <IPAddress>

Note the trailing "." on the dc1 name, you must maintain that or it will add a record relative to the mydomain.corp zone which is really really unhelpful.

HTH

Chris
1

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
strausyAuthor Commented:
Fixing the entries in the delegation worked. The entries were there, they just has an asterisk next to them. Removing the record and re-adding them resolved the isse.

The below commands also work when done on the DCs without proper glue records (taken from http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Q_24313463.html).

Stop the netlogon and the DNS service (at cmd prompt type net stop netlogon and net stop dns)

Go to %systemroot%\system32\config folder and then delete the netlogon.dns and netlogon.dnb files

Restart DNS and netlogon

Run netdiag /fix

My comments:
Then wait for replication and do a dcdiag /test:dns /dnsdelegation
0
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
Active Directory

From novice to tech pro — start learning today.