Re: nslookup shows wrong domain when using forwarder

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Jonathan de Boyne Pollard (J.deBoynePollard_at_Tesco.NET)
Date: 02/27/04 

Date: Fri, 27 Feb 2004 17:20:37 +0000

a> When I use nslookup with a non fqdn like "server1" which doesn't
a> exist in the comp1.com zone but exists in the comp2.com zone, it
a> will always return "comp1.com" instead of "comp2.com".

DNS servers don't deal in anything _but_ fully-qualified domain names. So
before your query from "nslookup" even reached your server, it was converted
to using a fully-qualified domain name by your DNS Client.

This is a plain and simple DNS Client configuration issue.

Relevant Pages

  • Re: Add FQDN host name to windows 2000 dns
    ... One cannot add data to a "zone" that aren't for a domain name within that "zone". ... That's the search path in the nslookup ... DNS Client at work, and nothing to do with your DNS server. ...
    (microsoft.public.win2000.dns)
  • Re: Start of Authority and Zone Transfers
    ... The DNS servers are peers and each one ... considers itself authoritative for that zone. ... > 'server1.domain.com' listed as the start of authority. ... Should Server1 list Server2 as it's SOA and vise ...
    (microsoft.public.win2000.dns)
  • Re: Delegation of Reverse Zones
    ... I am trying to figure out Delegations of reverse lookup zones. ... If you need to delegate a zone, you will setup a zone on ... and you will setup delegation on Server1. ... I cant figure out how delegation of reverse zones works. ...
    (microsoft.public.cert.exam.mcse)
  • Re: Ereignis ID: 3034 (Redirectordienst)
    ... Server1: DC, DNS; IP 192.168.2.2 ... Wenn ich nslookup 192.168.2.2 an einem TS eingebe bekomme ich ... Wenn ich einen Ping mit dem Namen des Server1 absetze bekomme ich die ... Next by Date: ...
    (microsoft.public.de.german.win2000.termserv.apps)
  • Re: DNS - 2 domains, through VPN
    ... Thanks kevin - that is great advice, ... On the other hand, to properly set this up is fairly simple, on each DNS ... the Zone transfers tab, select "Only to these IP addresses" and enter the IP ... On server1 Create a new secondary zonefor the name of the zoneon ...
    (microsoft.public.win2000.dns)