Re: nslookup strange return
- From: "Kevin D. Goodknecht Sr. [MVP]" <admin@xxxxxxxxxxxxxx>
- Date: Mon, 8 May 2006 14:44:09 -0500
NormD wrote:
There is much I'm not following about this; my fault, not yours,
Kevin! Thank you for your patience.
Windows IP Configuration
Host Name . . . . . . . . . . . . : kai130
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce MCP
Networking Controller
Physical Address. . . . . . . . . : 00-50-8D-62-73-4C
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.130
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.248
DNS Servers . . . . . . . . . . . : 151.197.0.39
151.198.0.39
From the problem server:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : kamail
Primary DNS Suffix . . . . . . . : com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI NIC
(3C905-TX)
Physical Address. . . . . . . . . : 00-10-4B-32-B6-A8
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.8
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.248
DNS Servers . . . . . . . . . . . : 151.197.0.39
151.198.0.39
Where the "Primary DNS Suffix . . . . . . . : com" comes from beats
me, but it sure looks like what's getting tacked onto the end of the
nslookup line!
Any suggestions before I start in with the crowbar and chain saw?!
This is an Exchange server isn't it?
Exchange requires Active Directory, which requires its own DNS resolution.
Is it also the domain controller?
Is DNS installed on the Domain Controller?
What is the AD domain name?
The Primary DNS suffix may be incorrect, but it should match the AD domain
name, if the AD domain name is com it is a single label domain name which is
big problems for Active Directory.
All AD domain Member MUST use ONLY DNS servers that support the AD domain,
these appear to be your ISP's DNS which is highly unlike to support your AD
Domain.
Getting close, please reply with the answers from the questions above and it
should be cleared up after my next reply.
--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
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/
https://secure.lsaol.com/
===================================
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.oehelp.com/OEBackup/Default.aspx
===================================
.
- Follow-Ups:
- Re: nslookup strange return
- From: NormD
- Re: nslookup strange return
- References:
- Re: nslookup strange return
- From: Ace Fekay [MVP]
- Re: nslookup strange return
- From: Kevin D. Goodknecht Sr. [MVP]
- Re: nslookup strange return
- From: Kevin D. Goodknecht Sr. [MVP]
- Re: nslookup strange return
- From: NormD
- Re: nslookup strange return
- Prev by Date: Re: Reverse DNS problem
- Next by Date: Re: Reverse DNS problem
- Previous by thread: Re: nslookup strange return
- Next by thread: Re: nslookup strange return
- Index(es):
Relevant Pages
|