Networks

Ask something
Discussion Locked

www. what?

0 helpful
9 replies

by daniel.quick

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Here is the problem. I have IIS 4.0 installed/ NT 4.0 Server/ Internal DNS and External DNS servers setup on two different boxes.

once upon a time www.mycompany.org's internal ip address issued by the internal DNS was 192.168.1.200. I recently changed the ip address and the nslookups report the change to ip address 192.168.2.200 opposed to the 192.168.1.200. If you ping the A record though, it returns 192.168.1.200 even though the most recent A record reports 192.168.2.200. The external DNS server reports the correct IP address.

Help, if you need anymore info. please let me know.

Daniel

9 replies

by jb007

Tried looking at WINS? Is there an old entry in there that can be removed? you can sort by IP Address and take a look at the old IP entry.

There are only a few locations this could also be at like:

hosts file entry?

Another A record entry on a secondary server perhaps?

Where are you pinging from also makes a difference.

Try it from the dns server and see if it sees the right address as opposed to a client.

hope this helps,

jb

by daniel.quick

Thanks, but this was not the case. Would use an A record, but cnames are recommended by the rfc's and http headers workbest with them.

Also, all dns queries are directed to the internal dns servers first, and then directed to the external dns server

by cavedweller

Use nslookup. Query your local servers and see what they answer. They might have the old value in their cache. It could also have been hardwired in the configuration files (unusual but possible). Nslookup should either find the problem server orlet you know to look elsewhere.

by stillatit

When you make a change to a DNS entry, you typically need to change the serial number in the SOA record. I am not sure that the MS GUI does this for you. If this has not done, you have not flagged the world to un-cache and reread your DNS.

Any station or DNS server which has cached your address keeps it until the TTL (time to live) expires. Some places have this set to as long as three months.

Any stations having a problem should be checked for the following:
1) Which DNS server are theyusing? (Then check that server)
2) Host file entries

If you get truely stuck, the best reference on DNS is the O'Reilly book on the subject.

Good luck.

by daniel.quick

MS DNS server automatically changes the serial number. Also, it has the option of manually updating the db files and then refreshing the cache and entries to reflect the correct chagnes.

by mebudman

Have you created a reverse lookup zone for the 192.168.2.* network. You have a reverse lookup entry for the 192.168.1.* subnet. Open it up and delete the 192.168.1.200 entry. This should fix the problem.

Hope this helps.

by daniel.quick

Yes, I have created the correct reverse lookups. Also, on MS DNS the reverse lookups when finished should look like this

2.168.192.in-addr.arpa

the db file should appear as 2.168.192.in-addr.arpa.dns

This discussion is closed to new replies.