Windows Forum

Ask something
Discussion Locked

DNS Server on NT4.0-No Reverse Lookup

0 helpful
5 replies

by fluffy

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

I have set up the DNS Manager on windows NT Server 4.0, but I believe that reverse-lookups are not being resolved. First of all this DNS Server is inside my companies firewall and is for the inside(intranet). Our external DNS(internet) is working fine. With my desktop pointed only at my new internal DNS Server, i can ping internally/externally. I am able to resolve on the internet as well as inside.But,when I execute an nslookup for any computer inside or out, the DNS times out, with no defaultserver available, it does show the ip address od my nameserver, but reads server: unknown. It does resolve the computer that I specify, but there seems to be a problem in resolving the name of my nameserver. Now I am aware of 4 files that exist in C:\winnt\sys32\dns --boot, cache, place.dom (domain.com.dns), and arpa###.rev. It is this last file, the reverse lookup, that is non-existent(i think). Idon't understand what it should be called exactly, I do have a model of what it should read. I have created the associated PTR record for all hosts added to domain.com.dns, but I can find no 'file' that was created by the gui setup. Where is this info going? Should I be looking towards the registry maybe? Tnanx for your help,
.....Keith Auerbach

5 replies

by jerrym mcse+i / a+

Hi Keith,
you need to create the reverse lookup zone, goto the microsoft knowledge base and get the article number Q172953, how to install and configure ms dns server, it explains exactly what you are trying to do.
Thank you for the post!!!...jer

by rwscc

I used a similar setup of NT4 dns for intranet and external name servers for internet. It is critical that each machines list of dns servers has the internal one listed first. If it is listed first, the problem is likely in the reverse lookup file. The names for the revers lookup files are based on the subnet address. If you defined a reverse lookup during the initial dns setup for subnet 172.16 and later add a device with address 172.17.1.1 the creation of a reverse pointer will fail. You can create additional reverse lookup files for additional subnets after the initial creation of forward zone.
Look for marked down books on the MCSE course NT in the Enterprize. It covers dns and dhcp and may only cost a feww bucks now that 2000 is out.

This discussion is closed to new replies.