[CLUE-Tech] PPTP DNS Problems

[David L. Willson]

Here's an annoying 'feature'.  Can anyone shed some light?

When I PPTP into work, my /etc/resolv.conf updates, but somehow, my
actual resolutions continue to fail.  I can 'dig' and get the right
(internal) address, but when I 'traceroute' or 'ping', I get the wrong
(external) address.

Check this out (actual bash session quoted below) :
----------------------------------------------------------------------
[root at geneva ppp-stuph]# dig fedoracore2.parsec.com
 
; <<>> DiG 9.2.3 <<>> fedoracore2.parsec.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59446
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
 
;; QUESTION SECTION:
;fedoracore2.parsec.com.                IN      A
 
;; ANSWER SECTION:
fedoracore2.parsec.com. 900     IN      A       10.100.0.207
 
;; Query time: 53 msec
;; SERVER: 10.100.0.25#53(10.100.0.25)
;; WHEN: Mon Oct 25 13:11:01 2004
;; MSG SIZE  rcvd: 56
 
[root at geneva ppp-stuph]# traceroute fedoracore2.parsec.com
traceroute to fedoracore2.parsec.com (65.125.246.107), 30 hops max, 38
byte pack ets
----------------------------------------------------------------------

What do you make of that?  I've been on over two hours, but I still seem
to be pulling from some cached something-or-other.