Constantly having to flush DNS

[Guest]

We have a number of CNAME entries in DNS. We have to flush/register DNS on
clients to be able to access the desired server by CNAME. Example, we have a
phone system that we can access by hostname, IP address or the CNAME
“phonesystemâ€. It is always available by hostname and IP. “Phonesystemâ€
will work most of the time, however every once in a while (what seams random)
it will bring up a live search looking for it on the internet. To fix it you
have to flush/register DNS. We have recently put a sharepoint site online
and there is a CNAME “sharepointâ€, I am seeing the same thing with
“sharepoint†and it is getting old walking users through flushing DNS. Is
there any suggestions?
Thanks.

 

[Herb Martin]

We have a number of CNAME entries in DNS. We have to flush/register DNS
on
clients to be able to access the desired server by CNAME. Example, we
have a
phone system that we can access by hostname, IP address or the CNAME
"phonesystem". It is always available by hostname and IP. "Phonesystem"
will work most of the time, however every once in a while (what seams
random)
it will bring up a live search looking for it on the internet. To fix it
you
have to flush/register DNS.

Live search tends to kick in when there are no DOTS in the DNS name (and
you don't bother with the HTTP:// - If these are www.-----.com addresses
then
teach your users to hit Ctrl-Enter to get the prefixed-suffixed
automatically.

As to the need to flush/register that is absolutely abnormal; do you have
ISP
or other EXTERNAL DNS servers listed on your DNS CLIENT NICs?

You must list ONLY your INTERNAL DNS on the internal DNS clients.
This includes DCs and other servers which also "DNS Clients".

We have recently put a sharepoint site online
and there is a CNAME "sharepoint", I am seeing the same thing with
"sharepoint" and it is getting old walking users through flushing DNS. Is
there any suggestions?

If you are using CNAMEs for SMB shares that requies special registry
settings.

 

[Guest]

Thanks! It was an external DNS server listed in the DHCP options.

 

[Herb Martin]

Thanks! It was an external DNS server listed in the DHCP options.

People do that usually in the mistaken belief that this is the way to
resolve "The Internet" so if you haven't already, set your internal
DNS servers to handle Internet resolution, usually by having them
forward to a firewall/gateway DNS or you ISP DNS server.