nslookup www.google.com 1.1.1.1
Google DNS: nslookup www.google.com 8.8.8.8
-- Linux -- dig @1.1.1.1 www.google.com
Google DNS: dig @8.8.8.8 www.google.com nslookup www.google.com 1.1.1.1
Google DNS: nslookup www.google.com 8.8.8.8
-- Linux -- dig @1.1.1.1 www.google.com
Google DNS: dig @8.8.8.8 www.google.com nslookup www.google.com 1.1.1.1
Google DNS: nslookup www.google.com 8.8.8.8
-- Linux -- dig @1.1.1.1 www.google.com
Google DNS: dig @8.8.8.8 www.google.com detailed.com. 3600 IN TXT "v=spf1 include:smtp.groovehq.com ~all"
detailed.com. 3600 IN TXT "v=spf1 mx include:send.aweber.com -all"
Should be: detailed.com. IN TXT "v=spf1 mx include:send.aweber.com include:smtp.groovehq.com ~all"
2. You SOA record is incorrect detailed.com. 172800 IN NS ns.sourcedns.com.
detailed.com. 172800 IN NS ns1.sourcedns.com.
Your current SOA is: detailed.com. 3600 IN SOA ns.liquidweb.com. admin.liquidweb.com. 2017042600 86400 7200 3600000 14400
In your SOA, ns.liquidweb.com is incorrect. It should be ns.sourcedns.com
We tried the log ingest but even for 1 VM, it was several GB per day data. 99% of the log data was irrelevant and trying to figure out how to filter it via New Relic was extremely difficult to figure out. We turned it off.
I guarantee that if they turn this on on 5/3, then 90% of their free accounts will shoot past the 100GB free tier. They hope people will convert to paid plans.
If they provided clear and easy to understand examples on how to filter the data before sending it into their environment, it would allow people to decide what data to send and then only have to pay for the data that is relevant instead of EVERYTHING.