Re: Bind unable to get MX reocrd from Parrent name server

2013-07-05 Thread John Wobus
The other DNS server software is working around or ignoring the issues. Server software varies in how much it ignores or works around bad domain setups. Also, in some situations, configuration problems result in symptoms that come and go. One reason DNS software is picky about correct setups is

Re: Bind unable to get MX reocrd from Parrent name server

2013-07-05 Thread Matus UHLAR - fantomas
On 05.07.13 12:59, Fosiul Alam wrote: I am not the domain admin for "rbcaa.co.za" I can see they have issue with their domain setup . but what I want to know is : when all Dns server can resolved their mx record example , mxtoolbox,introdns,google .. (Despite they have issue with their dns setup

Re: Bind unable to get MX reocrd from Parrent name server

2013-07-05 Thread Steven Carr
Their setup is broken, it doesn't work for me either... sjcarr@elmo:~ $ dig @ns1.yithosting.co.za rbcaa.co.za mx ; <<>> DiG 9.8.3-P1 <<>> @ns1.yithosting.co.za rbcaa.co.za mx ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19408 ;; fla

Re: Bind unable to get MX reocrd from Parrent name server

2013-07-05 Thread Fosiul Alam
Hi thanks for reply, I am not the domain admin for "rbcaa.co.za" I can see they have issue with their domain setup . but what I want to know is : when all Dns server can resolved their mx record example , mxtoolbox,introdns,google .. (Despite they have issue with their dns setup for that domain (as

Re: Bind unable to get MX reocrd from Parrent name server

2013-07-05 Thread Steven Carr
Your glue is broken. You need to update the glue NS records in the parent to reflect the actual nameservers that are authoritative for the zone. It also looks like you could have some data mismatch between zones hosted on (ns1.yithosting.co.za + ns2.yithosting.co.za) and (demeter.is.co.za + babylo