DNS problem: differences in response time between domain names and subdomains

We changed our company name, and thus our domainname (newdomain.com) as well. We still have the old name (olddomain.com), and it is still the name of our Active Directory. Both domain names point to the same machine / server / website. If I open a test page (/test.html) via the old domain name, it takes about 0.2 second to respond. If I open the same page using the new domain name, it takes about 2 seconds longer. (I've created a simple testpage on an external website that calls an include from our site and measures the difference in response time between both URLs. This is repeated several times to see if it's consistent, which it is.)

If I open the DNS (Windows 2000 Server), I see a Forward Lookup Zone, and a Reverse Lookup Zone. The Reverse Loopup Zone has one subnet, with a WINS reverse lookup for the olddomain, and an alias for the newdomain.

The Forward Lookup Zone has two zones defined for both domain names. In the old zone, I see all machines that are connected to the network, plus the name servers, Start of authority, www (as host), WINS. Furthermore, I see four folders (_msdcs, _sites, _tcp, _udp).

The new domain zone didn't have the same properties at first. I changed those to match the old zone, but that didn't have any effect. It had name servers, SOA, WINS and www (as alias). I removed that last alias (www) and replaced it with a host. I linked this host directly to the ip-address of the webserver.

The result of the change is that www.newdomain.com is as fast as www.olddomain.com or olddomain.com. Still, newdomain.com is slow. I would like to have newdomain.com as fast as the others. Furthermore, I wonder if this is the right way to do this. If in the future I move the webserver to another machine with a different ip, this host won't update by itself I suppose.
Who is Participating?
Gen2003Connect With a Mentor Commented:
Some tips:

- Do you really need WINS? If not switch it off.
- Check any static mappings in WINS. Try to have the same records for newdomain as for olddomain.
- Create reverse zone for newdomain.

grexxAuthor Commented:
I don't know if I need WINS, and don't know how to turn it off. Is just removing the WINS lookup in both the Forward Lookup Zone and Reverse Lookup Zone of the old domain enough? I opened WINS, and it showed one active server. If I opened Active Registrations or Replication Partners, it just displayed a help text, no list.

If I remove WINS from the FLZ, do I still need to check for those static mappings?

How do I setup a new reverse zone? I see one zone: 192.168.x.x. It has the olddomain.com as WINS, newdomain.com as alias, a nameserver and Start of Authority.
- To remove WINS delete all related records from FLZ. On machines with static network addresses delete WINS server TCP/IP properties, if DHCP server is in use delete related options from DHCP scope.

- Another tip: STOP old WINS server and start it on newdomain computer. Make mentioned changes in DNS and DHCP to reflect changes.

To create reverse zone open RLZ and create it with the same numbers as old RLZ you have, but change names to newdomain. Or - try to create A record in FLZ (newdomain) with option to create reverse pointer. It will probably automatically create RLZ for your new domain.

Even you can try to delete RLZ and recreate it again.
grexxAuthor Commented:
Sometimes the solution is a lot simpler than it first appears. :-)

I removed WINS, but that didn't make any difference. Then I realized I had another domain name, with no FLZ at all. When I tested that domain name, it was as quick as the old domain name. So I removed the FLZ for the new domain name, and then suddenly it was as fast as the old domain! Problem solved!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.