Localhost. and unbound

Unbound
1

Hi,

It seems some people use contructs like:

localhost.domain.tld. IN CNAME localhost.

When asked of unbound, it seems unbound delivers a response that is not an NXDOMAIN
for the localhost. TLD. I guess this is by design, perhaps to avoid more crap from
hitting the root name servers.

However, unbound's answer is:

;; ANSWER SECTION:
localhost. 10800 IN A 127.0.0.1

If you are going to return data for localhost, I guess it should also return a AAAA for ::1

Paul

2

Hi Paul,

Hi,

It seems some people use contructs like:

localhost.domain.tld. IN CNAME localhost.

When asked of unbound, it seems unbound delivers a response that is not
an NXDOMAIN
for the localhost. TLD. I guess this is by design, perhaps to avoid more
crap from
hitting the root name servers.

RFC6303 I think.

However, unbound's answer is:

;; ANSWER SECTION:
localhost. 10800 IN A 127.0.0.1

If you are going to return data for localhost, I guess it should also
return a AAAA for ::1

There should already by a AAAA ::1 for localhost. Are you querying for
a AAAA record?

Best regards,
   Wouter

3

RFC6303 I think.

Ahh yes.

However, unbound's answer is:

;; ANSWER SECTION:
localhost. 10800 IN A 127.0.0.1

If you are going to return data for localhost, I guess it should also
return a AAAA for ::1

There should already by a AAAA ::1 for localhost. Are you querying for
a AAAA record?

I guess it works if you query for A or AAAA. If you query for ANY
it returns nothing. (well SOA)

Paul