Domain.local DNS issue

Hi.

For some reason my local company domain is not been resolved on the Pcs.

I have got domain.local in the DNS server pointing to 192.168.1.200 and when I do and NSLookup it resolves to 200 but it's not responding to a ping.

This is what the folder redirects using so users redirect are not working at the moment.

I have 2 DNS servers and I have cleared the cashe on both servers and also ipconfig /flushdns on the PC.

Thanks
Gareth_PointonAsked:
Who is Participating?
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.

Cliff GaliherCommented:
If nslookup works then your issue is not DNS. It is elsewhere. Bad subnet, routing table, or even firewall issues. Ping is more than just DNS, it actually sends packets and expects a response.
0
Gareth_PointonAuthor Commented:
Yes it's not able to resolve though to an IP address to send to though.

It's all on the same subnet.

There is also only one "same as root" in the DNS server.

I have another domain.info on the same forest and that's ok.
0
Cliff GaliherCommented:
Post your nslookup and ping outputs. What you describe is contradictory.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Pramod UbheCommented:
try to ping with fqdn and check if domain.local is added in dns suffix.
0
Gareth_PointonAuthor Commented:
Hi.

The issue was with an old abs server that was causing more other issues as well as this. Once I took that from the DNS, demoted it and also removed googles DNS from the dhcp then everything was ok.
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
Gareth_PointonAuthor Commented:
This fixed the issue
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.