Michele Neylon :: Blacknight writes: > Surely that's an issue with your resolver and not with enom?
I'm a little surprised I haven't seen someone comment on this issue with their servers (but maybe I missed it in my quick skim; if so, apologies for redundancy): > On 14 Jan 2013, at 17:53, Fan Of Network <[email protected]> wrote: > > ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.6 <<>> > test1.xclusivmedia.com @dns1.name-services.com > > ;; global options: printcmd > > ;; Got answer: > > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43753 > > ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 6, ADDITIONAL: 0 > > > > ;; QUESTION SECTION: > > ;test1.xclusivmedia.com. IN A > > > > ;; AUTHORITY SECTION: > > test1.xclusivmedia.com. 1800 IN A 91.102.91.61 > > test1.xclusivmedia.com. 1800 IN TXT "v=spf1 -all" > > test1.xclusivmedia.com. 3600 IN NS ns1.p28.dynect.net. > > test1.xclusivmedia.com. 3600 IN NS ns2.p28.dynect.net. > > test1.xclusivmedia.com. 3600 IN NS ns3.p28.dynect.net. > > test1.xclusivmedia.com. 3600 IN NS ns4.p28.dynect.net. Why are the A and TXT record in the Authority section? _______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
