Can't resolve a domain in Ubuntu, but can in Windows?
up vote
1
down vote
favorite
A couple of days ago, I stopped being able to download my email from comcast via pop3. Every time I ask Thunderbird to get my mail, it says "Failed to connect to mail.comcast.net". Thing is, I can send mail just fine. So I thought to myself, why not just try to ping the servers. This is what I get:
procyon@MSI-GS60-6QE:~$ ping mail.comcast.net
ping: mail.comcast.net: Name or service not known
procyon@MSI-GS60-6QE:~$ ping smtp.comcast.net
PING smtp.g.comcast.net (96.114.157.81) 56(84) bytes of data.
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=1 ttl=51 time=60.7 ms
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=2 ttl=51 time=69.7 ms
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=3 ttl=51 time=67.2 ms
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=4 ttl=51 time=59.7 ms
However, I happen to dual boot this laptop, so I switched over to Windows 10 to try pinging mail.comcast.net from there. Lo and behold:
C:UsersScott>ping mail.comcast.net
Pinging imap.ge.xfinity.com [96.117.3.96] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
So it's obviously not set up to respond to ping, but the domain DID get resolved (to something else) or so it seems. I don't know how to begin to debug this sort of problem. Does anyone out there have any ideas? Comcast's customer support was useless, as expected. Thank you.
dns email smtp imap
edited Nov 22 at 12:11
LeonidMew
385215
asked Nov 22 at 4:26
Scott Jacobi
215
add a comment |
up vote
1
down vote
favorite
A couple of days ago, I stopped being able to download my email from comcast via pop3. Every time I ask Thunderbird to get my mail, it says "Failed to connect to mail.comcast.net". Thing is, I can send mail just fine. So I thought to myself, why not just try to ping the servers. This is what I get:
procyon@MSI-GS60-6QE:~$ ping mail.comcast.net
ping: mail.comcast.net: Name or service not known
procyon@MSI-GS60-6QE:~$ ping smtp.comcast.net
PING smtp.g.comcast.net (96.114.157.81) 56(84) bytes of data.
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=1 ttl=51 time=60.7 ms
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=2 ttl=51 time=69.7 ms
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=3 ttl=51 time=67.2 ms
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=4 ttl=51 time=59.7 ms
However, I happen to dual boot this laptop, so I switched over to Windows 10 to try pinging mail.comcast.net from there. Lo and behold:
C:UsersScott>ping mail.comcast.net
Pinging imap.ge.xfinity.com [96.117.3.96] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
So it's obviously not set up to respond to ping, but the domain DID get resolved (to something else) or so it seems. I don't know how to begin to debug this sort of problem. Does anyone out there have any ideas? Comcast's customer support was useless, as expected. Thank you.
dns email smtp imap
edited Nov 22 at 12:11
LeonidMew
385215
asked Nov 22 at 4:26
Scott Jacobi
215
Runnslookup mail.comcast.netin both Windows and in Ubuntu and see if theServer:andAddress:line right after the command is the same in both.
– Terrance
Nov 22 at 5:12
Here is how Comcast says to configure thunderbird: link
– TonyB
Nov 22 at 6:21
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
A couple of days ago, I stopped being able to download my email from comcast via pop3. Every time I ask Thunderbird to get my mail, it says "Failed to connect to mail.comcast.net". Thing is, I can send mail just fine. So I thought to myself, why not just try to ping the servers. This is what I get:
procyon@MSI-GS60-6QE:~$ ping mail.comcast.net
ping: mail.comcast.net: Name or service not known
procyon@MSI-GS60-6QE:~$ ping smtp.comcast.net
PING smtp.g.comcast.net (96.114.157.81) 56(84) bytes of data.
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=1 ttl=51 time=60.7 ms
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=2 ttl=51 time=69.7 ms
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=3 ttl=51 time=67.2 ms
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=4 ttl=51 time=59.7 ms
However, I happen to dual boot this laptop, so I switched over to Windows 10 to try pinging mail.comcast.net from there. Lo and behold:
C:UsersScott>ping mail.comcast.net
Pinging imap.ge.xfinity.com [96.117.3.96] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
So it's obviously not set up to respond to ping, but the domain DID get resolved (to something else) or so it seems. I don't know how to begin to debug this sort of problem. Does anyone out there have any ideas? Comcast's customer support was useless, as expected. Thank you.
dns email smtp imap
edited Nov 22 at 12:11
LeonidMew
385215
asked Nov 22 at 4:26
Scott Jacobi
215
A couple of days ago, I stopped being able to download my email from comcast via pop3. Every time I ask Thunderbird to get my mail, it says "Failed to connect to mail.comcast.net". Thing is, I can send mail just fine. So I thought to myself, why not just try to ping the servers. This is what I get:
procyon@MSI-GS60-6QE:~$ ping mail.comcast.net
ping: mail.comcast.net: Name or service not known
procyon@MSI-GS60-6QE:~$ ping smtp.comcast.net
PING smtp.g.comcast.net (96.114.157.81) 56(84) bytes of data.
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=1 ttl=51 time=60.7 ms
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=2 ttl=51 time=69.7 ms
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=3 ttl=51 time=67.2 ms
64 bytes from omta-po.sys.comcast.net (96.114.157.81): icmp_seq=4 ttl=51 time=59.7 ms
However, I happen to dual boot this laptop, so I switched over to Windows 10 to try pinging mail.comcast.net from there. Lo and behold:
C:UsersScott>ping mail.comcast.net
Pinging imap.ge.xfinity.com [96.117.3.96] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
So it's obviously not set up to respond to ping, but the domain DID get resolved (to something else) or so it seems. I don't know how to begin to debug this sort of problem. Does anyone out there have any ideas? Comcast's customer support was useless, as expected. Thank you.
dns email smtp imap
dns email smtp imap
edited Nov 22 at 12:11
LeonidMew
385215
asked Nov 22 at 4:26
Scott Jacobi
215
edited Nov 22 at 12:11
LeonidMew
385215
asked Nov 22 at 4:26
Scott Jacobi
215
edited Nov 22 at 12:11
LeonidMew
385215
edited Nov 22 at 12:11
LeonidMew
385215
edited Nov 22 at 12:11
LeonidMew
385215
385215
asked Nov 22 at 4:26
Scott Jacobi
215
asked Nov 22 at 4:26
Scott Jacobi
215
asked Nov 22 at 4:26
Scott Jacobi
215
215
Runnslookup mail.comcast.netin both Windows and in Ubuntu and see if theServer:andAddress:line right after the command is the same in both.
– Terrance
Nov 22 at 5:12
Here is how Comcast says to configure thunderbird: link
– TonyB
Nov 22 at 6:21
add a comment |
Runnslookup mail.comcast.netin both Windows and in Ubuntu and see if theServer:andAddress:line right after the command is the same in both.
– Terrance
Nov 22 at 5:12
Here is how Comcast says to configure thunderbird: link
– TonyB
Nov 22 at 6:21
Run
nslookup mail.comcast.net in both Windows and in Ubuntu and see if the Server: and Address: line right after the command is the same in both.– Terrance
Nov 22 at 5:12
Run
nslookup mail.comcast.net in both Windows and in Ubuntu and see if the Server: and Address: line right after the command is the same in both.– Terrance
Nov 22 at 5:12
Here is how Comcast says to configure thunderbird: link
– TonyB
Nov 22 at 6:21
Here is how Comcast says to configure thunderbird: link
– TonyB
Nov 22 at 6:21
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
Can you reconfigure email client to use imap? Seems imap working fine, with address imap.comcast.net
nslookup for mail:
$ nslookup mail.comcast.net
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
mail.comcast.net canonical name = imap.ge.xfinity.com.
Name: imap.ge.xfinity.com
Address: 96.118.242.201
Name: imap.ge.xfinity.com
Address: 96.118.242.237
...
answered Nov 22 at 5:27
LeonidMew
385215
add a comment |
up vote
0
down vote
accepted
tl;dr: This turned out to be an issue with my /etc/resolv.conf file.
Between LeonidMew's answer and Terrance's comment, I was able to piece this together. My nslookup for mail was the same as LeonidMew's. But when I did what Terrance suggested, and tried nslookup in Windows, the Address was pointing to my router at 192.168.0.1. I knew I had seen 127.0.0.53 before when I was Googling around trying to find an answer, and I realized I had seen it in my resolv.conf file. I edited that file, and changed 127.0.0.53 to 192.169.0.1, and my system was successfully able to find and connect with mail.comcast.net. Thanks very much for all of your help.
answered Nov 22 at 12:20
Scott Jacobi
215
1
Depending on what version of Ubuntu you can make that kind of permanent as well. Ubuntu 16.04 see askubuntu.com/questions/988201/… and for Ubuntu 18.04 I have found to do askubuntu.com/a/1057752/231142
– Terrance
Nov 22 at 18:04
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Can you reconfigure email client to use imap? Seems imap working fine, with address imap.comcast.net
nslookup for mail:
$ nslookup mail.comcast.net
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
mail.comcast.net canonical name = imap.ge.xfinity.com.
Name: imap.ge.xfinity.com
Address: 96.118.242.201
Name: imap.ge.xfinity.com
Address: 96.118.242.237
...
answered Nov 22 at 5:27
LeonidMew
385215
add a comment |
up vote
0
down vote
Can you reconfigure email client to use imap? Seems imap working fine, with address imap.comcast.net
nslookup for mail:
$ nslookup mail.comcast.net
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
mail.comcast.net canonical name = imap.ge.xfinity.com.
Name: imap.ge.xfinity.com
Address: 96.118.242.201
Name: imap.ge.xfinity.com
Address: 96.118.242.237
...
answered Nov 22 at 5:27
LeonidMew
385215
add a comment |
up vote
0
down vote
up vote
0
down vote
Can you reconfigure email client to use imap? Seems imap working fine, with address imap.comcast.net
nslookup for mail:
$ nslookup mail.comcast.net
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
mail.comcast.net canonical name = imap.ge.xfinity.com.
Name: imap.ge.xfinity.com
Address: 96.118.242.201
Name: imap.ge.xfinity.com
Address: 96.118.242.237
...
answered Nov 22 at 5:27
LeonidMew
385215
Can you reconfigure email client to use imap? Seems imap working fine, with address imap.comcast.net
nslookup for mail:
$ nslookup mail.comcast.net
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
mail.comcast.net canonical name = imap.ge.xfinity.com.
Name: imap.ge.xfinity.com
Address: 96.118.242.201
Name: imap.ge.xfinity.com
Address: 96.118.242.237
...
answered Nov 22 at 5:27
LeonidMew
385215
answered Nov 22 at 5:27
LeonidMew
385215
answered Nov 22 at 5:27
LeonidMew
385215
answered Nov 22 at 5:27
LeonidMew
385215
385215
add a comment |
add a comment |
up vote
0
down vote
accepted
tl;dr: This turned out to be an issue with my /etc/resolv.conf file.
Between LeonidMew's answer and Terrance's comment, I was able to piece this together. My nslookup for mail was the same as LeonidMew's. But when I did what Terrance suggested, and tried nslookup in Windows, the Address was pointing to my router at 192.168.0.1. I knew I had seen 127.0.0.53 before when I was Googling around trying to find an answer, and I realized I had seen it in my resolv.conf file. I edited that file, and changed 127.0.0.53 to 192.169.0.1, and my system was successfully able to find and connect with mail.comcast.net. Thanks very much for all of your help.
answered Nov 22 at 12:20
Scott Jacobi
215
1
Depending on what version of Ubuntu you can make that kind of permanent as well. Ubuntu 16.04 see askubuntu.com/questions/988201/… and for Ubuntu 18.04 I have found to do askubuntu.com/a/1057752/231142
– Terrance
Nov 22 at 18:04
add a comment |
up vote
0
down vote
accepted
tl;dr: This turned out to be an issue with my /etc/resolv.conf file.
Between LeonidMew's answer and Terrance's comment, I was able to piece this together. My nslookup for mail was the same as LeonidMew's. But when I did what Terrance suggested, and tried nslookup in Windows, the Address was pointing to my router at 192.168.0.1. I knew I had seen 127.0.0.53 before when I was Googling around trying to find an answer, and I realized I had seen it in my resolv.conf file. I edited that file, and changed 127.0.0.53 to 192.169.0.1, and my system was successfully able to find and connect with mail.comcast.net. Thanks very much for all of your help.
answered Nov 22 at 12:20
Scott Jacobi
215
1
Depending on what version of Ubuntu you can make that kind of permanent as well. Ubuntu 16.04 see askubuntu.com/questions/988201/… and for Ubuntu 18.04 I have found to do askubuntu.com/a/1057752/231142
– Terrance
Nov 22 at 18:04
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
tl;dr: This turned out to be an issue with my /etc/resolv.conf file.
Between LeonidMew's answer and Terrance's comment, I was able to piece this together. My nslookup for mail was the same as LeonidMew's. But when I did what Terrance suggested, and tried nslookup in Windows, the Address was pointing to my router at 192.168.0.1. I knew I had seen 127.0.0.53 before when I was Googling around trying to find an answer, and I realized I had seen it in my resolv.conf file. I edited that file, and changed 127.0.0.53 to 192.169.0.1, and my system was successfully able to find and connect with mail.comcast.net. Thanks very much for all of your help.
answered Nov 22 at 12:20
Scott Jacobi
215
tl;dr: This turned out to be an issue with my /etc/resolv.conf file.
Between LeonidMew's answer and Terrance's comment, I was able to piece this together. My nslookup for mail was the same as LeonidMew's. But when I did what Terrance suggested, and tried nslookup in Windows, the Address was pointing to my router at 192.168.0.1. I knew I had seen 127.0.0.53 before when I was Googling around trying to find an answer, and I realized I had seen it in my resolv.conf file. I edited that file, and changed 127.0.0.53 to 192.169.0.1, and my system was successfully able to find and connect with mail.comcast.net. Thanks very much for all of your help.
answered Nov 22 at 12:20
Scott Jacobi
215
answered Nov 22 at 12:20
Scott Jacobi
215
answered Nov 22 at 12:20
Scott Jacobi
215
answered Nov 22 at 12:20
Scott Jacobi
215
215
1
Depending on what version of Ubuntu you can make that kind of permanent as well. Ubuntu 16.04 see askubuntu.com/questions/988201/… and for Ubuntu 18.04 I have found to do askubuntu.com/a/1057752/231142
– Terrance
Nov 22 at 18:04
add a comment |
1
Depending on what version of Ubuntu you can make that kind of permanent as well. Ubuntu 16.04 see askubuntu.com/questions/988201/… and for Ubuntu 18.04 I have found to do askubuntu.com/a/1057752/231142
– Terrance
Nov 22 at 18:04
1
1
Depending on what version of Ubuntu you can make that kind of permanent as well. Ubuntu 16.04 see askubuntu.com/questions/988201/… and for Ubuntu 18.04 I have found to do askubuntu.com/a/1057752/231142
– Terrance
Nov 22 at 18:04
Depending on what version of Ubuntu you can make that kind of permanent as well. Ubuntu 16.04 see askubuntu.com/questions/988201/… and for Ubuntu 18.04 I have found to do askubuntu.com/a/1057752/231142
– Terrance
Nov 22 at 18:04
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1094998%2fcant-resolve-a-domain-in-ubuntu-but-can-in-windows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Run
nslookup mail.comcast.netin both Windows and in Ubuntu and see if theServer:andAddress:line right after the command is the same in both.– Terrance
Nov 22 at 5:12
Here is how Comcast says to configure thunderbird: link
– TonyB
Nov 22 at 6:21