From AWS route 53 to Bind9
Reindl Harald
h.reindl at thelounge.net
Sun Feb 5 17:24:19 UTC 2017
Am 05.02.2017 um 13:11 schrieb Cogumelos Maravilha:
> On 02/05/2017 12:29 AM, Reindl Harald wrote:
>>
>> Am 04.02.2017 um 22:30 schrieb Mark Andrews:
>>> It has been suggested many times that there should be a record which
>>> says which server(s) serve a zone for HTTP and HTTPS. We could do
>>> this with SRV (_http._tcp.example.com and _https._tcp.example.com)
>>> or we could come up with a new record example.com HTTP <server>.
>>
>> for the thread starter - use https://intodns.com/ to find out and fix
>> common mistakes in dns zones
>
> Since bind don't load that zone domain with errors there's no point to
> debug using tools like intodns.com
then the whole subject is misleading
as already explained you can't define the "example.com" as CNAME *and*
anything else and looking how a CNAME works you know why
http://serverfault.com/questions/694895/cname-record-with-any-other-resource-record-in-bind
;; ANSWER SECTION:
www.rhsoft.net. 86400 IN CNAME proxy.thelounge.net.
proxy.thelounge.net. 86400 IN TXT "v=spf1 a
ip4:91.118.73.0/24 ip4:95.129.202.170 -all"
;; ANSWER SECTION:
www.rhsoft.net. 86400 IN CNAME proxy.thelounge.net.
proxy.thelounge.net. 86400 IN A 91.118.73.4
More information about the bind-users
mailing list