Yes I have checked intodns.com. The errors on there disappear when I restart bind except for the one that says it has NO GLUE for ns2.
However when I checked it just now I am getting the Same Glue error which is a yellow ! where the ns1 server is being reported to have the same ip as what I told them for the ns2 server, and I don't even know if this should be an ip of the ns2 server. It is just a different ip that points at the server.
Here is that error:
Same Glue Looks like the A records (the GLUE) got from the parent zone check are different than the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do.I detected some problems as follows:
For ns1.domain.com the parent reported: ['ipaddress2'] and your nameservers reported: ['ipaddress1']
There are some other blue ! in various places but it seems most sites have these, even google.com. The only one that is different which is related is one that says:
Glue for NS records INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. The nameservers without glue are:
You can fix this for example by adding A records to your nameservers for the zones listed above.
At this point there is nothing in the red but I am guessing it will go back to that soon so I can show you those errors. They go away when I restart BIND for some reason or other.