intoDNS developement
Adrian Andreias | Thursday, December 13th, 2007The intoDNS development team has taken a small break as we plan on launching the new Elvsoft website. We haven’t forgotten about intoDNS at all and we are preparing new tests and old ones improved. It’s hard to give people good results as a lot of things changed during time, some in our disadvantage. Since it’s almost impossible to always give accurate results we plan on giving people the option to report “problems” and ask us to manually analyze a server and set the results in intoDNS as they should be. We cannot do this for free since some will be tempted to give us a lot of work for nothing, that is why we have to charge every request with a small amount of money (around $5, one time or until a new request). The price will be low and acceptable and it’s the only solution we found so far.
Examples where results will not be accurate:
SPF checks – a lot of people add a SPF record without having any clue if that record is really ok. It’s impossible to test with intoDNS or any other tool like it since we do not know if your e-mail is really going out through your MX or through another IP different than the one(s) listed as your MX.
Mail checks – The same as in the case of SPF, we do not know if your e-mail really goes out through your MX records, we only assume that.
Scott says:
What is the check that you do for glue records. It seems to fail for most sites, saying glue was not sent. I have looked over this many times, my zones do in fact gave glue. Is there perhaps a bug in the way you are checking glue records?
There was a discussion on the isc bind mailing list a few weeks back, and we all looked over multiple zones, to conclude, the test is incorrect.
I would also like to suggest, when there are errors, perhaps I could supply you with some different text. For example, I just bumped my SOA, and the secondary has not picked up on it yet. The error is understood, but it may be nice to say:
Looks like your nameservers do not agree on the SOA serial. Ths SOA records as reported by your nameservers:
xx.xx.xx.xx -> 2009101600
xx.xx.xx.yy -> 2009102000
If you just made an edit to your zone, this is normal. If you have not made any edits to your zone, this should be fixed immediately.
Thanks
[d] says:
When are you planning on supporting ipv6 name servers? That would be a very forward-looking feature!
Categories
Archives