NSLOOKUP only works using DNS server IP

  • Thread starter Thread starter TRB_NV
  • Start date Start date
T

TRB_NV

I installed DNS on a W2K server using the default settings and can't get
NSLOOKUP to work properly without using the DNS server's IP. I added a test
entry, test.domain.com -- 192.168.1.123 in the host table. I'm using W2K
server with the most recent service packs installed as a single server (No
Active directory).
NSLOOKUP
Click to expand...
server ns1.domain.com
test.domain.com
*** ns1.domain.com can't find test.domain.com: Non-existent domain
NSLOOKUP
Click to expand...
server 192.168.1.104
test.domain.com
name: test.domain.com
address: 192.168.1.123

Portion of host table follows:
\winnt\system32\domain.com.dns
; Zone NS records
;

@ NS ns1.
ns1. A 192.168.1.104

;
; Zone records
;

test A 192.168.1.123
ns1 A 192.168.1.104
 
In
TRB_NV said:
I installed DNS on a W2K server using the default settings and can't
get NSLOOKUP to work properly without using the DNS server's IP. I
added a test entry, test.domain.com -- 192.168.1.123 in the host
table. I'm using W2K server with the most recent service packs
installed as a single server (No Active directory).

server ns1.domain.com
test.domain.com
*** ns1.domain.com can't find test.domain.com: Non-existent domain

server 192.168.1.104
test.domain.com
name: test.domain.com
address: 192.168.1.123

Portion of host table follows:
\winnt\system32\domain.com.dns
; Zone NS records
;

@ NS ns1.
ns1. A 192.168.1.104

;
; Zone records
;

test A 192.168.1.123
ns1 A 192.168.1.104
Click to expand...

What DNS is listed in TCP/IP properties?
It looks to me like what ever DNS it is starting with cannot resolve
ns1.domain.com.
Plus it looks like in your NS record ns1. does not have a domain suffix.
 
The DNS listed under TCP/IP properties is for my ISP (216.254.95.2 /
216.231.41.2)

Thanks
 
In
TRB_NV said:
The DNS listed under TCP/IP properties is for my ISP (216.254.95.2 /
216.231.41.2)
Click to expand...
Then that would be the problem, when you start nslookup it is pointing to
your ISP's DNS when you input server ns1.domain.com it asks your ISP's DNS
for the IP for that name, of course your ISP's DNS cannot do a lookup for a
name that only your local DNS has the answer to.
I would suggest that you use your local DNS in TCP/IP properties, then
configure it to forward unknown domains to your ISP's DNS. It this were an
AD domain using your local DNS would be required.
It does little good to have a local DNS server and not use it which is what
your current configuration is doing, if you do not have your local DNS in
TCP/IP properties it will not be queried.
300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1
 
Back
Top