Nslookup Error

[Justin]

Anyone able to help me solve this:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>nslookup
*** Can't find server name for address 192.168.1.3: Non-existent domain
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.1.3

Both on workstations and 2000 Servers.

Thanks

 

[Kevin D. Goodknecht Sr. [MVP]]

In Justin <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.

Anyone able to help me solve this:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>nslookup
*** Can't find server name for address 192.168.1.3: Non-existent
domain
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.1.3

Both on workstations and 2000 Servers.

Thanks

Either you don't have a reverse lookup zone configured or you don't have PTR
records in it for the IP address

 

[Kevin D. Goodknecht Sr. [MVP]]

In Justin <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.

I have a reverse zone configured - how do iconfigure the ptr record?

THanks

In Justin <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.

Anyone able to help me solve this:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>nslookup
*** Can't find server name for address 192.168.1.3: Non-existent
domain
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.1.3

Both on workstations and 2000 Servers.

Thanks

Either you don't have a reverse lookup zone configured or you don't
have PTR records in it for the IP address

If you have the zone properties set to allow dynamic updates Netlogon will
create the records. Otherwise you'll have to manually create the PTR
records. the zone should be either 168.192.in-addr.arpa with a sub domain
named 1 and a PTR record named 3 and the FQDN host name or
1.168.192.in-addr.arpa with the PTR name 3 and the FQDN

You cannot use 192.in-addr.arpa because the will conflict with public
reverse lookup zones

 

[Justin]

I have a reverse zone configured - how do iconfigure the ptr record?

THanks

In Justin <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.

Anyone able to help me solve this:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>nslookup
*** Can't find server name for address 192.168.1.3: Non-existent
domain
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.1.3

Both on workstations and 2000 Servers.

Thanks

Either you don't have a reverse lookup zone configured or you don't have PTR
records in it for the IP address

 

[Justin Martin]

I am totally lost - sorry . The only in-addr.arpa stuff I have is for 0....
127... and 255...

Not too sure what the next step is. Create new Zone -> AD integrated ->
Reverse ->Select reverse name based on what you have given me below?

I have IP ranges 192.168.251.0, 192.168.252.0, 192.168.253.0 and
192.168.254.0 - do I need to do this for each range?

Thanks
Justin

In Justin <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.

I have a reverse zone configured - how do iconfigure the ptr record?

THanks

In Justin <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.
Anyone able to help me solve this:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>nslookup
*** Can't find server name for address 192.168.1.3: Non-existent
domain
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.1.3

Both on workstations and 2000 Servers.

Thanks

Either you don't have a reverse lookup zone configured or you don't
have PTR records in it for the IP address

If you have the zone properties set to allow dynamic updates Netlogon will
create the records. Otherwise you'll have to manually create the PTR
records. the zone should be either 168.192.in-addr.arpa with a sub domain
named 1 and a PTR record named 3 and the FQDN host name or
1.168.192.in-addr.arpa with the PTR name 3 and the FQDN

You cannot use 192.in-addr.arpa because the will conflict with public
reverse lookup zones

 

[Kevin D. Goodknecht Sr. [MVP]]

In Justin <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.

Thanks again for all of the help/

Justin

I am totally lost - sorry . The only in-addr.arpa stuff I have is
for 0.... 127... and 255...

Not too sure what the next step is. Create new Zone -> AD integrated
-> Reverse ->Select reverse name based on what you have given me
below?

I have IP ranges 192.168.251.0, 192.168.252.0, 192.168.253.0 and
192.168.254.0 - do I need to do this for each range?

Thanks
Justin

In Justin <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.
I have a reverse zone configured - how do iconfigure the ptr
record?

THanks

message In Justin <[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.
Anyone able to help me solve this:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>nslookup
*** Can't find server name for address 192.168.1.3:
Non-existent domain
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.1.3

Both on workstations and 2000 Servers.

Thanks

Either you don't have a reverse lookup zone configured or you
don't have PTR records in it for the IP address



If you have the zone properties set to allow dynamic updates
Netlogon will create the records. Otherwise you'll have to
manually create the PTR records. the zone should be either
168.192.in-addr.arpa with a sub domain named 1 and a PTR record
named 3 and the FQDN host name or
1.168.192.in-addr.arpa with the PTR name 3 and the FQDN

You cannot use 192.in-addr.arpa because the will conflict with
public reverse lookup zones

No Problem