Sponsored Content
Operating Systems Linux Ubuntu Network Manager not setting correct DNS servers Post 302998463 by bakunin on Friday 2nd of June 2017 05:40:55 AM
Old 06-02-2017
Network Manager not setting correct DNS servers

Since a few weeks i use Ubuntu 16 on my laptop:

Code:
# uname -a
Linux xxxx 4.8.0-52-generic #55~16.04.1-Ubuntu SMP Fri Apr 28 14:36:29 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Because i want to use a custom name server i set the properties in the "Edit Connections" dialogue to the following:

Code:
[...]
Method: Automatic (DHCP) addresses only
[...]
DNS Servers: <list of IP-addresses with DNS servers>

And i expected that any time i use this connection that the respective DNS servers are automatically put into the file /etc/resolv.conf (which is actually a link to /run/resolvconf/resolv.conf, as it should be, i am told).

Still, this doesn't happen and in /etc/resolv.conf a name server provided by the DHCP server is mentioned instead of the ones i entered. What am i doing wrong?

bakunin
This User Gave Thanks to bakunin For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

DNS servers

I am supposed to setup a Domain Name Server, and I don't really know how to do this, can someone either help me, or point me in the direction of a site that has a good explination of how to do this. Thanks, Ronnie (5 Replies)
Discussion started by: ignus7
5 Replies

2. IP Networking

My dns entries - are they correct ?

$ttl 38400 thedigitaldream.co.uk. IN SOA digiserv. admin.thedigitaldream.co.uk. ( 1033481631 10800 3600 604800 38400 ) thedigitaldream.co.uk. IN NS digiserv. thedigitaldream.co.uk. IN A 81.97.225.82 www.thedigitaldream.co.uk. IN A 81.97.225.82... (1 Reply)
Discussion started by: matt2kjones
1 Replies

3. Linux

setting primary dns

Hi, I am running Fedora 7. I seem to remember there being a command to determine the primary dns. Can anyone help me find out what it is? Thanks! (2 Replies)
Discussion started by: user23
2 Replies

4. AIX

Dns Servers

My only question is Can we have two auteritative Name servers for a single domain? Just a question. (1 Reply)
Discussion started by: vjm
1 Replies

5. AIX

Servers still querying old DNS server?

Hello, I've created new DNS servers and changed all of the clients /etc/resolv.conf to point to them, but when I check the old DNS logs, I see that the clients are still querying it. Does anybody know why? thanks, (2 Replies)
Discussion started by: ctcuser
2 Replies

6. Shell Programming and Scripting

Setting the correct parameter

Hi Gurus, Here is the issue that I've encountered. VAR1=`hostname | tr '' ''` -> convert hostname to uppercase VAR2=`grep $VAR1 /etc/hosts | awk '{ print $1 }'` -> Since hostname is already in uppercase, grep is unable to find it in /etc/hosts. How to handle VAR2? Is there a... (5 Replies)
Discussion started by: superHonda123
5 Replies

7. Linux

Setting up slave DNS?

can someone point me in the right direction im trying to setup a Slave dns server this is my named.conf file zone "website1.org" { type slave; file"mydb-for-website1-org"; notify NO; };and this is my var/named/mydb-for-website1-org $TTL 3D @ IN SOA ... (1 Reply)
Discussion started by: gangsta
1 Replies

8. IP Networking

DNS and Authoritative Servers

Hey everyone, I've noticed that when I do a dig command, I don't get any authoritative records back. For example a dig to cnn.com just yields: ;; QUESTION SECTION: ;cnn.com. IN A ;; ANSWER SECTION: cnn.com. 300 IN A 157.166.226.25 cnn.com. 300 IN ... (8 Replies)
Discussion started by: Lost in Cyberia
8 Replies

9. UNIX for Dummies Questions & Answers

Help me setting up dns and understanding it.

Hi I need to set up a dns server for Oracle 11g rac setup. I got some files (copied from friend) named.conf and related files in /var/named , i was told that this would work fine. But i am getting some issues. I am attaching the files here. The problem is dig... (1 Reply)
Discussion started by: ankurk
1 Replies
RESOLVCONF.CONF(5)					      System Manager's Manual						RESOLVCONF.CONF(5)

NAME
resolvconf.conf -- resolvconf configuration file DESCRIPTION
resolvconf.conf is the configuration file for resolvconf(8). The resolvconf.conf file is a shell script that is sourced by resolvconf(8), meaning that resolvconf.conf must contain valid shell commands. Listed below are the standard resolvconf.conf variables that may be set. After updating this file, you may wish to run resolvconf -u to apply the new configuration. RESOLVCONF OPTIONS
interface_order These interfaces will always be processed first. If unset, defaults to the following:- lo lo[0-9]* dynamic_order These interfaces will be processed next, unless they have a metric. If unset, defaults to the following:- tap[0-9]* tun[0-9]* vpn vpn[0-9]* ppp[0-9]* ippp[0-9]* search_domains Prepend search domains to the dynamically generated list. search_domains_append Append search domains to the dynamically generated list. domain_blacklist A list of domains to be removed from consideration. To remove a domain, you can use foo.* To remove a sub domain, you can use *.bar name_servers Prepend name servers to the dynamically generated list. You should set this to 127.0.0.1 if you use a local name server other than libc. name_servers_append Append name servers to the dynamically generated list. name_server_blacklist A list of name servers to be removed from consideration. The default is 0.0.0.0 as some faulty routers send it via DHCP. To remove a block, you can use 192.168.* private_interfaces These interfaces name servers will only be queried for the domains listed in their resolv.conf. Useful for VPN domains. This is equivalent to the resolvconf -p option. state_dir Override the default state directory of /run/resolvconf. This should not be changed once resolvconf is in use unless the old direc- tory is copied to the new one. LIBC OPTIONS
The following variables affect resolv.conf(5) directly:- resolv_conf Defaults to /etc/resolv.conf if not set. resolv_conf_options A list of libc resolver options, as specified in resolv.conf(5). resolv_conf_passthrough When set to YES the latest resolv.conf is written to resolv_conf without any alteration. resolv_conf_sortlist A libc resolver sortlist, as specified in resolv.conf(5). resolv_conf_local_only If a local nameserver is configured then the default is just to specify that and ignore all other entries as they will be configured for the local nameserver. Set this to YES to list them instead, if you need working DNS and the local nameserver stops functioning at the expense of duplicated server queries. SUBSCRIBER OPTIONS
openresolv ships with subscribers for the name servers dnsmasq(8), named(8), pdnsd(8) and unbound(8). Each subscriber can create configura- tion files which should be included in in the subscribers main configuration file. dnsmasq_conf This file tells dnsmasq which nameservers to use for specific domains. dnsmasq_resolv This file tells dnsmasq which nameservers to use for global lookups. Example resolvconf.conf for dnsmasq: nameservers=127.0.0.1 dnsmasq_conf=/etc/dnsmasq-conf.conf dnsmasq_resolv=/etc/dnsmasq-resolv.conf Example dnsmasq.conf: listen-address=127.0.0.1 conf-file=/etc/dnsmasq-conf.conf resolv-file=/etc/dnsmasq-resolv.conf named_options Include this file in the named options block. This file tells named which nameservers to use for global lookups. named_zones Include this file in the named global scope, after the options block. This file tells named which nameservers to use for specific domains. Example resolvconf.conf for named: nameservers=127.0.0.1 named_options=/etc/named-options.conf named_zones=/etc/named-zones.conf Example named.conf: options { listen-on { 127.0.0.1; }; include /etc/named-options.conf; }; include /etc/named-zones.conf; pdnsd_conf This is the main pdnsd configuration file which we modify to add our forward domains to. If this variable is not set then we rely on the pdnsd configuration file setup to read pdnsd_resolv as documented below. pdnsd_resolv This file tells pdnsd about global nameservers. If this variable is not set then it's written to pdnsd_conf. Example resolvconf.conf for pdnsd: nameservers=127.0.0.1 pdnsd_conf=/etc/pdnsd.conf # pdnsd_resolv=/etc/pdnsd-resolv.conf Example pdnsd.conf: global { server_ip = 127.0.0.1; status_ctl = on; } server { # A server definition is required, even if emtpy. label="empty"; proxy_only=on; # file="/etc/pdnsd-resolv.conf"; } unbound_conf This file tells unbound about specific and global nameservers. Example resolvconf.conf for unbound: nameservers=127.0.0.1 unbound_conf=/etc/unbound-resolvconf.conf Example unbound.conf: include: /etc/unbound-resolvconf.conf SEE ALSO
resolv.conf(5) and resolvconf(8). AUTHORS
Roy Marples <roy@marples.name> BUGS
Please report them to http://roy.marples.name/projects/openresolv BSD
March 19, 2012 BSD
All times are GMT -4. The time now is 06:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy