smtp event log error
in [IIS]
|
Prev: Problems loading an Excel File
Next: iisadmin.mfl
From: Sparky Polastri on 3 Mar 2005 14:16 Well the first step is to know what DNS should be for that domain. i.e. www goes to what IP, MX goes to what hostname and then to what IP. Then use ping to find out what the DNS resolution on that box is (by logging onto it, using ping with the hostname) and compare that with what your network actually is. Chances are a) your DNS resolution system is not working (thus "Internal DNS error") or b) DNS is cached locally and reporting the wrong IP for that mail server or c) dns for that domain actually is messed up. Logging onto the box can get you a) and b). c) can be done using any number of tools on the web. Also in general, DNS is forced to refresh if you reboot devices (including the router). Whether or not you should do that depends on your use of the machines. If you can't reboot, stop and restart the DNS client service on the computer to make sure it is not "remembering" the wrong IP addresses. "Roy" <rdeal(a)newsgroup.nospam> wrote in message news:8509B4B4-0630-4164-98D3-1BD9692E30E5(a)microsoft.com... > Thanks for the pointers, Jeff and Sparky. Since the event log error > mentions > an internal DNS error, it seems like I should use nslookup to troubleshoot > my > router's DNS server. Is that correct? If so, then what queries do I > issue? > > I see from http://support.microsoft.com/kb/200525 examples for querying my > ISP's incoming/outgoing email hosts (mail.comcast.net/smtp.comcast.net), > but > how do I query MY machine to make sure it's getting proper DNS? > > "Jeff Cochran" wrote: > >> On Thu, 3 Mar 2005 06:27:04 -0800, Roy <rdeal(a)newsgroup.nospam> wrote: >> >> >I am not very networking savvy, so what you mean by do some DNS queries? >> >I >> >did do a few things with nslookup - I that's along the lines of what you >> >recommended - that I read in a kbase article or two, but interpreting >> >the >> >output is not my strong suit. >> >> Post the output in the DNS groups and you'll get a decent tutorial in >> how to read them. >> >> Jeff >> >> >Thanks for the advice. >> > >> >"Sparky Polastri" wrote: >> > >> >> Log onto the box and do some DNS queries to make sure the box is >> >> getting >> >> proper DNS. >> >> >> >> Changing network stuff around could very well cause ripple-effect type >> >> errors in DNS. >> >> >> >> "Roy" <rdeal(a)newsgroup.nospam> wrote in message >> >> news:C3371806-8B84-4F43-8321-EAFD4875F417(a)microsoft.com... >> >> >I have a program that I wrote which sends text messages to my cell >> >> >phone. >> >> > The program uses IMessage from cdosys. It has been working fine for >> >> > about >> >> > a >> >> > year, but about a week ago, errors like the following started >> >> > showing up >> >> > in >> >> > the nt event log: >> >> > >> >> > source: smtpsvc >> >> > event id: 4000 >> >> > description: Message delivery to the remote domain 'vtext.com' >> >> > failed for >> >> > the following reason: An internal DNS error caused a failure to find >> >> > the >> >> > remote server. >> >> > >> >> > The only thing I can think of that I did around that time was put my >> >> > Windows >> >> > 2000 box into a new workgroup while trying to set up peer-to-peer >> >> > networking >> >> > between 2 machines at my house. I haven't changed any settings on >> >> > my >> >> > router. >> >> > I tried putting the computer back in the WORKGROUP workgroup, but >> >> > that >> >> > didn't fix the problem. >> >> > >> >> > I did run the smtpdiag utility, but I'm unsure of how to interpret >> >> > the >> >> > output. The output is included below. Any ideas what might be >> >> > going on? >> >> > >> >> > Thanks, >> >> > Roy >> >> > >> >> > Searching for Exchange external DNS settings. >> >> > Computer name is THEBOX. >> >> > Failed to connect to the domain controller. Error: >> >> > 8007054b >> >> > >> >> > Checking SOA for vtext.com. >> >> > Checking external DNS servers. >> >> > Checking internal DNS servers. >> >> > >> >> > Checking TCP/UDP SOA serial number using DNS server >> >> > [192.168.2.1]. >> >> > Failed: DNS server [192.168.2.1] may be down. >> >> > DNS server [192.168.2.1] did not return a valid SOA >> >> > record. >> >> > SOA serial number match: Failed with one or more >> >> > failures. >> >> > >> >> > Checking local domain records. >> >> > Starting TCP and UDP DNS queries for the local domain. >> >> > This test will try to >> >> > validate that DNS is set up correctly for inbound >> >> > mail. This test can fail for >> >> > 3 reasons. >> >> > 1) Local domain is not set up in DNS. Inbound mail >> >> > cannot be routed to >> >> > local mailboxes. >> >> > 2) Firewall blocks TCP/UDP DNS queries. This will >> >> > not affect inbound mail, >> >> > but will affect outbound mail. >> >> > 3) Internal DNS is unaware of external DNS >> >> > settings. This is a valid >> >> > configuration for certain topologies. >> >> > Checking MX records using TCP: comcast.net. >> >> > Warning: The TCP DNS query returned no results. >> >> > Checking MX records using UDP: comcast.net. >> >> > MX: gateway-s.comcast.net (5) >> >> > MX: gateway-r.comcast.net (5) >> >> > A: gateway-s.comcast.net [IP address - looks valid] >> >> > A: gateway-s.comcast.net [IP address - looks valid] >> >> > A: gateway-r.comcast.net [IP address - looks valid] >> >> > A: gateway-r.comcast.net [IP address - looks valid] >> >> > A: dns01.jdc01.pa.comcast.net [IP address - looks valid] >> >> > A: dns02.jdc01.pa.comcast.net [IP address - looks valid] >> >> > >> >> > Checking remote domain records. >> >> > Starting TCP and UDP DNS queries for the remote >> >> > domain. This test will try to >> >> > validate that DNS is set up correctly for outbound >> >> > mail. This test can fail for >> >> > 3 reasons. >> >> > 1) Firewall blocks TCP/UDP queries which will >> >> > block outbound mail. Windows >> >> > 2000/NT Server requires TCP DNS queries. Windows >> >> > Server 2003 will use UDP >> >> > queries first, then fall back to TCP queries. >> >> > 2) Internal DNS does not know how to query >> >> > external domains. You must >> >> > either use an external DNS server or configure DNS >> >> > server to query external >> >> > domains. >> >> > 3) Remote domain does not exist. Failure is >> >> > expected. >> >> > Checking MX records using TCP: vtext.com. >> >> > Warning: The TCP DNS query returned no results. >> >> > Checking MX records using UDP: vtext.com. >> >> > MX: smtpsp.vtext.com (50) >> >> > MX: smtpsp1.vtext.com (50) >> >> > A: smtpsp.vtext.com [IP address - looks valid] >> >> > A: smtpsp1.vtext.com [IP address - looks valid] >> >> >> >> >> >> >> >>
From: Roy on 3 Mar 2005 15:15 I'll have to confirm this, but I believe I can logon to the machine with the event log errors and ping it by name, and the IP address returned by ping is the same as it has always been 192.168.2.3. That is within the range that has been set up in my router. If I do an ipconfig /all, then the DNS IP is 192.168.2.1, which is correct. I'll try your suggestions tonight. You know, I remember one other thing I did to the network settings on the 2nd machine in my home network. I disabled the Computer Browser service on it so it would not be the master browser. Could that have anything to do with this? "Sparky Polastri" wrote: > Well the first step is to know what DNS should be for that domain. i.e. www > goes to what IP, MX goes to what hostname and then to what IP. > > Then use ping to find out what the DNS resolution on that box is (by logging > onto it, using ping with the hostname) and compare that with what your > network actually is. > > Chances are a) your DNS resolution system is not working (thus "Internal DNS > error") or b) DNS is cached locally and reporting the wrong IP for that mail > server or c) dns for that domain actually is messed up. > > Logging onto the box can get you a) and b). c) can be done using any number > of tools on the web. > > Also in general, DNS is forced to refresh if you reboot devices (including > the router). Whether or not you should do that depends on your use of the > machines. If you can't reboot, stop and restart the DNS client service on > the computer to make sure it is not "remembering" the wrong IP addresses. > > "Roy" <rdeal(a)newsgroup.nospam> wrote in message > news:8509B4B4-0630-4164-98D3-1BD9692E30E5(a)microsoft.com... > > Thanks for the pointers, Jeff and Sparky. Since the event log error > > mentions > > an internal DNS error, it seems like I should use nslookup to troubleshoot > > my > > router's DNS server. Is that correct? If so, then what queries do I > > issue? > > > > I see from http://support.microsoft.com/kb/200525 examples for querying my > > ISP's incoming/outgoing email hosts (mail.comcast.net/smtp.comcast.net), > > but > > how do I query MY machine to make sure it's getting proper DNS? > > > > "Jeff Cochran" wrote: > > > >> On Thu, 3 Mar 2005 06:27:04 -0800, Roy <rdeal(a)newsgroup.nospam> wrote: > >> > >> >I am not very networking savvy, so what you mean by do some DNS queries? > >> >I > >> >did do a few things with nslookup - I that's along the lines of what you > >> >recommended - that I read in a kbase article or two, but interpreting > >> >the > >> >output is not my strong suit. > >> > >> Post the output in the DNS groups and you'll get a decent tutorial in > >> how to read them. > >> > >> Jeff > >> > >> >Thanks for the advice. > >> > > >> >"Sparky Polastri" wrote: > >> > > >> >> Log onto the box and do some DNS queries to make sure the box is > >> >> getting > >> >> proper DNS. > >> >> > >> >> Changing network stuff around could very well cause ripple-effect type > >> >> errors in DNS. > >> >> > >> >> "Roy" <rdeal(a)newsgroup.nospam> wrote in message > >> >> news:C3371806-8B84-4F43-8321-EAFD4875F417(a)microsoft.com... > >> >> >I have a program that I wrote which sends text messages to my cell > >> >> >phone. > >> >> > The program uses IMessage from cdosys. It has been working fine for > >> >> > about > >> >> > a > >> >> > year, but about a week ago, errors like the following started > >> >> > showing up > >> >> > in > >> >> > the nt event log: > >> >> > > >> >> > source: smtpsvc > >> >> > event id: 4000 > >> >> > description: Message delivery to the remote domain 'vtext.com' > >> >> > failed for > >> >> > the following reason: An internal DNS error caused a failure to find > >> >> > the > >> >> > remote server. > >> >> > > >> >> > The only thing I can think of that I did around that time was put my > >> >> > Windows > >> >> > 2000 box into a new workgroup while trying to set up peer-to-peer > >> >> > networking > >> >> > between 2 machines at my house. I haven't changed any settings on > >> >> > my > >> >> > router. > >> >> > I tried putting the computer back in the WORKGROUP workgroup, but > >> >> > that > >> >> > didn't fix the problem. > >> >> > > >> >> > I did run the smtpdiag utility, but I'm unsure of how to interpret > >> >> > the > >> >> > output. The output is included below. Any ideas what might be > >> >> > going on? > >> >> > > >> >> > Thanks, > >> >> > Roy > >> >> > > >> >> > Searching for Exchange external DNS settings. > >> >> > Computer name is THEBOX. > >> >> > Failed to connect to the domain controller. Error: > >> >> > 8007054b > >> >> > > >> >> > Checking SOA for vtext.com. > >> >> > Checking external DNS servers. > >> >> > Checking internal DNS servers. > >> >> > > >> >> > Checking TCP/UDP SOA serial number using DNS server > >> >> > [192.168.2.1]. > >> >> > Failed: DNS server [192.168.2.1] may be down. > >> >> > DNS server [192.168.2.1] did not return a valid SOA > >> >> > record. > >> >> > SOA serial number match: Failed with one or more > >> >> > failures. > >> >> > > >> >> > Checking local domain records. > >> >> > Starting TCP and UDP DNS queries for the local domain. > >> >> > This test will try to > >> >> > validate that DNS is set up correctly for inbound > >> >> > mail. This test can fail for > >> >> > 3 reasons. > >> >> > 1) Local domain is not set up in DNS. Inbound mail > >> >> > cannot be routed to > >> >> > local mailboxes. > >> >> > 2) Firewall blocks TCP/UDP DNS queries. This will > >> >> > not affect inbound mail, > >> >> > but will affect outbound mail. > >> >> > 3) Internal DNS is unaware of external DNS > >> >> > settings. This is a valid > >> >> > configuration for certain topologies. > >> >> > Checking MX records using TCP: comcast.net. > >> >> > Warning: The TCP DNS query returned no results. > >> >> > Checking MX records using UDP: comcast.net. > >> >> > MX: gateway-s.comcast.net (5) > >> >> > MX: gateway-r.comcast.net (5) > >> >> > A: gateway-s.comcast.net [IP address - looks valid] > >> >> > A: gateway-s.comcast.net [IP address - looks valid] > >> >> > A: gateway-r.comcast.net [IP address - looks valid] > >> >> > A: gateway-r.comcast.net [IP address - looks valid] > >> >> > A: dns01.jdc01.pa.comcast.net [IP address - looks valid] > >> >> > A: dns02.jdc01.pa.comcast.net [IP address - looks valid] > >> >> > > >> >> > Checking remote domain records. > >> >> > Starting TCP and UDP DNS queries for the remote > >> >> > domain. This test will try to > >> >> > validate that DNS is set up correctly for outbound > >> >> > mail. This test can fail for > >> >> > 3 reasons. > >> >> > 1) Firewall blocks TCP/UDP queries which will > >> >> > block outbound mail. Windows > >> >> > 2000/NT Server requires TCP DNS queries. Windows > >> >> > Server 2003 will use UDP > >> >> > queries first, then fall back to TCP queries. > >> >> > 2) Internal DNS does not know how to query > >> >> > external domains. You must > >> >> > either use an external DNS server or configure DNS > >> >> > server to query external > >> >> > domains. > >> >> > 3) Remote domain does not exist. Failure is > >> >> > expected. > >> >> > Checking MX records using TCP: vtext.com. > >> >> > Warning: The TCP DNS query returned no results. > >> >> > Checking MX records using UDP: vtext.com. > >> >> > MX: smtpsp.vtext.com (50) > >> >> > MX: smtpsp1.vtext.com (50) > >> >> > A: smtpsp.vtext.com [IP address - looks valid] > >> >> > A: smtpsp1.vtext.com [IP address - looks valid] > >> >> > >> >> > >> >> > >> > >> > > >
From: Jeff Cochran on 3 Mar 2005 15:46 On Thu, 3 Mar 2005 12:15:11 -0800, Roy <rdeal(a)newsgroup.nospam> wrote: >I'll have to confirm this, but I believe I can logon to the machine with the >event log errors and ping it by name, and the IP address returned by ping is >the same as it has always been 192.168.2.3. That is within the range that >has been set up in my router. > >If I do an ipconfig /all, then the DNS IP is 192.168.2.1, which is correct. > >I'll try your suggestions tonight. > >You know, I remember one other thing I did to the network settings on the >2nd machine in my home network. I disabled the Computer Browser service on >it so it would not be the master browser. Could that have anything to do >with this? Not likely. That might affect NetBIOS name issues, but not DNS. Have you simply retried the message? Some of these errors can be from temporary network glitches too. Jeff >"Sparky Polastri" wrote: > >> Well the first step is to know what DNS should be for that domain. i.e. www >> goes to what IP, MX goes to what hostname and then to what IP. >> >> Then use ping to find out what the DNS resolution on that box is (by logging >> onto it, using ping with the hostname) and compare that with what your >> network actually is. >> >> Chances are a) your DNS resolution system is not working (thus "Internal DNS >> error") or b) DNS is cached locally and reporting the wrong IP for that mail >> server or c) dns for that domain actually is messed up. >> >> Logging onto the box can get you a) and b). c) can be done using any number >> of tools on the web. >> >> Also in general, DNS is forced to refresh if you reboot devices (including >> the router). Whether or not you should do that depends on your use of the >> machines. If you can't reboot, stop and restart the DNS client service on >> the computer to make sure it is not "remembering" the wrong IP addresses. >> >> "Roy" <rdeal(a)newsgroup.nospam> wrote in message >> news:8509B4B4-0630-4164-98D3-1BD9692E30E5(a)microsoft.com... >> > Thanks for the pointers, Jeff and Sparky. Since the event log error >> > mentions >> > an internal DNS error, it seems like I should use nslookup to troubleshoot >> > my >> > router's DNS server. Is that correct? If so, then what queries do I >> > issue? >> > >> > I see from http://support.microsoft.com/kb/200525 examples for querying my >> > ISP's incoming/outgoing email hosts (mail.comcast.net/smtp.comcast.net), >> > but >> > how do I query MY machine to make sure it's getting proper DNS? >> > >> > "Jeff Cochran" wrote: >> > >> >> On Thu, 3 Mar 2005 06:27:04 -0800, Roy <rdeal(a)newsgroup.nospam> wrote: >> >> >> >> >I am not very networking savvy, so what you mean by do some DNS queries? >> >> >I >> >> >did do a few things with nslookup - I that's along the lines of what you >> >> >recommended - that I read in a kbase article or two, but interpreting >> >> >the >> >> >output is not my strong suit. >> >> >> >> Post the output in the DNS groups and you'll get a decent tutorial in >> >> how to read them. >> >> >> >> Jeff >> >> >> >> >Thanks for the advice. >> >> > >> >> >"Sparky Polastri" wrote: >> >> > >> >> >> Log onto the box and do some DNS queries to make sure the box is >> >> >> getting >> >> >> proper DNS. >> >> >> >> >> >> Changing network stuff around could very well cause ripple-effect type >> >> >> errors in DNS. >> >> >> >> >> >> "Roy" <rdeal(a)newsgroup.nospam> wrote in message >> >> >> news:C3371806-8B84-4F43-8321-EAFD4875F417(a)microsoft.com... >> >> >> >I have a program that I wrote which sends text messages to my cell >> >> >> >phone. >> >> >> > The program uses IMessage from cdosys. It has been working fine for >> >> >> > about >> >> >> > a >> >> >> > year, but about a week ago, errors like the following started >> >> >> > showing up >> >> >> > in >> >> >> > the nt event log: >> >> >> > >> >> >> > source: smtpsvc >> >> >> > event id: 4000 >> >> >> > description: Message delivery to the remote domain 'vtext.com' >> >> >> > failed for >> >> >> > the following reason: An internal DNS error caused a failure to find >> >> >> > the >> >> >> > remote server. >> >> >> > >> >> >> > The only thing I can think of that I did around that time was put my >> >> >> > Windows >> >> >> > 2000 box into a new workgroup while trying to set up peer-to-peer >> >> >> > networking >> >> >> > between 2 machines at my house. I haven't changed any settings on >> >> >> > my >> >> >> > router. >> >> >> > I tried putting the computer back in the WORKGROUP workgroup, but >> >> >> > that >> >> >> > didn't fix the problem. >> >> >> > >> >> >> > I did run the smtpdiag utility, but I'm unsure of how to interpret >> >> >> > the >> >> >> > output. The output is included below. Any ideas what might be >> >> >> > going on? >> >> >> > >> >> >> > Thanks, >> >> >> > Roy >> >> >> > >> >> >> > Searching for Exchange external DNS settings. >> >> >> > Computer name is THEBOX. >> >> >> > Failed to connect to the domain controller. Error: >> >> >> > 8007054b >> >> >> > >> >> >> > Checking SOA for vtext.com. >> >> >> > Checking external DNS servers. >> >> >> > Checking internal DNS servers. >> >> >> > >> >> >> > Checking TCP/UDP SOA serial number using DNS server >> >> >> > [192.168.2.1]. >> >> >> > Failed: DNS server [192.168.2.1] may be down. >> >> >> > DNS server [192.168.2.1] did not return a valid SOA >> >> >> > record. >> >> >> > SOA serial number match: Failed with one or more >> >> >> > failures. >> >> >> > >> >> >> > Checking local domain records. >> >> >> > Starting TCP and UDP DNS queries for the local domain. >> >> >> > This test will try to >> >> >> > validate that DNS is set up correctly for inbound >> >> >> > mail. This test can fail for >> >> >> > 3 reasons. >> >> >> > 1) Local domain is not set up in DNS. Inbound mail >> >> >> > cannot be routed to >> >> >> > local mailboxes. >> >> >> > 2) Firewall blocks TCP/UDP DNS queries. This will >> >> >> > not affect inbound mail, >> >> >> > but will affect outbound mail. >> >> >> > 3) Internal DNS is unaware of external DNS >> >> >> > settings. This is a valid >> >> >> > configuration for certain topologies. >> >> >> > Checking MX records using TCP: comcast.net. >> >> >> > Warning: The TCP DNS query returned no results. >> >> >> > Checking MX records using UDP: comcast.net. >> >> >> > MX: gateway-s.comcast.net (5) >> >> >> > MX: gateway-r.comcast.net (5) >> >> >> > A: gateway-s.comcast.net [IP address - looks valid] >> >> >> > A: gateway-s.comcast.net [IP address - looks valid] >> >> >> > A: gateway-r.comcast.net [IP address - looks valid] >> >> >> > A: gateway-r.comcast.net [IP address - looks valid] >> >> >> > A: dns01.jdc01.pa.comcast.net [IP address - looks valid] >> >> >> > A: dns02.jdc01.pa.comcast.net [IP address - looks valid] >> >> >> > >> >> >> > Checking remote domain records. >> >> >> > Starting TCP and UDP DNS queries for the remote >> >> >> > domain. This test will try to >> >> >> > validate that DNS is set up correctly for outbound >> >> >> > mail. This test can fail for >> >> >> > 3 reasons. >> >> >> > 1) Firewall blocks TCP/UDP queries which will >> >> >> > block outbound mail. Windows >> >> >> > 2000/NT Server requires TCP DNS queries. Windows >> >> >> > Server 2003 will use UDP >> >> >> > queries first, then fall back to TCP queries. >> >> >> > 2) Internal DNS does not know how to query >> >> >> > external domains. You must >> >> >> > either use an external DNS server or configure DNS >> >> >> > server to query external >> >> >> > domains. >> >> >> > 3) Remote domain does not exist. Failure is >> >> >> > expected. >> >> >> > Checking MX records using TCP: vtext.com. >> >> >> > Warning: The TCP DNS query returned no results. >> >> >> > Checking MX records using UDP: vtext.com. >> >> >> > MX: smtpsp.vtext.com (50) >> >> >> > MX: smtpsp1.vtext.com (50) >> >> >> > A: smtpsp.vtext.com [IP address - looks valid] >> >> >> > A: smtpsp1.vtext.com [IP address - looks valid] >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >>
From: Roy on 3 Mar 2005 16:01 I haven't retried any of the messages, I do believe that the smtp service is configured to try sending the message more than once. IMessage::Send returns S_OK as if everything is fine, so there is no indication that the send has failed. However, there were several entries in inetpub\mailroot\badmail and inetpub\mailroot\queue. The number of files just keeps growing with each new Send call.
From: Roy on 3 Mar 2005 21:41
OK, I ran nslookup on the domains involved. I've been attempting to send an email FROM a comcast.net address TO a vtext.com address and TO a yahoo.com address. Below are DNS queries for yahoo.com, vtext.com, smtp.comcast.net (outgoing mail server), mail.comcast.net (incoming mail server), and comcast.net. C:\Documents and Settings\Administrator>nslookup *** Can't find server name for address 192.168.2.1: Non-existent domain *** Default servers are not available Default Server: UnKnown Address: 192.168.2.1 > set q=mx > > > yahoo.com Server: UnKnown Address: 192.168.2.1 Non-authoritative answer: yahoo.com MX preference = 1, mail exchanger = mx2.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = mx3.mail.yahoo.com yahoo.com MX preference = 5, mail exchanger = mx4.mail.yahoo.com yahoo.com MX preference = 1, mail exchanger = mx1.mail.yahoo.com yahoo.com nameserver = ns1.yahoo.com yahoo.com nameserver = ns2.yahoo.com yahoo.com nameserver = ns3.yahoo.com yahoo.com nameserver = ns4.yahoo.com yahoo.com nameserver = ns5.yahoo.com mx2.mail.yahoo.com internet address = 64.156.215.8 mx2.mail.yahoo.com internet address = 67.28.114.35 mx2.mail.yahoo.com internet address = 67.28.114.36 mx4.mail.yahoo.com internet address = 68.142.202.113 mx4.mail.yahoo.com internet address = 68.142.202.112 mx1.mail.yahoo.com internet address = 64.157.4.78 mx1.mail.yahoo.com internet address = 67.28.113.10 mx1.mail.yahoo.com internet address = 67.28.113.11 ns1.yahoo.com internet address = 66.218.71.63 ns2.yahoo.com internet address = 66.163.169.170 ns3.yahoo.com internet address = 217.12.4.104 ns4.yahoo.com internet address = 63.250.206.138 ns5.yahoo.com internet address = 216.109.116.17 > > > vtext.com Server: UnKnown Address: 192.168.2.1 vtext.com MX preference = 50, mail exchanger = smtpsp1.vtext.com vtext.com MX preference = 50, mail exchanger = smtpsp.vtext.com vtext.com nameserver = njbdns1.vtext.com vtext.com nameserver = njbdns2.vtext.com vtext.com nameserver = cawcns1.vtext.com vtext.com nameserver = cawcns2.vtext.com smtpsp.vtext.com internet address = 66.174.76.30 smtpsp1.vtext.com internet address = 66.174.3.30 cawcns1.vtext.com internet address = 66.174.6.71 cawcns2.vtext.com internet address = 66.174.6.72 njbdns1.vtext.com internet address = 66.174.3.71 njbdns2.vtext.com internet address = 66.174.3.72 > > > > smtp.comcast.net Server: UnKnown Address: 192.168.2.1 comcast.net primary name server = dns01.jdc01.pa.comcast.net responsible mail addr = dnsadmin.comcast.net serial = 1082 refresh = 900 (15 mins) retry = 180 (3 mins) expire = 604800 (7 days) default TTL = 3600 (1 hour) > > > mail.comcast.net Server: UnKnown Address: 192.168.2.1 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to UnKnown timed-out > > > > comcast.net Server: UnKnown Address: 192.168.2.1 Non-authoritative answer: comcast.net MX preference = 5, mail exchanger = gateway-r.comcast.net comcast.net MX preference = 5, mail exchanger = gateway-s.comcast.net comcast.net nameserver = dns01.jdc01.pa.comcast.net comcast.net nameserver = dns02.jdc01.pa.comcast.net gateway-r.comcast.net internet address = 216.148.227.126 gateway-r.comcast.net internet address = 204.127.198.26 gateway-s.comcast.net internet address = 63.240.76.26 gateway-s.comcast.net internet address = 204.127.202.26 dns01.jdc01.pa.comcast.net internet address = 68.87.96.3 dns02.jdc01.pa.comcast.net internet address = 68.87.96.4 > |