Hi again Peter, again thanks for your help.
The reverse lookup seems to work (atleast with dig)
dig ptr -x 74.125.237.68 @192.168.0.57
; <<>> DiG 9.8.1-P1 <<>> ptr -x 74.125.237.68 @192.168.0.57
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47736
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;68.237.125.74.in-addr.arpa. IN PTR
;; AUTHORITY SECTION:
in-addr.arpa. 86400 IN SOA ns1.infoteq.com.au.
hostmaster.infoteq.com.au. 2012123102 28800 7200 604800 86400
;; Query time: 6 msec
;; SERVER: 192.168.0.57#53(192.168.0.57)
;; WHEN: Fri Mar 15 08:18:34 2013
;; MSG SIZE rcvd: 109
I've removed the zone anyway, and am now getting...
ping google.com.au
PING google.com.au (74.125.237.88) 56(84) bytes of data.
>From UbuntuDev.local (192.168.0.57): icmp_seq=1 Redirect Host(New nexthop:
>192.168.0.1)
64 bytes from syd01s06-in-f24.1e100.net (74.125.237.88): icmp_req=1 ttl=54
time=48.1 ms
>From UbuntuDev.local (192.168.0.57): icmp_seq=2 Redirect Host(New nexthop:
>192.168.0.1)
64 bytes from syd01s06-in-f24.1e100.net (74.125.237.88): icmp_req=2 ttl=55
time=48.4 ms
>From UbuntuDev.local (192.168.0.57): icmp_seq=3 Redirect Host(New nexthop:
>192.168.0.1)
64 bytes from syd01s06-in-f24.1e100.net (74.125.237.88): icmp_req=3 ttl=54
time=48.0 ms
>From UbuntuDev.local (192.168.0.57): icmp_seq=4 Redirect Host(New nexthop:
>192.168.0.1)
64 bytes from syd01s06-in-f24.1e100.net (74.125.237.88): icmp_req=4 ttl=55
time=48.0 ms
>From UbuntuDev.local (192.168.0.57): icmp_seq=5 Redirect Host(New nexthop:
>192.168.0.1)
however, this is still slow.
Peter.
On Thu, 14 Mar 2013 04:04:06 PM Peter van Dijk wrote:
> Hello Peter,
>
> On Mar 11, 2013, at 10:10 , Peter Nunn wrote:
>
> > (192.168.0.57 being the internal name server).
> >
> > Ping with this configuration.
> >
> > ping google.com
> > PING google.com (74.125.237.68) 56(84) bytes of data.
> > 64 bytes from 74.125.237.68: icmp_req=1 ttl=55 time=51.1 ms
> > 64 bytes from 74.125.237.68: icmp_req=2 ttl=55 time=62.9 ms
> > 64 bytes from 74.125.237.68: icmp_req=3 ttl=55 time=50.1 ms
> > 64 bytes from 74.125.237.68: icmp_req=4 ttl=55 time=50.7 ms
> > 64 bytes from 74.125.237.68: icmp_req=5 ttl=55 time=50.6 ms
> > ^C64 bytes from 74.125.237.68: icmp_req=6 ttl=55 time=51.2 ms
> >
> > --- google.com ping statistics ---
> > 6 packets transmitted, 6 received, 0% packet loss, time 25402ms
> > rtt min/avg/max/mdev = 50.167/52.820/62.992/4.572 ms
> >
> > each ping responce takes about 4 seconds.
> >
> > Without the internal NS
> >
> > ping google.com
> > PING google.com (74.125.237.105) 56(84) bytes of data.
> > 64 bytes from syd01s12-in-f9.1e100.net (74.125.237.105): icmp_req=1 ttl=55
> > time=189 ms
> > 64 bytes from syd01s12-in-f9.1e100.net (74.125.237.105): icmp_req=2 ttl=55
> > time=180 ms
> > 64 bytes from syd01s12-in-f9.1e100.net (74.125.237.105): icmp_req=3 ttl=55
> > time=195 ms
> > 64 bytes from syd01s12-in-f9.1e100.net (74.125.237.105): icmp_req=4 ttl=55
> > time=56.4 ms
> > 64 bytes from syd01s12-in-f9.1e100.net (74.125.237.105): icmp_req=5 ttl=55
> > time=78.1 ms
> > ^C
> > --- google.com ping statistics ---
> > 5 packets transmitted, 5 received, 0% packet loss, time 4001ms
> > rtt min/avg/max/mdev = 56.443/139.940/195.003/59.866 ms
> >
> >
> > I get about 2 ping returns per second.
>
> Ping should do one return per second. If you get more, your clock is broken!
>
> > infoteq.com.au
> > intq.com.au
> > in-addr.arpa
>
> This zone (in-addr.arpa) is overriding your reverse lookups. Remove it, or
> replace it with a more specific version if you really need to.
>
> Note that presence of the zone only explains the lack of names in the ping
> output, not the delays you are experiencing. My best guess about the delays
> is that your in-addr.arpa zone is also broken. Try a 'dig ptr -x
> 74.125.237.68 @192.168.0.57' to see; if it says SERVFAIL, this might explain
> the delays.
>
> Kind regards,
>
--
Director
InfoTeq Pty Ltd
0412 174 230
03 9017 2707
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
