DNS problem

Ok this one is confusing... So I just built a new web server on our local network. Everything on the server works fine now comes the tricky part. When users try connect to it by using the name only some can connect others cannot. However everyone can connect using the ip address. So obviously it would be a DNS issue. The server has one main ip address then there are 5 attached web server ip addresses.

Things Ive done:

Deleted the 5 attached website ip address from dns so now there is only the one main ip there attached to the name.

Made sure the forward & reverse lookup zones are accurate as far as record type and ip/name association.

They are identical on both our domain controllers/dns servers however one can connect using the name and one cannot. weird?

I did do ipconfig /flushdns and it didn't help multiple times lol.

Anyone seen this before?

Find more posts tagged with

Comments

Devilsbane

Are you sure that the servers that can't connect via the name are actually connecting via the ip? If all you are using is ping, it may be lying to you. Try doing a telnet over port 80 or access files off of the server to be sure that you are actually hitting the server.

loxleynew

Devilsbane wrote: »

Are you sure that the servers that can't connect via the name are actually connecting via the ip? If all you are using is ping, it may be lying to you. Try doing a telnet over port 80 or access files off of the server to be sure that you are actually hitting the server.

Yea they can connect using the ip not just ping it and another thing they can connect using the FQDN just not the host name.

Devilsbane

loxleynew wrote: »

Yea they can connect using the ip not just ping it and another thing they can connect using the FQDN just not the host name.

Is the default suffix configured correctly on those machines?

dynamik

Do you have the same DNS servers configured on all those machines? What do you get if you use nslookup?

tiersten

Is it doing a NetBIOS lookup? The host name resolution system in Windows is weird. If the DNS lookup fails then it will try NetBIOS.

loxleynew

nslookup said everything was the same as far as I could tell. Both A type records with correct PT records. It seems like all the hosts on the DC2 (we split up the network so half use DC1 and half use DC2) can not connect using the host name just the FQDN and ip. I reloaded the dns on dc2 so it should be identical to dc1 and still no luck.

loxleynew

tiersten wrote: »

Is it doing a NetBIOS lookup? The host name resolution system in Windows is weird. If the DNS lookup fails then it will try NetBIOS.

It seems to be but just for the one server, how do i disable that.

Ahriakin

Devilsbane wrote: »

Is the default suffix configured correctly on those machines?

You didn't answer DB on this question - I'd agree it sounds like a suffix issue if the FQDN is working. Chances are it's misconfigured on the other DHCP pool (presuming you are using DHCP)

loxleynew

Ahriakin wrote: »

You didn't answer DB on this question - I'd agree it sounds like a suffix issue if the FQDN is working. Chances are it's misconfigured on the other DHCP pool (presuming you are using DHCP)

Sorry for not replying work got busy. Yea the suffix was right, it was identical to DC1. I did get it to work and it makes little to no sense to me.

I did two things, one was I created a reservation with the name/ip in both primary and secondary dhcp servers. Then I went to the computer that couldn't connect to it by name and tried and it didn't work. Then I browsed for it through the network (like browsing all network computers/servers and scrolling to it) then it worked after I did that. Now it works all the time. Maybe DHCP just took time to populate over it still doesn't make much sense to me.

Thanks for your help!

Michael.J.Palmer

Yeah, sounds a bit weird. Not sure if flushing the DNS would have resolved it as well on those that it didn't work on, but now that it does work I guess you can ignore that bit.

I would have also suggested just statically placing the IP for the DNS server in one of the computers it didn't work in just to see if it was definitely a DHCP error or not.

Glad you got it worked out though.

tiersten

loxleynew wrote: »

Then I browsed for it through the network (like browsing all network computers/servers and scrolling to it) then it worked after I did that. Now it works all the time. Maybe DHCP just took time to populate over it still doesn't make much sense to me.

I'd still look into your DNS server and its settings. It sounds like you're doing NetBIOS name resolving since it only started working once you cached it from browsing the domain.

Hyper-Me

Are you connecting by NetBIOS name or FQDN?