Lulupard
By:
Lulupard

Zone file not updating after 2 hours

August 30, 2014 4.1k views

How long does it take for the zone file to update? I've changed my MX records 2 hours ago and still nothing.

4 Answers

I am having the same issue here. I would give it at least 24hrs before putting in a support ticket. Some times things just run a little slower than they usually do. I am sure it will update within the 24hr period.

Something is wrong with the MX records too, can't verify them with google apps, every NS server keeps reporting different MX values.

Are you guys still having trouble? I added a new domain via the Control Panel over 7 hours ago, and I still can't get an answer from ns1.digitalocean.com when I run dig. I'm wondering if something is broken.

  • I'm wondering if its the same problem I'm having.

  • Same to me. If I do a whois I see the digitalocean name servers:

       Name Server: NS1.DIGITALOCEAN.COM
       Name Server: NS2.DIGITALOCEAN.COM
       Name Server: NS3.DIGITALOCEAN.COM
    

    However, I get a SERVFAIL when doing a dig:

    ; <<>> DiG 9.9.5-3-Ubuntu <<>> esplailagrapadora.com
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 17518
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 512
    ;; QUESTION SECTION:
    ;esplailagrapadora.com.     IN  A
    

    And a refused:

    root@juanramon-01:~# dig -t NS esplailagrapadora.com @ns1.digitalocean.com
    
    ; <<>> DiG 9.9.5-3-Ubuntu <<>> -t NS esplailagrapadora.com @ns1.digitalocean.com
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 15453
    ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
    ;; WARNING: recursion requested but not available
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;esplailagrapadora.com.     IN  NS
    
    ;; Query time: 3 msec
    ;; SERVER: 173.245.58.51#53(173.245.58.51)
    ;; WHEN: Sun Aug 31 23:04:38 CEST 2014
    ;; MSG SIZE  rcvd: 50
    
  • How long ago did you make your DNS change?

  • My change finally went through about 10 hours later. I now get an answer for my domain with dig @ns1.digitalocean.com. It looks like yours is working now too, juanramon.

  • Yes! Maybe it took longer than usual to propagate.

I have changed MX records to google's 12 hours ago. Still nothing.

Have another answer? Share your knowledge.