I messed up my DNS test environment somehow. What I had originally tried to
do was multihome a DC running DNS to facilitate a migration, and as a result
now when I do a lookup against anything I get this...

C:\Documents and Settings\Administrator.ISTEST>nslookup pudge
*** Can't find server name for address 10.65.2.37: Non-existent domain
Server: UnKnown
Address: 10.65.2.37

Name: pudge.istest.com
Address: 10.64.3.54

pudge is a client(linux) that registered itself in DNS, however, 10.65.2.37
is my DNS server(named dnstestsrv2). This lookup was done from dnstestsrv2.
Why is this happening? Why isn't the server known? In the DNS zone for
istest.com I have NS records for dnstestsrv2.istest.com so it should know
that it is the nameserver for istest.com. I had since removed all the extra
IP's I put onto the domain controllers in an effort to rectify the situation,
but it still doesn't seemed to have done anything.

If anyone has any insight that would be grand. I moved DNS servers from
dnstestsrv to dnstestsrv2 in an effort to an issue I was having with
some linux clients.

this at one point used to work.. here's a bit from an earlier post from
another issue..
C:\Users\dmurphy>nslookup 10.64.3.104
Server: dnstestsrv.istest.com
Address: 10.65.2.34:53 - this is my AD DNS server, which is also a DC for
istest.com

Name: testmcaffee3.istest.com
Address: 10.64.3.106


To save time here is the output of ipconfig /all from dnstestsrv2

C:\Documents and Settings\Administrator.ISTEST>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : dnstestsrv2
Primary Dns Suffix . . . . . . . : istest.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : istest.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-0C-29-3D-69-8B
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.65.2.37
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.65.2.1
DNS Servers . . . . . . . . . . . : 10.65.2.37

C:\Documents and Settings\Administrator.ISTEST>



"infinitiguy" wrote:

> I messed up my DNS test environment somehow. What I had originally tried to
> do was multihome a DC running DNS to facilitate a migration, and as a result
> now when I do a lookup against anything I get this...
>
> C:\Documents and Settings\Administrator.ISTEST>nslookup pudge
> *** Can't find server name for address 10.65.2.37: Non-existent domain
> Server: UnKnown
> Address: 10.65.2.37
>
> Name: pudge.istest.com
> Address: 10.64.3.54
>
> pudge is a client(linux) that registered itself in DNS, however, 10.65.2.37
> is my DNS server(named dnstestsrv2). This lookup was done from dnstestsrv2.
> Why is this happening? Why isn't the server known? In the DNS zone for
> istest.com I have NS records for dnstestsrv2.istest.com so it should know
> that it is the nameserver for istest.com. I had since removed all the extra
> IP's I put onto the domain controllers in an effort to rectify the situation,
> but it still doesn't seemed to have done anything.
>
> If anyone has any insight that would be grand. I moved DNS servers from
> dnstestsrv to dnstestsrv2 in an effort to an issue I was having with
> some linux clients.
>
>

Read inline please.

In news:BF5E4C25-EDEC-4557-A439-649923D5BFA6@microsoft.com,
infinitiguy <infinitiguy@discussions.microsoft.com> typed:
> I messed up my DNS test environment somehow. What I had originally
> tried to do was multihome a DC running DNS to facilitate a migration,
> and as a result now when I do a lookup against anything I get this...
>
> C:\Documents and Settings\Administrator.ISTEST>nslookup pudge
> *** Can't find server name for address 10.65.2.37: Non-existent domain
> Server: UnKnown
> Address: 10.65.2.37
>
> Name: pudge.istest.com
> Address: 10.64.3.54
>
> pudge is a client(linux) that registered itself in DNS, however,
> 10.65.2.37 is my DNS server(named dnstestsrv2). This lookup was done
> from dnstestsrv2. Why is this happening? Why isn't the server known?
> In the DNS zone for istest.com I have NS records for
> dnstestsrv2.istest.com so it should know that it is the nameserver
> for istest.com. I had since removed all the extra IP's I put onto
> the domain controllers in an effort to rectify the situation, but it
> still doesn't seemed to have done anything.
>
> If anyone has any insight that would be grand. I moved DNS servers
> from dnstestsrv to dnstestsrv2 in an effort to an issue I was
> having with some linux clients.

This is just nslookup doing a reverse lookup on the DNS server's IP address,
and the PTR does not exist.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oe.com/OEBackup/Default.aspx
===================================

Good call. I understand now because the DNS server was registering its IP in
a subnet that was not under control by MS DNS or DHCP (still on our bind
server). I think I had it set up to work before and made so many changes
that I forgot how it was originally set. I uncomplicated matters for testing
and moved my DNS server to a local 10.64.3.x subnet and things work well
again.

One more quick followup about stubs. I think I understand how they work.
Stubs are basically an index for a changing DNS environment. So if I have my
clients all point to a stub at 10.65.6.2 and the stub knows that 10.65.6.3
and 10.65.6.4 are the DNS servers, all clients should be able to resolve fine
against them. If I then were to re-IP 10.65.6.3 and 10.65.6.4 to x.5 and x.6
the stub zone should realize this and the clients will still be able to do
DNS lookups without having to change anything.

Correct? Or am I misunderstanding something

"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Read inline please.
>
> In news:BF5E4C25-EDEC-4557-A439-649923D5BFA6@microsoft.com,
> infinitiguy <infinitiguy@discussions.microsoft.com> typed:
> > I messed up my DNS test environment somehow. What I had originally
> > tried to do was multihome a DC running DNS to facilitate a migration,
> > and as a result now when I do a lookup against anything I get this...
> >
> > C:\Documents and Settings\Administrator.ISTEST>nslookup pudge
> > *** Can't find server name for address 10.65.2.37: Non-existent domain
> > Server: UnKnown
> > Address: 10.65.2.37
> >
> > Name: pudge.istest.com
> > Address: 10.64.3.54
> >
> > pudge is a client(linux) that registered itself in DNS, however,
> > 10.65.2.37 is my DNS server(named dnstestsrv2). This lookup was done
> > from dnstestsrv2. Why is this happening? Why isn't the server known?
> > In the DNS zone for istest.com I have NS records for
> > dnstestsrv2.istest.com so it should know that it is the nameserver
> > for istest.com. I had since removed all the extra IP's I put onto
> > the domain controllers in an effort to rectify the situation, but it
> > still doesn't seemed to have done anything.
> >
> > If anyone has any insight that would be grand. I moved DNS servers
> > from dnstestsrv to dnstestsrv2 in an effort to an issue I was
> > having with some linux clients.
>
> This is just nslookup doing a reverse lookup on the DNS server's IP address,
> and the PTR does not exist.
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This s
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oe.com/OEBackup/Default.aspx
> ===================================
>
>
>

Read inline please.

In news:93A1EE23-A065-442E-A89A-E1B86AF4403A@microsoft.com,
infinitiguy <infinitiguy@discussions.microsoft.com> typed:
> Good call. I understand now because the DNS server was registering
> its IP in a subnet that was not under control by MS DNS or DHCP
> (still on our bind server). I think I had it set up to work before
> and made so many changes that I forgot how it was originally set. I
> uncomplicated matters for testing and moved my DNS server to a local
> 10.64.3.x subnet and things work well again.
>
> One more quick followup about stubs. I think I understand how they
> work. Stubs are basically an index for a changing DNS environment.
> So if I have my clients all point to a stub at 10.65.6.2 and the
> stub knows that 10.65.6.3 and 10.65.6.4 are the DNS servers, all
> clients should be able to resolve fine against them. If I then were
> to re-IP 10.65.6.3 and 10.65.6.4 to x.5 and x.6 the stub zone should
> realize this and the clients will still be able to do DNS lookups
> without having to change anything.
>
> Correct? Or am I misunderstanding something

That is pretty much just how Stub zones work, but if the IP changes on the
one Configured on the General tab, you'll need to fix it.



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oe.com/OEBackup/Default.aspx
===================================