Cannot use real top-level domain

[mitar]

I am using -environment server and -domain example.com and if I try to resolve server.example.com I get back all IPs inside the environment, instead of real server.example.com IP for that server. Even crazier, if I try to resolve example.com, I get back 0.0.0.0.

I think that everything from environment up (inclusive) should be recursed to provided DNS server.

[miekg]

[ Quoting notifications@github.com in "[skydock] Cannot use real top-level..." ]

I am using -environment server and -domain example.com and if I try to resolve server.example.com I get back all IPs inside the environment, instead of real server.example.com IP for that server. Even crazier, if I try to resolve example.com, I get back 0.0.0.0.

I think that everything from environment up should be recursed to provided DNS server.

Can you reproduce this with a skyDNS only setup?

/Miek

Miek Gieben

[mitar]

Hm, not sure how to do that? I just used docker containers available here and ran them using existing domain for top-level domain and existing server name for environment. Any instructions how should I test this only with skyDNS?

[miekg]

[ Quoting notifications@github.com in "Re: [skydock] Cannot use real top-l..." ]

Hm, not sure how to do that? I just used docker containers available here and ran them using existing domain for top-level domain and existing server name for environment. Any instructions how should I test this only with skyDNS?

You need to figure out the command line used for SkyDNS and then start skydns
and query it to see what it returns.

Note: i think skydock still uses skydns version 1, not skydns version 2, which
is the version I care about :)

/Miek

Miek Gieben

[mitar]

Yes, it uses version 1.