On Sun, August 12, 2012 9:47 am, Kyle wrote: > This might be a bit simplistic but;
> If Verizon are claiming they are receiving a "Domain Not Found" error > _and_ you are certain your domains are correctly configured, > then isn't the problem likely to lie with Net Registry? Kyle, thanks yes, that's my assertion, convincing NetREgistry is a somewhat different matter, though, Verizon sent me his dig output where he is getting SERVFAIL from all three namseservers, the issue persevered about 48 hours (my fault for not identifying it sooner....) > The domains are 'hosted' (on a DNS basis) with them. Ergo they are > supposed to return the record, surely? > > Or alternatively, is there some form of blacklisting going on somewhere > in the chain? > > ------------------------------------------------------------------------ > Kind Regards > > > Kyle > > > > On 12/08/12 8:53 AM, li...@sbt.net.au wrote: > >> On Sat, August 11, 2012 10:20 pm, Amos Shapira wrote: >> thanks, Amos >> >> reverse is OK other domains have been on this server for some time, with >> same dns servers, no issues were seen >> >> in my testing on Sat, I also managed to get SERVFAIL responses at times >> >> >> I think I should maybe run a dig query every few minutes and log it ? >> >> >> I tried mxtoolbox and intodns to cross check, at one point, output from >> dig contradicted what the website was saying.... so, not sure >> >> and, mail server locked out mxtoolbox for portscanning the >> mailserver... >> >> > -- > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html > > -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
