[dns-operations] Question about logger querys with registers points to 127.0.0.1

[Robert Edmonds]

Mark Andrews wrote:
> Yet another misconfigured load balancer.
> 
> Lenovo fix your nameservers.  The listed nameservers either return
> NXDOMAIN, SERVFAIL or garbage for their names.  See below for full
> trace.

> ;; ANSWER SECTION:
> f5-hk01.gtm.lenovo.com. 0       IN      A       127.0.0.1

Oh, right.  It's the nameserver querying itself, then.

Same with the other domain in the original poster's email.

;; QUESTION SECTION:
;lawsorsing.com.                        IN      A

;; AUTHORITY SECTION:
lawsorsing.com.         172800  IN      NS      dns1.registerfly.com.deleted.gandi.net.
lawsorsing.com.         172800  IN      NS      dns2.registerfly.com.deleted.gandi.net.
lawsorsing.com.         172800  IN      NS      dns3.registerfly.com.deleted.gandi.net.

;; ADDITIONAL SECTION:
dns1.registerfly.com.deleted.gandi.net. 172800 IN A 216.40.47.18
dns2.registerfly.com.deleted.gandi.net. 172800 IN A 64.97.159.10
dns3.registerfly.com.deleted.gandi.net. 172800 IN A 65.22.7.10

;; Query time: 38 msec
;; SERVER: 2001:503:a83e::2:30#53(2001:503:a83e::2:30)
;; WHEN: Thu Oct 15 13:19:25 EDT 2015
;; MSG SIZE  rcvd: 181

The glue records point to addresses that are real but lame nameservers,
and actually resolving those nameserver names returns 127.0.0.1 at the
gandi.net nameservers.

;; QUESTION SECTION:
;*.deleted.gandi.net.           IN      A

;; ANSWER SECTION:
*.deleted.gandi.net.    86400   IN      A       127.0.0.1

Unbound has a "do-not-query-localhost" config option (default enabled)
that will prevent sending queries to localhost, but I'm not sure if
similar functionality is available in BIND.

-- 
Robert Edmonds