Page 2 of 3 FirstFirst 123 LastLast
Results 26 to 50 of 66
  1. #26
    Join Date
    Jul 2003
    Location
    NC
    Posts
    270
    Yes. The mentioned domain is resolving correctly now.

  2. #27
    Join Date
    Feb 2005
    Posts
    299
    No, the issue is not resolved.

    I have asked GoDaddy to delete this blank zone which is an error anyway, regardless if it is the source of my DNS problem or not. They reply to me always like this:

    We have confirmed via internal as well as third party DNS tools that the nameservers set for the domain in question are as follows:

    * NS14.ZONEEDIT.COM
    * NS19.ZONEEDIT.COM

    These are not Go Daddy controld nameservers.

    If you would like to have control over this domain's DNS, refer to the following:

    To modify your domain name's name server settings to 'park' your domain name

    • Select 'Domain Manager' from the 'My Products' menu located on the left hand side of the page.
    • Check the box next to the domain(s) you wish to modify.
    • Click 'Nameservers' from the menu above.
    • Click the circle next to 'I want to Park or Forward my domains'.
    • Click 'Ok' to save changes.
    • Allow 48 hours for the changes to take effect*.
    They are ignoring my request to delete this blank zone, hell they won't even acknowledge it is there via email.

    Zoneedit who manage my DNS reply to me like this:

    Hello,

    that would not be a problem on our side

  3. #28
    Join Date
    Mar 2009
    Location
    deep blue yonder
    Posts
    176
    Quote Originally Posted by zymic View Post
    No, the issue is not resolved.
    Well... that's what I thought, but I wasn't sure if you were happy or not.
    Quote Originally Posted by zymic View Post
    I have asked GoDaddy to delete this blank zone which is an error anyway, regardless if it is the source of my DNS problem or not. They reply to me always like this:
    Quote Originally Posted by GoDaddy
    We have confirmed via internal as well as third party DNS tools that the nameservers set for the domain in question are as follows:
    [snip]
    They are ignoring my request to delete this blank zone, hell they won't even acknowledge it is there via email.
    All I can suggest is that you keep the ticket open and if they continue to ignore the bogus host problem, keep reminding them about it and asking them to escalate the ticket. At some point, someone senior at GoDaddy who understands how DNS resolution works, needs to become involved.
    Quote Originally Posted by zymic View Post
    Zoneedit who manage my DNS reply to me like this:
    Quote Originally Posted by ZoneEdit
    Hello,

    that would not be a problem on our side
    I would agree with Zoneedit.
    424 bits were harmed in the making of this signature.

  4. #29
    Join Date
    Feb 2005
    Posts
    299
    Top admin firm tells me this:

    The problem is at godaddy->parent servers (not ZoneEdit). ZoneEdit are returning the correct entries for your nameservers but the root dns servers are being fed the A record 72.232.162.50 rather than referring you to ZoneEdit.

    You can see this at,

    # dig A zymic.com @D.GTLD-SERVERS.NET

    ; <> DiG 9.3.4-P1 <> A zymic.com @D.GTLD-SERVERS.NET
    ; (1 server found)
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16020
    ;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

    ;; QUESTION SECTION:
    ;zymic.com. IN A

    ;; ANSWER SECTION:
    zymic.com. 172800 IN A 72.232.162.50

    ;; AUTHORITY SECTION:
    zymic.com. 172800 IN NS ns14.zoneedit.com.
    zymic.com. 172800 IN NS ns19.zoneedit.com.

    ;; ADDITIONAL SECTION:
    ns14.zoneedit.com. 172800 IN A 209.126.137.108
    ns19.zoneedit.com. 172800 IN A 216.227.210.10


    The reason the www. entry works is because they are not returning the record, they are referring you properly,

    ]# dig A www.zymic.com @D.GTLD-SERVERS.NET

    ; <> DiG 9.3.4-P1 <> A www.zymic.com @D.GTLD-SERVERS.NET
    ; (1 server found)
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5091
    ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2

    ;; QUESTION SECTION:
    ;www.zymic.com. IN A

    ;; AUTHORITY SECTION:
    zymic.com. 172800 IN NS ns14.zoneedit.com.
    zymic.com. 172800 IN NS ns19.zoneedit.com.
    Conclusion: it is Godaddy.

  5. #30
    Join Date
    Feb 2005
    Posts
    299
    Oh my word, they have confirmed the blank host name issue is the cause of the problem! But wait, they ask ME to delete it! I can't delete it or do anything to it, it is a bug as explained and demonstrated on my first post backed up with a video.

    Dear Jack,

    Thank you for contacting Online Support. I apologize for the previous responses and frustration regarding this issue. Upon review of the domain name it appears that you have configured a custom nameserver in the host summary of the domain and this is showing a blank nameserver entry and it is pointed to the IP address that you have specified. That being said, it is most likely that this is what is causing the issue and you will need to delete this nameserver using the instructions below and then allow up to 48 hours for this to propagate.
    To Delete Custom Nameserver Entries:


    1. Log in to your Account Manager.

    2. In the My Products section, click Domain Manager.

    3. Click the domain for which you want to create a host.

    4. In the Host Summary section, click the delete hyperlink next to the blank entry.

    5. Click OK.

    Arghhhh!!!!!!!

  6. #31
    Join Date
    Jun 2001
    Location
    Cheltenham
    Posts
    2,618
    Think of it this way - at least you have progress!
    l 201TB.com • 201TB bandwidth as standard in three USA DC’s. KVMoIP, auto reboot & OS install all included - Now available in the Netherlands!
    l udedi.com • UK, USA & NL unmetered 100mb & 1GB 100TB premium bandwidth servers
    l Assiva Ltd • UK Shared & Reseller LiteSpeed • 10 years of hosting • R1Soft

  7. #32
    Join Date
    Feb 2005
    Posts
    299
    And to top this off ZoneEdit have randomly emailed me this:

    Response 10/28/2009 10:59 AM
    i have reset the DNS on that zone please allow at least 1 hour for it to update
    What is happening *_* now ZoneEdit are taking action when the problem is now confirmed as Godaddy. This just gets worse! I hope reset does not mean delete.

    What a mess this is now.

  8. #33
    Join Date
    Mar 2009
    Location
    deep blue yonder
    Posts
    176
    Quote Originally Posted by zymic View Post
    Arghhhh!!!!!!!
    Never give up... Especially when chasing your tail.
    424 bits were harmed in the making of this signature.

  9. #34
    Join Date
    Jun 2001
    Location
    Cheltenham
    Posts
    2,618
    its perhaps a touch extreme, but you could migrate your domain away from godaddy. it would certainly solve any godaddy problems!
    l 201TB.com • 201TB bandwidth as standard in three USA DC’s. KVMoIP, auto reboot & OS install all included - Now available in the Netherlands!
    l udedi.com • UK, USA & NL unmetered 100mb & 1GB 100TB premium bandwidth servers
    l Assiva Ltd • UK Shared & Reseller LiteSpeed • 10 years of hosting • R1Soft

  10. #35
    Join Date
    Jul 2003
    Location
    NC
    Posts
    270
    Your domains are resolving just fine, both host and www. I've checked the resource records (with dig +trace), they are fine.

    What you are experiencing right now is an effect of your ISP caching DNS (and also your OS/browser). That and the typical propagation time. Check back in a few hours.
    Last edited by TowerOfPower; 10-28-2009 at 02:23 PM.

  11. #36
    Join Date
    Jul 2003
    Location
    NC
    Posts
    270
    This has nothing to do with godaddy. It was old records with zoneedit. How many time can one say this? Does anyone else here understand how DNS resolution is done and what nameservers are? Or am I in a dream?

    The only other possibility is that the DNS system is broken.
    Last edited by TowerOfPower; 10-28-2009 at 02:23 PM.

  12. #37
    Join Date
    Jul 2003
    Location
    NC
    Posts
    270
    Code:
    [root@ ~]# dig ANY zymic.com @ns14.zoneedit.com
    
    ; <<>> DiG 9.2.4 <<>> ANY zymic.com @ns14.zoneedit.com
    ; (1 server found)
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58739
    ;; flags: qr aa rd; QUERY: 1, ANSWER: 6, AUTHORITY: 2, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;zymic.com.                     IN      ANY
    
    ;; ANSWER SECTION:
    zymic.com.              7200    IN      A       216.18.194.242
    zymic.com.              7200    IN      NS      ns14.zoneedit.com.
    zymic.com.              7200    IN      NS      ns19.zoneedit.com.
    zymic.com.              7200    IN      SOA     ns14.zoneedit.com. soacontact.zoneedit.com. 1089847035 14400 7200 950400 7200
    zymic.com.              7200    IN      MX      0 ASPMX.L.GOOGLE.com.
    zymic.com.              7200    IN      TXT     "v=spf1 a ~all"
    
    ;; AUTHORITY SECTION:
    zymic.com.              7200    IN      NS      ns14.zoneedit.com.
    zymic.com.              7200    IN      NS      ns19.zoneedit.com.
    
    ;; Query time: 14 msec
    ;; SERVER: 209.126.137.108#53(209.126.137.108)
    ;; WHEN: Wed Oct 28 14:24:43 2009
    ;; MSG SIZE  rcvd: 222
    Last edited by TowerOfPower; 10-28-2009 at 02:25 PM.

  13. #38
    Join Date
    Jul 2003
    Location
    NC
    Posts
    270
    Quote Originally Posted by zymic View Post
    Top admin firm tells me this:



    Conclusion: it is Godaddy.
    Get a better firm.

    Code:
    [root@*** ~]# dig A zymic.com @ns14.zoneedit.com
    
    ; <<>> DiG 9.2.4 <<>> A zymic.com @ns14.zoneedit.com
    ; (1 server found)
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29020
    ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;zymic.com.                     IN      A
    
    ;; ANSWER SECTION:
    zymic.com.              7200    IN      A       216.18.194.242
    
    ;; AUTHORITY SECTION:
    zymic.com.              7200    IN      NS      ns14.zoneedit.com.
    zymic.com.              7200    IN      NS      ns19.zoneedit.com.
    
    ;; Query time: 15 msec
    ;; SERVER: 209.126.137.108#53(209.126.137.108)
    ;; WHEN: Wed Oct 28 14:27:23 2009
    ;; MSG SIZE  rcvd: 90
    All you had to do was go into your zoneedit account and set the A record for host.
    Last edited by TowerOfPower; 10-28-2009 at 02:28 PM.

  14. #39
    Join Date
    Mar 2009
    Location
    deep blue yonder
    Posts
    176
    Quote Originally Posted by TowerOfPower View Post
    This has nothing to do with godaddy. It was old records with zoneedit. How many time can one say this? Does anyone else here understand how DNS resolution is done and what nameservers are? Or am I in a dream?
    Nope.

    I think you are misunderstanding the nature of the problem. The problem is not with the A record associated with the www host entry, but rather with the A record associated with the domain itself:
    Code:
    $ dig -ta zymic.com @L.GTLD-SERVERS.NET.
    
    ; <<>> DiG 9.4.2-P2 <<>> -ta zymic.com @L.GTLD-SERVERS.NET.
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40104
    ;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
    ;; WARNING: recursion requested but not available
    
    ;; QUESTION SECTION:
    ;zymic.com.                     IN      A
    
    ;; ANSWER SECTION:
    zymic.com.              172800  IN      A       72.232.162.50
    
    ;; AUTHORITY SECTION:
    zymic.com.              172800  IN      NS      ns14.zoneedit.com.
    zymic.com.              172800  IN      NS      ns19.zoneedit.com.
    
    ;; ADDITIONAL SECTION:
    ns14.zoneedit.com.      172800  IN      A       209.126.137.108
    ns19.zoneedit.com.      172800  IN      A       216.227.210.10
    424 bits were harmed in the making of this signature.

  15. #40
    Join Date
    Feb 2005
    Posts
    299
    TowerOfPower, it is not a problem with ZoneEdit, nor will your solution work because the A record is correct in ZoneEdit anyway. Godaddy have confirmed it is a problem with them, as explained in this thread; I do not think you understand. Or I may be missing something.

    Thanks

  16. #41
    Join Date
    Jul 2003
    Location
    NC
    Posts
    270
    I've corrected the above post... To the host... Which is resolving correctly by the nameservers it's been assigned. You're getting stale results.

    And if it's a problem, why am I getting good results for host and www in browser, with dig, and right from the zoneedit servers? Yesterday, I was getting bad results.

  17. #42
    Join Date
    Feb 2005
    Posts
    299
    TowerOfPower, it has loaded fine for me on my home connection, many users do not experience the problem. It is only a small amount of users who see the incorrect IP.

    Do you want access to my Windows server to see some proof? As the problem occurs for this server.

    Please refer to TDS's post which reiterates the problem which is with Godaddy.
    Last edited by zymic; 10-28-2009 at 02:38 PM.

  18. #43
    Join Date
    Jul 2003
    Location
    NC
    Posts
    270
    Quote Originally Posted by zymic View Post
    TowerOfPower, it has loaded fine for me on my home connection, many users do not experience the problem. It is only a small amount of users who see the incorrect IP.

    Do you want access to my Windows server to see some proof? As the problem occurs for this server.
    It takes time for the root dns servers to update their records and even more time for ISPs to flush their cache. Your zoneedit nameservers where the problem, records needed to be updated to the correct IP, they were updated; now the system is propagating the changes.

    This is a simple issue that has been blown way out of proportion.

  19. #44
    Join Date
    Jan 2005
    Location
    Scotland, UK
    Posts
    2,681
    Quote Originally Posted by TowerOfPower View Post
    Get a better firm.

    Code:
    [root@*** ~]# dig A zymic.com @ns14.zoneedit.com
    
    ; <<>> DiG 9.2.4 <<>> A zymic.com @ns14.zoneedit.com
    ; (1 server found)
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29020
    ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;zymic.com.                     IN      A
    
    ;; ANSWER SECTION:
    zymic.com.              7200    IN      A       216.18.194.242
    
    ;; AUTHORITY SECTION:
    zymic.com.              7200    IN      NS      ns14.zoneedit.com.
    zymic.com.              7200    IN      NS      ns19.zoneedit.com.
    
    ;; Query time: 15 msec
    ;; SERVER: 209.126.137.108#53(209.126.137.108)
    ;; WHEN: Wed Oct 28 14:27:23 2009
    ;; MSG SIZE  rcvd: 90
    All you had to do was go into your zoneedit account and set the A record for host.
    You are wrong, end of discussion.

    ####

    Quote Originally Posted by zymic View Post
    TowerOfPower, it has loaded fine for me on my home connection, many users do not experience the problem. It is only a small amount of users who see the incorrect IP.

    Do you want access to my Windows server to see some proof? As the problem occurs for this server.
    Why would you need to give proof to someone? Especially someone who is wrong

    The bottom line is godaddy is announcing the IP to the root zones instead of the redirect to zoneedit. They have acknowledged this and have provided instructions to correct this, if the instructions do not work continue on with them to get them to manually adjust it.

    People will get different results based on their resolvers and in turn the software their resolvers are running.

    #####

    You can see this at,

    # dig A zymic.com @D.GTLD-SERVERS.NET

    ; <> DiG 9.3.4-P1 <> A zymic.com @D.GTLD-SERVERS.NET
    ; (1 server found)
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16020
    ;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

    ;; QUESTION SECTION:
    ;zymic.com. IN A

    ;; ANSWER SECTION:
    zymic.com. 172800 IN A 72.232.162.50

    ;; AUTHORITY SECTION:
    zymic.com. 172800 IN NS ns14.zoneedit.com.
    zymic.com. 172800 IN NS ns19.zoneedit.com.

    ;; ADDITIONAL SECTION:
    ns14.zoneedit.com. 172800 IN A 209.126.137.108
    ns19.zoneedit.com. 172800 IN A 216.227.210.10


    The reason the www. entry works is because they are not returning the record, they are referring you properly,

    ]# dig A www.zymic.com @D.GTLD-SERVERS.NET

    ; <> DiG 9.3.4-P1 <> A www.zymic.com @D.GTLD-SERVERS.NET
    ; (1 server found)
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5091
    ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2

    ;; QUESTION SECTION:
    ;www.zymic.com. IN A

    ;; AUTHORITY SECTION:
    zymic.com. 172800 IN NS ns14.zoneedit.com.
    zymic.com. 172800 IN NS ns19.zoneedit.com.
    Shows the problem.

  20. #45
    Join Date
    Jul 2003
    Location
    NC
    Posts
    270
    What it shows is that it takes time for changes in ns14.zoneedit and ns19.zoneedit to propagate to the root servers.

  21. #46
    Join Date
    Jan 2005
    Location
    Scotland, UK
    Posts
    2,681
    Quote Originally Posted by TowerOfPower View Post
    What it shows is that it takes time for changes in ns14.zoneedit and ns19.zoneedit to propagate to the root servers.
    If you actually bothered to query the root servers you would see they are the ones answering the request, not zoneedit. Godaddy have even acknowledge this.

    dig A zymic.com @D.GTLD-SERVERS.NET
    dig A www.zymic.com @D.GTLD-SERVERS.NET

    Look for yourself.

  22. #47
    Join Date
    Jul 2003
    Location
    NC
    Posts
    270
    A TTL=172800 is 2 Days.

  23. #48
    Join Date
    Jul 2003
    Location
    NC
    Posts
    270
    Quote Originally Posted by Scott.Mc View Post
    If you actually bothered to query the root servers you would see they are the ones answering the request, not zoneedit. Godaddy have even acknowledge this.

    dig A zymic.com @D.GTLD-SERVERS.NET
    dig A www.zymic.com @D.GTLD-SERVERS.NET

    Look for yourself.

    I'm open to suggestions and 3rd party interpretations.

  24. #49
    Join Date
    Jun 2001
    Location
    Cheltenham
    Posts
    2,618
    guys - no need to scrap.
    l 201TB.com • 201TB bandwidth as standard in three USA DC’s. KVMoIP, auto reboot & OS install all included - Now available in the Netherlands!
    l udedi.com • UK, USA & NL unmetered 100mb & 1GB 100TB premium bandwidth servers
    l Assiva Ltd • UK Shared & Reseller LiteSpeed • 10 years of hosting • R1Soft

  25. #50
    Join Date
    Jul 2003
    Location
    NC
    Posts
    270
    I've been looking over this thread again and again, and this is what I'm getting from the other side...

    That it's possible for GoDaddy to register outside nameservers for a domain.tld, and yet also, *at the same time*, magically assign and pipe an A resource record using its own host records for the base domain ... right into the root dns system.

    Can someone explain this to me? Is this even technically feasible (that is, without those nameservers delegating back)?
    Last edited by TowerOfPower; 10-28-2009 at 04:11 PM.

Page 2 of 3 FirstFirst 123 LastLast

Similar Threads

  1. breaking news: emergency landing/MD80 with problem nose gear
    By Techno in forum Web Hosting Lounge
    Replies: 5
    Last Post: 02-22-2008, 04:45 PM
  2. SSL -- Problem, Emergency!
    By eComputer2001 in forum Hosting Security and Technology
    Replies: 6
    Last Post: 04-25-2007, 09:54 PM
  3. Emergency!
    By REVCOM-Lawrence in forum Hosting Security and Technology
    Replies: 4
    Last Post: 08-18-2006, 09:52 AM
  4. EMERGENCY Webmail Horde Problem
    By darkstar757 in forum Hosting Security and Technology
    Replies: 4
    Last Post: 10-10-2004, 07:49 PM
  5. cPanel IP & Apache Problem *EMERGENCY
    By acompw in forum Hosting Software and Control Panels
    Replies: 11
    Last Post: 06-20-2004, 01:46 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •