DNS Issue - Help Please
 

http://www.xxxsextube.club/

I have name servers set correctly and Registrar confirms this.

Host says:
"They need to clear the domain name cache on their servers"

I've never heard about a Registrar needing to clear a domain cache before. Wtf!?

Can someone please kindly lmk to whom it is that I should be taking a crap on, please and thanks.

I've never heard of that either. Tried running your domain through IntoDNS but apparently it doesn't like the .club extension.

Wow, I haven't heard those words since the 90s.

I believe your host is referring to propagation. Unless, you're dealing with some lost tribe in the Amazon jungle, propagation should take a few hours globally.

It's a SERVFAIl status, likely caused by no IP assigned to it (yet). A DIG for it shows an "A" record with no IP assigned to it. Thus, it's generating a SERVFAIL response.

dig xxxsextube.club

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.37.rc1.el6_7.6 <<>> xxxsextube.club
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 32438
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;xxxsextube.club. IN A IP.SHOULD.BE.HERE

;; Query time: 278 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Apr 26 13:42:42 2016
;; MSG SIZE rcvd: 33

I'm of the mind that it has something to do with the .club extension, but what that is I dunno.

I set name servers 10? days ago. Yeah, rare that it takes more than a couple of hours to propagate.

Would this be an issue with server or Registrar? I'm inclined to think server, but I'm being asked to run this in linux (like I have some magical way of accessing Registrar's server) dig -t ns xxxsextube.club

Thanks for your help, it is appreciated.

It's the Host, as I figured all along.

Thanks for looking people.

It's not the host. You need to contact your registrar because even though you've set your nameservers to the correct one. When you run this command in linux if you have access to a server (not your registrars server) you can see the nameservers flip flopping or just not existing at all:
dig -t ns xxxsextube.club

That will give you a response for what your nameservers are set to at your registrar level. If those are not consistent then there are deeper issues that only the registar can fix for you.

I switched name servers to another Host and site was live in under 5 minutes; however, that is not the Host I need it to point to.

I'll send this to Registrar, thank-you for taking the time to help.

Your name servers are not set up right.

Or not propagated yet?
it can take 24 to as long as 48 hours if it is a new domain and not an update

Professional Toolset | DNSstuff

I triple checked name servers. For you, I checked again and they are correct. Name servers were pointed 10? days ago.

If I point them to my own servers name servers, I have a live site in 5 minutes.

I fail to see how this is a Registrar issue, yet tech is telling me that it is indeed on their end?!

I'm stumped...

Email admin at way3 dot Com and tell him someone sent you and he thought way3 would be able to determine your issue quickly. The guys name is Chris and he's a server and dns guru.

Then consider switching hosting companies and I recommend him, as he has saved me so many thousands of dollars over the years.

At DNSstuff . com

are there the current name servers listed correctly?
TTL=7200 should not be a long cache

WHO? :1orglaugh
and 2

What does that mean? His DNS is wrong, is hacked, is shaddy??

It shouldn't - I have a bunch of .club, .xyz, .online, etc... on various dns hosting sites (cloudflare, google domain dns, namecheap, godaddy, etc) and it works just fine.

I moved the majority of my dns stuff to Cloudflare (when you add your site just click on the cloud icons so they turn gray and that way you can just use Cloudflare's free dns and not all their other stuff) since their free dns hosting is fast as hell and stable.

It means that server [TRINITYTCP] has no/or cannot read the domain's zone file.

I have no idea why.

Remake the zone file on that DNS name server, [TRINITYTCP], so it is the correct one
Or, move the DNS servers to another and propagate.
The Registrar cannot set a zone where none exists.

1. Set the zone on your DNS server FIRST
2. only then, if the Registrar is able to find the domain's new zone on that DNS server, will the Registrar successfully update the zone in the root servers -- that is the ''Law of ICANN -- the Internet Gods''
3. The registrar will fail to change the DNS if its servers cannot locate the zone file.

This is not my host. Hosted situation where I have no control over server.

Probably not that. It was the only difference that I could see.

I have no idea why either, but I'll send this to the tech people, thank-you.