I was originally reporting that after setting up my mobile broadband
connection to use a custom dns resolver using network manager, nslookup
still reports that Ubuntu is still using one that is provided by my ISP.

After searching on the internet, I found out that this probably is not
Ubuntu's fault, but instead, happens because my ISP blocks port 53 and
thus redirects all DNS queries to their DNS server.

I do want to circumvent this, for I learned that there are other DNS
resolution providers using ports other than 53 (OpenDNS for example, has
made port 5353 avaible on their servers).

Learning to set this up with dnsmasq seems to be a good place to start,
but I have no idea how to do it.

Basically, I want a DNS proxy to redirect queries to a DNS server of my
choice that uses a port other than port 53. It must run on 127.0.0.1
listening on port 53, and I want all my DNS traffic to pass through it.

Thanks to everyone who may be able to help.

(AFAIK, this could be done on Windows using a software called Acrylic
DNS Proxy very easily.)

** Changed in: network-manager (Ubuntu)
       Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/network-manager/+question/197196

** Description changed:

+ UPDATE: I turned this into a question. See #3 on comments.
+ 
  1) $ lsb_release -rd
  Ubuntu 12.04 LTS
  
  2) $ apt-cache policy network-manager
  network-manager:
    Installed: 0.9.4.0-0ubuntu3
    Candidate: 0.9.4.0-0ubuntu3
    Version table:
   *** 0.9.4.0-0ubuntu3 0
          500 http://ph.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
          100 /var/lib/dpkg/status
  
  What I did:
  * Connect to Mobile Broadband using the DNS server provided by the ISP.
  * Take note using Connection Information the IP Addresses of the DNS servers 
provided by the ISP.
  * Disconnect, go to Network Connections, then Mobile Broadband, select the 
connection and click Edit.
  * Go to the IPv4 Settings tab, in the Method dropdown, change from Automatic 
(PPP) to Automatic (PPP) addresses only.
  * Put custom DNS server settings (say, 8.8.8.8,8.8.4.4) then click Save.
  * Connect using the modified profile.
  
  3) What I expected to happen:
  * I expected my browsers not to throw on me any more DNS lookup failure 
errors.
  
  4) What happened instead
  * Once connected, Connection Information confirms that Primary and Secondary 
DNS has indeed been modified.
  * HOWEVER, when I do nslookup on the terminal, it reports that the DNS server 
used is still the one provided by the ISP.
  * DNS lookup still timeouts frequently, as it has always been with the DNS 
server provided by my ISP, even while pinging the custom server I put (8.8.8.8) 
indicates that my computer can reliably access it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/997242

Title:
  manually specifying DNS server for Mobile Broadband connection does
  not work

Status in “network-manager” package in Ubuntu:
  Invalid

Bug description:
  UPDATE: I turned this into a question. See #3 on comments.

  1) $ lsb_release -rd
  Ubuntu 12.04 LTS

  2) $ apt-cache policy network-manager
  network-manager:
    Installed: 0.9.4.0-0ubuntu3
    Candidate: 0.9.4.0-0ubuntu3
    Version table:
   *** 0.9.4.0-0ubuntu3 0
          500 http://ph.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
          100 /var/lib/dpkg/status

  What I did:
  * Connect to Mobile Broadband using the DNS server provided by the ISP.
  * Take note using Connection Information the IP Addresses of the DNS servers 
provided by the ISP.
  * Disconnect, go to Network Connections, then Mobile Broadband, select the 
connection and click Edit.
  * Go to the IPv4 Settings tab, in the Method dropdown, change from Automatic 
(PPP) to Automatic (PPP) addresses only.
  * Put custom DNS server settings (say, 8.8.8.8,8.8.4.4) then click Save.
  * Connect using the modified profile.

  3) What I expected to happen:
  * I expected my browsers not to throw on me any more DNS lookup failure 
errors.

  4) What happened instead
  * Once connected, Connection Information confirms that Primary and Secondary 
DNS has indeed been modified.
  * HOWEVER, when I do nslookup on the terminal, it reports that the DNS server 
used is still the one provided by the ISP.
  * DNS lookup still timeouts frequently, as it has always been with the DNS 
server provided by my ISP, even while pinging the custom server I put (8.8.8.8) 
indicates that my computer can reliably access it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/997242/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to