dgr360
asked on
Want Help in Configuring DNS under Windows NT 4.0
HI! ppl,
Will you ppl will help me to configure DNS under Windows NT 4.0..... I have already Installed MS DNS Server and i have Given the ZONE and DOMAIN with the "A" Record..... but the thing is that on the same Machine when i NSLOOKUP, i get the following .....
DNS request Time out.
timeout was 2 seconds.
***** can't find server name for address 127.0.0.1: Timed out
***** Default servers are not available
Default Server: UnKnown
Address: 127.0.0.0
CAN any one have the idea what mistake i m making....
........dgr360
P.S. : when i did add "A" record and enable "Creat an Association with PTR".... it shows a warning about no reverse-lookup????
Will you ppl will help me to configure DNS under Windows NT 4.0..... I have already Installed MS DNS Server and i have Given the ZONE and DOMAIN with the "A" Record..... but the thing is that on the same Machine when i NSLOOKUP, i get the following .....
DNS request Time out.
timeout was 2 seconds.
***** can't find server name for address 127.0.0.1: Timed out
***** Default servers are not available
Default Server: UnKnown
Address: 127.0.0.0
CAN any one have the idea what mistake i m making....
........dgr360
P.S. : when i did add "A" record and enable "Creat an Association with PTR".... it shows a warning about no reverse-lookup????
You will have to create a reverse lookup zone for that IP-subnet (127.x.x.x). In that subnet, create a PTR record (PTR --> resolves IP to name) for your nameserver (127.0.0.1). Should work then.
Ok, you're right. I only deal with 2000.
So in NT I guess you have to create a primary zone in the in-addr.arpa domain, e.g 127.in-addr.arpa (I'm not 100% sure, but something like that). This a reverse lookup zone and can therefore contain PTR records.
Good luck.
So in NT I guess you have to create a primary zone in the in-addr.arpa domain, e.g 127.in-addr.arpa (I'm not 100% sure, but something like that). This a reverse lookup zone and can therefore contain PTR records.
Good luck.
ASKER
yes, you are right about this because i have tried this and it did associate with the PTR record..... just as it was writen in the following site:
http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/winntas/deploy/confeat/install.asp
but the thing is that i am still unable to NSLOOKUP on the same machine......
dgr360
http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/winntas/deploy/confeat/install.asp
but the thing is that i am still unable to NSLOOKUP on the same machine......
dgr360
Ok, three things to try:
1. Use another IP (not 127.0.0.1); you should have an IP for the box as I guess it's on a lan. Otherwise it would not make much sense to use it as DNS-server.
2. Delete the A-record for the NS itself and create a new one (again, don't use 127.0.0.1).
3. Could you post the output of an "ipconfig /all"?
1. Use another IP (not 127.0.0.1); you should have an IP for the box as I guess it's on a lan. Otherwise it would not make much sense to use it as DNS-server.
2. Delete the A-record for the NS itself and create a new one (again, don't use 127.0.0.1).
3. Could you post the output of an "ipconfig /all"?
ASKER
I am not using this IP (it was an example), but the thing is when i NSLOOKUP it shows 127.0.0.1 as a server ip....
i think it is becuase of the local host entry some where....
i will check this out ....
You are a good help to me......
i will my best to resolve it..
dgr360
i think it is becuase of the local host entry some where....
i will check this out ....
You are a good help to me......
i will my best to resolve it..
dgr360
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>Do you have the DNS server configured correctly in your IP-configuration? Therefore the "IPCONFIG /all" output would be interesting.
Agree with Wonko this is the most likely reason for it using 127.0.0.1 as the server. You can work around it by using "server 10.1.1.1" command in nslookup.
Some things to check,
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q166753
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q171789
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q172953
Agree with Wonko this is the most likely reason for it using 127.0.0.1 as the server. You can work around it by using "server 10.1.1.1" command in nslookup.
Some things to check,
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q166753
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q171789
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q172953
dgr360:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
ASKER