[Pdns-users] Screwy pdns configuration.

[Peter van Dijk]

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,
-- 
Peter van Dijk
Netherlabs Computer Consulting BV - http://www.netherlabs.nl/