Re: MX lookup results different depending on client application
- From: "Jeremy" <jeremy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Jun 2007 19:47:18 +1000
Well it looks to me like your system has correct DNS settings, but you really need to get the non-working system's ip configuration to diagnose this problem. I can't help much without it.
<zookster@xxxxxxxxx> wrote in message news:1181324918.592571.117320@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for the reply Jeremy.
The "non-working" server belongs to another company so I can't get the
information you requested from that machine.
The mail server shows these results...
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : mail
Primary Dns Suffix . . . . . . . : lehmans.lan
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lehmans.lan
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection #2
Physical Address. . . . . . . . . : 00-13-72-4F-BE-C0
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.1.7
192.168.0.2
192.168.1.5
C:\>nslookup
Default Server: sv02.lehmans.lan
Address: 192.168.1.7
set type=mxServer: sv02.lehmans.lan
humphreygasproducts.com
Address: 192.168.1.7
Non-authoritative answer:
humphreygasproducts.com MX preference = 10, mail exchanger =
mx.valueweb.com
mx.valueweb.com internet address = 216.219.253.196
Let me know if that helps or not.
djz
On Jun 7, 5:42 am, "Jeremy" <jer...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:This is the output from an nslookup for your MX record:
----
D:\downloads>nslookup
Default Server: dns1.tpgi.com.au
Address: 203.12.160.35:53
> set type=mx
> humphreygasproducts.com
Server: dns1.tpgi.com.au
Address: 203.12.160.35:53
Non-authoritative answer:
humphreygasproducts.com MX preference = 10, mail exchanger = mx.valueweb.com
humphreygasproducts.com nameserver = dns3.valueweb.com
humphreygasproducts.com nameserver = dns1.valueweb.com
humphreygasproducts.com nameserver = dns2.valueweb.com
mx.valueweb.com internet address = 216.219.253.196
-----
Can you please post the ipconfig /all output of both the non working server
and from the Exchange server and then the output of this nslookup query
above from both too.
Cheers,
Jeremy.<zooks...@xxxxxxxxx> wrote in message
news:1181069511.915087.37730@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> When our mail server performs an MX lookup on humphreygasproducts.com
> (which is done during the STMP conversation with their sending mail
> server when they send us a message) our internal Windows 2003 (5.2
> Build 3790.srv03_sp1_gdr.070304-2232) DNS server returns a "non-
> existant domain" reply. If I perform an nslookup on the mx record
> while at the console on the mail server, it returns the MX record just
> fine.
> I've tried flushing the DNS cache on the mail server, and clearing the
> cache in the DNS server. I've also checked the
> humphreygasproducts.com domain onwww.checkdns.net
> Any thoughts or help is greatly appreciated.
> Below is the debug log showing the mail server request and the DNS
> server negative reply.
> 20070605 11:42:15 E4C PACKET UDP Rcv 192.168.0.2 1dc3 Q [0001
> D NOERROR] (19)humphreygasproducts(3)com(0)
> UDP question info at 022B4F50
> Socket = 488
> Remote addr 192.168.0.2, port 2929
> Time Query=13868, Queued=0, Expire=0
> Buf length = 0x0500 (1280)
> Msg length = 0x0029 (41)
> Message:
> XID 0x1dc3
> Flags 0x0100
> QR 0 (QUESTION)
> OPCODE 0 (QUERY)
> AA 0
> TC 0
> RD 1
> RA 0
> Z 0
> RCODE 0 (NOERROR)
> QCOUNT 1
> ACOUNT 0
> NSCOUNT 0
> ARCOUNT 0
> QUESTION SECTION:
> Offset = 0x000c, RR count = 0
> Name "(19)humphreygasproducts(3)com(0)"
> QTYPE MX (15)
> QCLASS 1
> ANSWER SECTION:
> empty
> AUTHORITY SECTION:
> empty
> ADDITIONAL SECTION:
> empty
> 20070605 11:42:15 E4C PACKET UDP Snd 192.168.0.2 1dc3 R Q [8381
> DR NXDOMAIN] (19)humphreygasproducts(3)com(0)
> UDP response info at 022B4F50
> Socket = 488
> Remote addr 192.168.0.2, port 2929
> Time Query=13868, Queued=0, Expire=0
> Buf length = 0x0200 (512)
> Msg length = 0x0029 (41)
> Message:
> XID 0x1dc3
> Flags 0x8183
> QR 1 (RESPONSE)
> OPCODE 0 (QUERY)
> AA 0
> TC 0
> RD 1
> RA 1
> Z 0
> RCODE 3 (NXDOMAIN)
> QCOUNT 1
> ACOUNT 0
> NSCOUNT 0
> ARCOUNT 0
> QUESTION SECTION:
> Offset = 0x000c, RR count = 0
> Name "(19)humphreygasproducts(3)com(0)"
> QTYPE MX (15)
> QCLASS 1
> ANSWER SECTION:
> empty
> AUTHORITY SECTION:
> empty
> ADDITIONAL SECTION:
> empty
> ------------------
> Below is the nslookup request and reply.
> 20070605 11:45:47 E4C PACKET UDP Rcv 192.168.0.2 1e3d Q [0001
> D NOERROR] (19)humphreygasproducts(3)com(0)
> UDP question info at 023194E0
> Socket = 488
> Remote addr 192.168.0.2, port 3069
> Time Query=14080, Queued=0, Expire=0
> Buf length = 0x0500 (1280)
> Msg length = 0x0029 (41)
> Message:
> XID 0x1e3d
> Flags 0x0100
> QR 0 (QUESTION)
> OPCODE 0 (QUERY)
> AA 0
> TC 0
> RD 1
> RA 0
> Z 0
> RCODE 0 (NOERROR)
> QCOUNT 1
> ACOUNT 0
> NSCOUNT 0
> ARCOUNT 0
> QUESTION SECTION:
> Offset = 0x000c, RR count = 0
> Name "(19)humphreygasproducts(3)com(0)"
> QTYPE MX (15)
> QCLASS 1
> ANSWER SECTION:
> empty
> AUTHORITY SECTION:
> empty
> ADDITIONAL SECTION:
> empty
> 20070605 11:45:47 E4C PACKET UDP Snd 192.168.0.2 1e3d R Q [8081
> DR NOERROR] (19)humphreygasproducts(3)com(0)
> UDP response info at 023194E0
> Socket = 488
> Remote addr 192.168.0.2, port 3069
> Time Query=14080, Queued=0, Expire=0
> Buf length = 0x0200 (512)
> Msg length = 0x0055 (85)
> Message:
> XID 0x1e3d
> Flags 0x8180
> QR 1 (RESPONSE)
> OPCODE 0 (QUERY)
> AA 0
> TC 0
> RD 1
> RA 1
> Z 0
> RCODE 0 (NOERROR)
> QCOUNT 1
> ACOUNT 1
> NSCOUNT 0
> ARCOUNT 1
> QUESTION SECTION:
> Offset = 0x000c, RR count = 0
> Name "(19)humphreygasproducts(3)com(0)"
> QTYPE MX (15)
> QCLASS 1
> ANSWER SECTION:
> Offset = 0x0029, RR count = 0
> Name "[C00C](19)humphreygasproducts(3)com(0)"
> TYPE MX (15)
> CLASS 1
> TTL 3567
> DLEN 16
> DATA 10 (2)mx(8)valueweb[C020](3)com(0)
> AUTHORITY SECTION:
> empty
> ADDITIONAL SECTION:
> Offset = 0x0045, RR count = 0
> Name "[C037](2)mx(8)valueweb[C020](3)com(0)"
> TYPE A (1)
> CLASS 1
> TTL 267
> DLEN 4
> DATA 216.219.253.196
.
- Follow-Ups:
- References:
- Prev by Date: RE: Looking for info about scavenging Server 2003
- Next by Date: Re: Looking for info about scavenging Server 2003
- Previous by thread: Re: MX lookup results different depending on client application
- Next by thread: Re: MX lookup results different depending on client application
- Index(es):
Relevant Pages
|
Loading