dns issue

[bilbonvidia]

I put a new server in which was originally set up for dhcp and got address *.*.*.117 which was registered in DNS. I changed to .3 static and deleted the dns record and added the correct one in (A) manually. All was working fine on Friday clients could connect okay but today Monday when users try and connect they are unable as they are trying to connect to *.117 for some reason again. Tried doing a repair on their connection but the same. Cleared cash on the dns server still picking up 117 which does not exist. Where else would they be getting this from.
Putting dns suffinx in their connection properties at the top of the list seems to be working as a work around for now. But where could they still be getting 117 for this server?

 

[Roadki11]

try at a command line on the clients ipconfig /flushdns, see if that helps.

RoadKi11

 

[Davetoo]

Did you change your DHCP options to have them point to .3 for DNS as well?

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

 

[bilbonvidia]

Thanks no joy with the flushdns, (doing a repair on the connection clears all cache including dns)

The the dns server is separate to this server and has not changed so changing dhcp wont help there.

Why would adding the local domain suffix to the top of append suffix option under connection properties o the clients resolve the problem? Should clients not already try the suffix of the local domain first any way? I think that without this the server is being resolved to an address on a different domain which is not active. The server was originally built in another domain, but still I would have thought this should not matter as local suffix and dns should be queried 1st. I hope I make sense?

 

[Davetoo]

My bad...read it as the DNS server being the .117 switched to .3.

Go to your DNS server and ping the FQDN, does it come back right? If not, flushdns on the server and try again to confirm it's reading from your DNS.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

 

[bilbonvidia]

Yeah it comes back when I ping FQDN but I still get not reply from the original dhcp ip when just pinging servername after having flushed the dns? Wierd.

 

[Davetoo]

Sorry...not following you here.

What happens when you go to your DNS server and ping the FQDN? Do you get a response from the correct .3 IP address or from the old DHCP .117 address?



I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

 

[bilbonvidia]

when FQDN used all is okay. When just server name is used i get the .117.

I have changed group policy to set the local domain name in the top of the suffix search order which will resolve the problem so when ping (servername) the correct FQDN is used.

I think this has happened because the server in question was set up in another domain so when it got the 117 address this was registered somwhere in the rest of the organisations dns. I moved the server to our domain and changed address to .3 but because the clients trying to connect had the domain that the 117 was registered in high up in the append suffix in order section on the dns tab their tcp/ip properties they were getting the wrong ip address for the server. I hope I am making sense?

 

[Davetoo]

Yes. Best thing you could do, if you could, is rename the server. Short of that, you'll have to touch every DNS server within your organization and find the one that's still holding the old name. Because it exists somewhere it's always going to answer to the non-FQDN.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.