Archived from groups: microsoft.public.win2000.dns (More info?)
I'm using IIS 5.0 on a W2k server with GFI spam filtering. Today I started
getting failed email messages. I tested my DNS MX configuration with NSLOOKUP
and noticed that NSLOOKUP is appending my domain name even when I enter a
FQDN of other domains while testing. It's as if
NSLOOKUP is treating all domains on the Internet as a host on my domain. EX:
If I type novell.com after setting querytype=MX it replies with
"novell.com.mydomain.com" . This points to me as handling email for
"novell.com" because it treats novell.com as a host on my domain.
Setting a different DNS name servers for the network card, external or
internal to my domain does not fix this problem. Reboots don't help either.
Enabling or disabling cache only DNS server on the machine makes no
difference. Nothing special is in the host file under etc. All other inquires
in NSLOOKUP work, ie PTR, A, etc.. Other PC on the network don't have this
problem. Scanned and found no viruses.
Is NSLOOKUP reflecting the problem correctly or is this not a good tool to
use. If NSLOOKUP is reporting the problem correctly do you have any idea
why my system is now appending my domain to all domains in NSLOOKUP and maybe
for mail delivery, thus the failures?
I'm using IIS 5.0 on a W2k server with GFI spam filtering. Today I started
getting failed email messages. I tested my DNS MX configuration with NSLOOKUP
and noticed that NSLOOKUP is appending my domain name even when I enter a
FQDN of other domains while testing. It's as if
NSLOOKUP is treating all domains on the Internet as a host on my domain. EX:
If I type novell.com after setting querytype=MX it replies with
"novell.com.mydomain.com" . This points to me as handling email for
"novell.com" because it treats novell.com as a host on my domain.
Setting a different DNS name servers for the network card, external or
internal to my domain does not fix this problem. Reboots don't help either.
Enabling or disabling cache only DNS server on the machine makes no
difference. Nothing special is in the host file under etc. All other inquires
in NSLOOKUP work, ie PTR, A, etc.. Other PC on the network don't have this
problem. Scanned and found no viruses.
Is NSLOOKUP reflecting the problem correctly or is this not a good tool to
use. If NSLOOKUP is reporting the problem correctly do you have any idea
why my system is now appending my domain to all domains in NSLOOKUP and maybe
for mail delivery, thus the failures?