You are in fact correct Harry, I never bothered with a whois, had I done so I would have picked it up, put it down to too early in the morning, so this problem is out of Jared's control, unless he also manages that domain.
Ohh and nice to see you are actually behaving yourself on this list :) On 07/08/2014 08:40, Reindl Harald wrote: > Am 07.08.2014 um 00:33 schrieb Noel Butler: > >> Apart from stupid SOA values, losscontrol360.com seems OK > > OK? the failing NS query is caused by the errors below > this domain only works by luck from time to time > > [harry@srv-rhsoft:~]$ dig NS losscontrol360.com > ; <<>> DiG 9.9.4-P2-RedHat-9.9.4-15.P2.fc20 <<>> NS losscontrol360.com > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 49902 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 > > http://www.intodns.com/losscontrol360.com [1] > > Error Nameservers are lame ERROR: looks like you have lame nameservers. The > following nameservers are lame: > 54.241.6.128 > 54.243.153.234 > 107.6.6.8 > > Error Missing nameservers reported by parent FAIL: The following nameservers > are listed at your nameservers as > nameservers for your domain, but are not listed at the parent nameservers > (see RFC2181 5.4.1). You need to make > sure that these nameservers are working.If they are not working ok, you may > have problems! > b1.uberns.com > a1.uberns.com > > Error Missing nameservers reported by your nameservers ERROR: One or more of > the nameservers listed at the parent > servers are not listed as NS records at your nameservers. The problem NS > records are: > ns22.netriplex.com > ns21.netriplex.com > ns23.netriplex.com > ns20.netriplex.com > This is listed as an ERROR because there are some cases where nasty problems > can occur (if the TTLs vary from the > NS records at the root servers and the NS records point to your own domain, > for example) > > Error Stealth NS records sent Stealth NS records were sent: > b1.uberns.com > a1.uberns.com > >> if your customers don't see what your cache server does, they cant be using >> the same cache server as you showed here > > true > > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users [2] to > unsubscribe from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users [2] Links: ------ [1] http://www.intodns.com/losscontrol360.com [2] https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
