Discuss mailing list

[subhuman <discipline AT gmx.net>]

Heureka!

On Thu, 23 Dec 2010 21:49:07 -0500
Zach Gibbens <infocop411 AT gmail.com> wrote:

[snip]
> make sure both /etc/pppd/resolv.conf and /etc/resolv.conf contain
One never stops learning. :) I simply hadn't realized that there are
several resolv.conf's. 
> 
> nameserver 178.63.26.173
> nameserver 217.79.186.148
Having put the above lines in a file on /etc/ppp I ran:
# cat /etc/ppp/resolv.conf.opennic | resolvconf -a ppp0
by which I modified /etc/resolv.conf (or the file that symlink points
to). After that only /etc/ppp/resolv.conf was left to edit manually (by
simply overwriting it with resolv.conf.opennic).
> 
> and then run 3 commands, the order does matter. it will be a fair bit of
> output.
> 
> dig www.opennic.glue
;; QUESTION SECTION:
;www.opennic.glue.              IN      A

;; ANSWER SECTION:
www.opennic.glue.       14400   IN      A       75.127.96.89

;; AUTHORITY SECTION:
opennic.glue.           6245    IN      NS      ns4.opennic.glue.
opennic.glue.           6245    IN      NS      ns2.opennic.glue.
opennic.glue.           6245    IN      NS      ns6.opennic.glue.
opennic.glue.           6245    IN      NS      ns22.opennic.glue.
opennic.glue.           6245    IN      NS      ns21.opennic.glue.
opennic.glue.           6245    IN      NS      ns7.opennic.glue.
opennic.glue.           6245    IN      NS      ns5.opennic.glue.

;; ADDITIONAL SECTION:
ns2.opennic.glue.       917     IN      A       216.87.84.214
ns4.opennic.glue.       917     IN      A       84.200.228.200
ns5.opennic.glue.       917     IN      A       128.177.28.254
ns6.opennic.glue.       917     IN      A       207.192.71.13
ns7.opennic.glue.       917     IN      A       66.244.95.11
ns21.opennic.glue.      917     IN      A       58.6.115.46
ns22.opennic.glue.      917     IN      A       58.6.115.45

> dig www.opennic.glue @178.63.26.173
;; QUESTION SECTION:
;www.opennic.glue.              IN      A

;; ANSWER SECTION:
www.opennic.glue.       14299   IN      A       75.127.96.89

;; AUTHORITY SECTION:
opennic.glue.           6144    IN      NS      ns7.opennic.glue.
opennic.glue.           6144    IN      NS      ns22.opennic.glue.
opennic.glue.           6144    IN      NS      ns5.opennic.glue.
opennic.glue.           6144    IN      NS      ns2.opennic.glue.
opennic.glue.           6144    IN      NS      ns4.opennic.glue.
opennic.glue.           6144    IN      NS      ns6.opennic.glue.
opennic.glue.           6144    IN      NS      ns21.opennic.glue.

;; ADDITIONAL SECTION:
ns2.opennic.glue.       816     IN      A       216.87.84.214
ns4.opennic.glue.       816     IN      A       84.200.228.200
ns5.opennic.glue.       816     IN      A       128.177.28.254
ns6.opennic.glue.       816     IN      A       207.192.71.13
ns7.opennic.glue.       816     IN      A       66.244.95.11
ns21.opennic.glue.      816     IN      A       58.6.115.46
ns22.opennic.glue.      816     IN      A       58.6.115.45

> dig www.opennic.glue @217.79.186.148
> dig www.opennic.glue @83.223.73.116
... and so on

$ ping www.opennic.glue
PING www.opennic.glue (75.127.96.89) 56(84) bytes of data.
64 bytes from ns7.jdcomputers.com.au (75.127.96.89): icmp_req=1 ttl=52 
time=130 ms
64 bytes from ns7.jdcomputers.com.au (75.127.96.89): icmp_req=2 ttl=52 
time=128 ms
64 bytes from ns7.jdcomputers.com.au (75.127.96.89): icmp_req=3 ttl=52 
time=131 ms
64 bytes from ns7.jdcomputers.com.au (75.127.96.89): icmp_req=4 ttl=52 
time=129 ms
64 bytes from ns7.jdcomputers.com.au (75.127.96.89): icmp_req=5 ttl=52 
time=128 ms

Looks good, doesn't it? I guess that after the next restart of pppd
(which I can't do just now because of a currently running download) the
commented 'usepeerdns' in /etc/ppp/peers/dsl-provider will ensure that
no changes will be made by pppd.

Thanks a lot for all your help!
Martin

-- 
Volk ist Opium für eine Religion.