Secondary DNS zone Reload issue.

Secondary DNS zone Reload issue.
I have one Primary DNS server and two secondary DNS servers.
one of the two scondary DNS server can reload the zones from the master with no issue.
But the other Secondary DNS server can not reload the zones from the primary DNS.
What I noticed in the properties of the zones in the Primary DNS server if I go to NS tab I see a star (*) next to the IP address of the Secondary DNS server that has issue, then I remove that server from NS tab then readd it manually and reload the zone, after a while it reloads succefuly.
WHat I noticed also When I try to remove the DNS server from teh NS tab I get a message saying "Do you want to delete host record SECONDARYDNSNAMESERVER.MYDOMAIN.COM [10.10.10.10]"
But I can 't see that host record for that DNS server in the zones at all, since there is no zone for MYDOMAIN.COM in that DNS server, though this DNS server is member of the domain MYDOMAIN.COM.

I restarted primary and seconday DNS many times and still have the same issue. I enabled logging in the Secondary DNS that has issue and noticed that it's the primary DNS that is refusing the transfer of the zone.

I have many zones, so I would like to know if there is a quick solution to fix this issue, instead of going zone by zone and do what I have done so far to fix one zone at a time.

Thanks

jskfanAsked:
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:

> But I can 't see that host record for that DNS server in the zones at all

Glue records like that tend to be considered "out-of-zone" and because of that don't display in the GUI. A bit annoying really. They can be added / removed using scripts if necessary. If the IP had a * beside it then no Glue was present in the zone anyway.

That means a zone called "domain.com" could potentially have a record like "ns2.otherdomain.com.  IN A 1.2.3.4" within the "domain.com" zone. But that record would not be visible within the GUI.

I guess it's set to allow zone transfers to all servers in the Name Server list? If so, you might consider changing it to a set list of servers and entering the IP addresses.

Chris
0

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
jskfanAuthor Commented:
I fixed it in a way that doesn't make sense to me.
I went to each zone and removed the server under NS tab, then just added where it was (I mean under NS tab) then reloaded the zone, after a little while   the records showed up for the zone.


 
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
DNS

From novice to tech pro — start learning today.