Why doesn't Fedora 23 search DNS

asked 2015-11-29 14:26:59 -0600

andrewm659 gravatar image

updated 2015-12-01 00:08:34 -0600

I have some servers setup via static IP (CentOS 7.x) and all the windows PCS (including my fedora laptop) are DHCP, with my DNS server in the options. When I try to resolve DNS from the Fedora PC it won't work from the command line. And it won't work at all. Everything else works fine. Thoughts?

Yes.

[me@wolverine ~] $ cat /etc/resolv.conf 
# Generated by NetworkManager
search borg.local
nameserver 10.150.1.60
nameserver 8.8.8.8
[me@wolverine ~] $ 

[me@wolverine ~] $ dig @10.150.1.60 google.com +short
216.58.216.110
[me@wolverine ~] $ 

[me@wolverine ~] $ dig @10.150.1.60 fedoraproject.org +short
152.19.134.198
140.211.169.196
213.175.193.206
140.211.169.206
209.132.181.15
152.19.134.142
67.219.144.68
209.132.181.16
5.175.150.50
[me@wolverine ~] $ 

Maybe its a firmware/driver issue???

[me@wolverine ~] $ ethtool -i wlp7s0
driver: rtl8192ce
version: 4.2.6-301.fc23.x86_64+debug
firmware-version: N/A
expansion-rom-version: 
bus-info: 0000:07:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
[me@wolverine ~] $

[me@wolverine ~] $ dmesg |grep -i ethernet
[    9.288631] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[me@wolverine ~] $

By the way this happens on wired and wireless...

edit retag flag offensive close merge delete

Comments

Just to make sure: you're using your own servers for DNS while connected to the same LAN. I ask because your servers probably don't have routable IP addresses and if you're connected from a remote location, you wouldn't be able to reach them. BTW, can you ping those servers from your Fedora PC?

sideburns gravatar imagesideburns ( 2015-11-29 19:19:58 -0600 )edit

Can you share some info, like Fedora's /etc/resolv.conf, and the output of dig fedoraproject.org and dig fedoraproject.org @8.8.4.4 ?

randomuser gravatar imagerandomuser ( 2015-11-29 19:26:09 -0600 )edit

I moved your update to the question, because it was not an answer. It shows you resolving DNS from the command line. Can you update your question with an example of DNS not resolving from the command line as well?

randomuser gravatar imagerandomuser ( 2015-12-01 00:10:11 -0600 )edit

Can you post the output of dig executed without arguments? I'm interested in seeing which DNS server dig attempts to use without instruction. We may be able to better identify the cause of the improper DNS server selection if we know what is being selected. As described in the dig man page, dig should consult /etc/resolv.conf, so we should expect 10.150.1.60 to be used.

bitwiseoperator gravatar imagebitwiseoperator ( 2015-12-02 10:00:21 -0600 )edit