Does geodns support cname chain?

[li45]

No description provided.

[abh]

Can you give me an example of what you mean?

[li45]

my test.com.json:

    "bar" : {
        "a":[["192.168.1.2",100]]
    },
    "www":  {
        "cname": "bar.test.com."
    }

then run dig @127.0.0.1 www.test.com
response:

;; QUESTION SECTION:
;www.test.com.          IN  A

;; ANSWER SECTION:
www.test.com.   60  IN  CNAME   bar.test.com.

no A recode in here.

Expect response:

;; QUESTION SECTION:
;www.test.com.          IN  A

;; ANSWER SECTION:
www.test.com.   60  IN  CNAME   bar.test.com.
bar.test.com.    60 IN  A   192.168.1.2

[abh]

Ah, yes — I believe it works because the resolver will just query again for the other name, but obviously that could be optimized!

There’s an “alias” (I think it’s called) record type that “resolves” the CNAME internally.

I should fix the cname chain thing though.

[semihalev]

abh, for glue records, check my commit semihalev@fc96682, resolve internally for CNAME, MX, NS, but need small boolean (msg.CheckGlue) in dns lib.

[praveenkumar2608]

Ah, yes — I believe it works because the resolver will just query again for the other name, but obviously that could be optimized!

There’s an “alias” (I think it’s called) record type that “resolves” the CNAME internally.

I should fix the cname chain thing though.

@abh @semihalev Is this fixed. Facing same issue