Need help!!!

  • Thread starter Thread starter Angel Menendez
  • Start date Start date
A

Angel Menendez

Hope somebody out there could help. I have one domain configured with two
sites. I have two DNS servers per site. I had all 4 DNS servers on the DNS
tab on the Advanced TCP/IP settings. I was having excessive synchronization
issues so I change each site to have only the DNS servers of that site and
forwarders to the other site. (Each site is actually to cities) When I did
that some users began to have some web pages redirected to other sites. For
example, when trying to go to usatoday.com the Yahoo.com page appear.

I cleaned the Internet cache on one of the servers to rebuild the database
and reboot all the servers and that seems to help but I still have a few
users with the same issue. Should I have cleaned the Internet cache in all
the servers? Do anyone out there have a better idea? My concern now is that
when I try to do a nslookup it says that it can find the server name for
address xxx.xxx.xxx.xxx.

Any ideas will be appreciated!
Angel
 
In
Angel Menendez said:
Hope somebody out there could help. I have one domain configured with
two sites. I have two DNS servers per site. I had all 4 DNS servers
on the DNS tab on the Advanced TCP/IP settings. I was having
excessive synchronization issues so I change each site to have only
the DNS servers of that site and forwarders to the other site. (Each
site is actually to cities) When I did that some users began to have
some web pages redirected to other sites. For example, when trying to
go to usatoday.com the Yahoo.com page appear.

I cleaned the Internet cache on one of the servers to rebuild the
database and reboot all the servers and that seems to help but I
still have a few users with the same issue. Should I have cleaned the
Internet cache in all the servers? Do anyone out there have a better
idea? My concern now is that when I try to do a nslookup it says that
it can find the server name for address xxx.xxx.xxx.xxx.

Any ideas will be appreciated!
Angel
Click to expand...
The nslookup error means that it cannot find a reverse lookup on the IP
address for the DNS server it is pointing to.

On the clients having the trouble you can try flushing the DNS resolver
cache with this command ipconfig /flushdns
 
I will try the flush on the workstations and I'll post back. On the reverse
lookup, do I need to add one manually?
 
Back
Top