Making resolv.conf changes permanant

[Chris]

On Thu, 2015-04-30 at 22:19 +0000, Steven Jones wrote:
> I can see that there is UDP 53 traffic arriving at the caching server, so "I know" that the client is or appears to be asking the server for info, but it cant reach the server. 
> 
> My "mistake" obviously is to have a new all ubuntu network.  So what I am doing right now is installing Debian 7.08 with bind9.  A setup which I have used for over a decade with no issues in order to try and determine if its the ubuntu client or the ubuntu server that is the problem.
> 
> Frankly, these installs are all std build as default, so I am quite astounded that no one knows what is going on and the documentation is so inadequate on such a major package.
> 
> regards
> 
> Steven
I have found, at least for now, how to make the nameserver entry
in /etc/resolv.conf permanent. I have gone
into /etc/resolvconf/resolvconf.d/head and changed it to read like this:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.1
nameserver 8.8.8.8
nameserver 8.8.4.4

Note - I have not logged out and in or rebooted so I don't really know
if this is permanent or not however it does change my /etc/resolv.conf
to read 

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.1
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 127.0.1.1
search PK5001Z

This works fine as I said in my first post, it shows that 192.168.0.1
being used. I've even commented out that address and it would show
8.8.8.8. as being used:

chris at localhost:~$ dig linuxfoundation.org

; <<>> DiG 9.9.5-3ubuntu0.2-Ubuntu <<>> linuxfoundation.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19822
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;linuxfoundation.org.		IN	A

;; ANSWER SECTION:
linuxfoundation.org.	9443	IN	A	140.211.169.4

;; Query time: 18 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Thu Apr 30 20:39:22 CDT 2015
;; MSG SIZE  rcvd: 64

If that's not confusing enough when I made the change that Karl
mentioned by commenting out dns=dnsmasq
in /etc/NetworkManager/NetworkManager.conf I restarted the network. As I
was loading I noticed this:
Apr 30 20:10:41 localhost NetworkManager[823]: <info>   address 
192.168.0.51
Apr 30 20:10:41 localhost NetworkManager[823]: <info>   prefix 24
(255.255.255.0)
Apr 30 20:10:41 localhost NetworkManager[823]: <info>   gateway
192.168.0.1
Apr 30 20:10:41 localhost NetworkManager[823]: <info>   hostname
'localhost'
Apr 30 20:10:41 localhost NetworkManager[823]: <info>   nameserver
'192.168.0.1'
Apr 30 20:10:41 localhost NetworkManager[823]: <info>   nameserver
'205.171.2.226'
Apr 30 20:10:41 localhost NetworkManager[823]: <info>   domain name
'PK5001Z'

The 205.**** address is embarqmail.com which is what this complaint in
my Spamassassin markup is about

ADMINISTRATOR NOTICE: The query to URIBL was blocked.
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information.

Until I get this figured out every query I make to uribl.com is going to
be blocked. I have got to be missing something but I have no earthly
idea what it is.

Chris
 
-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11°N 97.89°W (Elev. 1092 ft)
20:17:19 up 3 days, 4:12, 6 users, load average: 0.17, 0.27, 0.25
Ubuntu 14.04.2 LTS, kernel 4.0.0-997-generic #201503310205 SMP Tue Mar
31 02:07:04 UTC 2015