If you configure your computer to access your preferred DNS servers directly, the system should respect that, and DNS requests will be passed straight through the router. However, have you confirmed that the configuration changes you made in the computer have actually stuck? The reason I ask is that the DNS subsystem in Debian (and presumably Debian-based distros) changed a little while back. Previously you could edit /etc/resolvconf directly, but now if you do that it gets overwritten on the first reboot. So you have to make the change elsewhere, and I'm not sure how Mint arranges this.
Blackeagle -- Someone has typed a malformed link! I wonder who it was? ::)
Oooops :-[
<snip> I haz repaired it now b*cat. I'm sure your *nix experience would be most welcome here :)
# Generated by dhcpcd from eth0
# /etc/resolv.conf.head can replace this line
nameserver 192.168.1.254
# /etc/resolv.conf.tail can replace this line# Generated by dhcpcd from eth0
# /etc/resolv.conf.head can replace this line
search lan
nameserver 127.0.0.1
nameserver 94.30.127.100
nameserver 89.145.254.78
nameserver 192.168.1.254
# /etc/resolv.conf.tail can replace this linednsmasq -o start in my rc.local to start my local nameserver after updating the resolv.confdig povray.org
; <<>> DiG 9.7.4-P1 <<>> povray.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4507
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;povray.org. IN A
;; ANSWER SECTION:
povray.org. 3600 IN A 203.29.75.48
;; AUTHORITY SECTION:
povray.org. 414 IN NS ns1.povray.org.
povray.org. 414 IN NS ns1.aussie.org.
;; Query time: 2099 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Apr 30 12:06:46 2012
;; MSG SIZE rcvd: 87
dig povray.org
; <<>> DiG 9.7.4-P1 <<>> povray.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15118
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;povray.org. IN A
;; ANSWER SECTION:
povray.org. 3596 IN A 203.29.75.48
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Apr 30 12:06:50 2012
;; MSG SIZE rcvd: 44
Hi asbokid - thanks for that.
I do configure the network as per your screenshot and the settings remain in place after reconnect/reboot etc. However, when I access the Opendns website to test the connection, I get the Oops! message and clicking their other links shows I'm not on their service! Frankly, I'm stumped.............
Rich
$ ping hubblelkdfjsddskfjsddfg.com
ping: unknown host hubblelkdfjsddskfjsddfg.com
$ sudo netstat -nucp
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 0 0 192.168.1.2:60078 8.8.8.8:53 ESTABLISHED 10899/ping
This reply to peter and asbokid - thanks again for your help
When I try to open /etc/resolve.conf in Terminal I get this, which suggests my system might not be configured correctly -
~ $ /etc/resolve.conf
bash: /etc/resolve.conf: No such file or directory
richard@xxxxxxxxx ~ $ sudo /etc/resolve.conf
[sudo] password for richard:
sudo: /etc/resolve.conf: command not found
$ gedit /etc/resolv.conf
Can you recommend a good, basic beginners guide to using Terminal?
$ sudo netstat -nucp
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 0 0 192.168.1.2:60078 8.8.8.8:53 ESTABLISHED 10899/ping
My bad! It's /etc/resolv.conf (no 'e' on the end). It's just a text file rather than a program to run, so load it with a text editor (e.g. gedit)
My eyesight! I didn't pick up the correct spelling in your screenshot!
I edited and saved resolv.conf then restarted but on checking it had placed the router DNS addresses above mine in the list. Thus -Code: [Select]nameserver 127.0.0.1
nameserver 194.168.4.100
nameserver 194.168.8.100
nameserver 208.67.222.222
nameserver 208.67.220.220
The 1st line seems correct, the 2nd and 3rd are the Virgin nameservers. The final 2 are opendns, which is what I want.
Of course if it was a vanilla modem/router, as distinct to one molested/violated by the ISP, I would advise setting the modem/router to hand out the IP addresses of the DNS servers which were desired to be used. Then all systems on the LAN just need to use the modem/router's LAN address for the DNS server. :-X
QuoteSomething is still retrieving the nameserver IP addresses from your Virgin router. Thinking back to the bad old days of dialup, those nameserver identities can also be provided during the ppp handshake as well as by DHCP. Two places to check..Ok, but where? In the computer or in the router?
$ sudo netstat -nlup
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 0 0 0.0.0.0:68 0.0.0.0:* 13422/dhclient
udp 0 0 0.0.0.0:51413 0.0.0.0:* 20322/transmission-
udp 0 0 0.0.0.0:631 0.0.0.0:* 1516/cupsd
udp 0 0 0.0.0.0:43682 0.0.0.0:* 20322/transmission-
$ sudo netstat -nlup
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 0 0 0.0.0.0:53 0.0.0.0:* 12345/adnsserver
$ sudo netstat -nlup
b*cat
As for "with TalkTalk (shiver)", Black Eagle, Asbokid and I are known users of that ISP / CP. As end-users with adequate knowledge of "what's what", we are content with what we are provided by TT. :-\
And very good too! Unfortunately, my experience with TT was a little different.............. ::)
It seems, to me, that you current issue is down to uncertainty with the Linux Mint distribution. Yes, the correct configuration of each system connected to your LAN can override the use of the modem/router as your local DNS server.
Hi asbokid - the output is -Code: [Select]Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 0 0 0.0.0.0:53 0.0.0.0:* 1172/dnsmasq
I see from the first line that dnsmasq is listed. I installed that as part of my feeble attempts to resolve this issue but truthfully, I've no idea what it does or whether I've configured it correctly!
$ sudo apt-get remove dnsmasq
Automatic (DHCP)
Automatic (DHCP) addresses only <----
Manual
Link-Local Only
Shared to other computers
Disabled
$ cat /etc/resolv.conf
# Generated by NetworkManager
$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 208.67.222.222
nameserver 208.67.222.220
Unless you definitely want DNS caching, maybe remove dnsmasq too. Done
How are you starting and stopping networking? Via network applet - left click, disconnect/reconnect as appropriate
When the Network Manager was used to edit the connection settings to add those OpenDNS name server addresses, were those modifications made to the correct connection listed under "Wired" connections? Yes. In fact I set up 'wired 1' and 'wired 2'. I changed #2 to the opendns settings and #1 to the same as the router. I did this as a precaution in case I messed up; this way I knew I'd still have internet access on one of them. But here's the thing - I also tried leaving #2 blank, saved, disconned and reconned #2 but still connected ok! Which suggests the applet is having no effect whatsoever?
Select "Automatic (DHCP) Addresses Only" under IPv4 Settings. Maybe also check that there isn't a conflicting nameserver option configured under "IPv6 Settings". Done, and no IPv6 options.
Then enter the DNS servers you want: e.g. 208.67.222.222, 208.67.222.220 Done
Click 'Save' and 'Close' the NetworkManager applet window. Done
Now Left Click on the NetworkManager taskbar icon and left click 'Wired Network | Disconnect'. Done - on #1 in this instance
From a shell type the following command and note that the output is the same as below. It shows that no nameserver is configured (because the network is down).
But I get this!
# Generated by resolvconf
nameserver 194.168.4.100
nameserver 194.168.8.100
Now Left Click again on the NetworkManager applet. Left click 'Wired connection 1' to bring the connection back up again. Wait until the DHCP server on the Virgin router has done its stuff (the spinny icon thingy on the taskbar has stopped spinning). Done
From a shell run the following command again and hopefully you should see this output.Code: [Select]$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 208.67.222.222
nameserver 208.67.222.220
And then this!
# Generated by resolvconf
nameserver 194.168.4.100
nameserver 194.168.8.100
nameserver 208.67.222.222
nameserver 208.67.220.220
I set up 'wired 1' and 'wired 2'. I changed #2 to the opendns settings and #1 to the same as the router. I did this as a precaution in case I messed up; this way I knew I'd still have internet access on one of them. But here's the thing - I also tried leaving #2 blank, saved, disconned and reconned #2 but still connected ok! Which suggests the applet is having no effect whatsoever?
But I get this!Code: [Select]# Generated by resolvconf...
nameserver 194.168.4.100
nameserver 194.168.8.100
And then this!Code: [Select]# Generated by resolvconf
nameserver 194.168.4.100
nameserver 194.168.8.100
nameserver 208.67.222.222
nameserver 208.67.220.220
$ gedit /etc/network/interfaces
dns-nameservers 194.168.4.100 194.168.8.100
#dns-nameservers 194.168.4.100 194.168.8.100
$ cat /etc/resolv.conf
Edit: I found how to install /etc/rc.d/init.d/nscd : ran it but still same!
# Generated by NetworkManager
nameserver 192.168.1.254I then changed the DNS servers to 208.67.222.222, 208.67.222.220 using the "Editing Wired connection 1" popup as shown on asbokid's post.# Generated by NetworkManager
nameserver 208.67.222.222
nameserver 208.67.220.220Then I went to http://www.opendns/welcome and got "Welcome to OpenDNS".Hi again,
Now I'm a bit mystified as to why you've had so many problems getting to use OpenDNS. Not as much as I am!
So much so that I made a Mint 12 (32 bit) installation under VirtualBox. Wow! Above and beyond the call of duty I'd say!
The initial installation showed 192.168.1.254 as the DNS. That's what I expected as that's my router.
resolv.conf was:Code: [Select]# Generated by NetworkManagerI then changed the DNS servers to 208.67.222.222, 208.67.222.220 using the "Editing Wired connection 1" popup as shown on asbokid's post.
nameserver 192.168.1.254
resolv.conf had changed to:Code: [Select]# Generated by NetworkManagerAs you can see from the previous posts, my results were different from those expected! Resov.conf produced the info but when I went back to check, system said it wasn't installed!
nameserver 208.67.222.222
nameserver 208.67.220.220
Elapsed time for all that was about 30 mins, not counting Mint download time; and I was doing something else for most of the time, too!
Maybe it's worth thinking about doing a complete reinstall of Mint as something in your system seems a bit misconfigured. Wipe the disk and start again. It wouldn't take too long. That's something I'd considered and I may yet do, but for now (after all the messing about) I'll let things run a while and see what occurs!
Cheers,
Peter
/sbin/resolvconf (the binary) was probably installed automatically as a dependency of another package you installed.. e.g. nscd or dnsmasq.
Whilst the main package, e.g. dnsmasq may have been removed, sometimes the files from a dependent package, e.g. resolvconf, remain.
EDIT: It looks like that is what happened when you installed dnsmasq. resolvconf is listed as a "suggested package" to install with it..
It seems that resolvconf is provided by two different Debian packages.. one package is called resolvconf and another is called openresolv.
Since resolvconf (the package) is not installed on golfer's machine, the finger of suspicion points also at the other package, openresolv.
All a bit academic now. Glad you got it sorted. The Linux Mint forum might be a better place for these questions.
cheers, a
Asbokid, you're definitely a genius and the pint is yours! I removed completely resolv.conf through package manger and my connection settings worked immediately. Openresolv had not been installed.
Funny how some things are simple innit..............but only when you know how!