dns resolution on lan problem

[elmurado]

Ok, starting to get this problem, if I ping on our lan by hostname-sometimes it resolves and finds the machine in question-other times it is routed externally to park.planetdomain.com
which looks like some kind of hosting company.

I thought that if the dns server ( a w2003 box) can't resolve something it should hand it to the forwarder sepcified in the dns settings(in this case our isp's dns servers). Is there a hidden order to this?

Where does the park.planetdomain.com come in to it?
And why does it seem random?

What's weird is that when this is happening, I can see strange outgoing connection attempts from different machines through our firewall:
04/23/08 14:37 firewalld[121]: deny out eth1 64 tcp 20 128 x.x.x.x 202.131.95.30 2385 2222 syn (Outgoing)

This only happens when the hostname resolution problem is happening. Otherwise no weird connection attaempts. Which makes me think that the connections usually take place but are routed correctly on the LAN.

the 202.131.95.30 is the IP of park.planetdomain.com
Anyone have an idea what might be happening here?
Is it because I have something wrong setup in dns suffixes?

 

[theravager]

You probibly haven't deleted the root hints which is letting the server resolve dns entries instead of passing it to the forwarded. Recursion is also an option here that affect how this works.

 

[elmurado]

Point is, I want the dns server to resolve internal enquiries
and only forward if it doesn't have the details. ie external hostnames
Don't I?