Dns problems?

Discussion in 'Installation/Configuration' started by fordwrench, May 9, 2007.

  1. fordwrench

    fordwrench Member HowtoForge Supporter

    When I dig at my primary nameserver I get the following:

    ; <<>> DiG 9.3.4 <<>> @ns1.50hq.com aol.com
    ; (1 server found)
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57816
    ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 0

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

    ;; AUTHORITY SECTION:
    . 518400 IN NS L.ROOT-SERVERS.NET.
    . 518400 IN NS M.ROOT-SERVERS.NET.
    . 518400 IN NS A.ROOT-SERVERS.NET.
    . 518400 IN NS B.ROOT-SERVERS.NET.
    . 518400 IN NS C.ROOT-SERVERS.NET.
    . 518400 IN NS D.ROOT-SERVERS.NET.
    . 518400 IN NS E.ROOT-SERVERS.NET.
    . 518400 IN NS F.ROOT-SERVERS.NET.
    . 518400 IN NS G.ROOT-SERVERS.NET.
    . 518400 IN NS H.ROOT-SERVERS.NET.
    . 518400 IN NS I.ROOT-SERVERS.NET.
    . 518400 IN NS J.ROOT-SERVERS.NET.
    . 518400 IN NS K.ROOT-SERVERS.NET.

    ;; Query time: 9 msec
    ;; SERVER: 76.201.116.225#53(76.201.116.225)
    ;; WHEN: Wed May 9 00:12:13 2007
    ;; MSG SIZE rcvd: 236


    Any Ideas what might be my problem?

    Fordwrench
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    This means that there is no authoritive nameserver for this domain. Please post the exact dig command that you used. Did you create the DNS-Record in the ISPConfig DNS-Manager on this server.
     
  3. fordwrench

    fordwrench Member HowtoForge Supporter

    The command I used was:

    dig @76.201.116.225 aol.com

    76.201.116.225 is my Primary Nameserver (ns1.50hq.com)
    76.201.116.226 is my Secondary Nameserver(ns1.50hq.com)

    This is the output when I dig the secondary nameserver:

    srv1:~# dig @76.201.116.226 aol.com

    ; <<>> DiG 9.3.4 <<>> @76.201.116.226 aol.com
    ; (1 server found)
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37590
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 0

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

    ;; ANSWER SECTION:
    aol.com. 60 IN A 64.12.50.151
    aol.com. 60 IN A 205.188.142.182

    ;; AUTHORITY SECTION:
    aol.com. 3600 IN NS dns-01.ns.aol.com.
    aol.com. 3600 IN NS dns-02.ns.aol.com.
    aol.com. 3600 IN NS dns-06.ns.aol.com.
    aol.com. 3600 IN NS dns-07.ns.aol.com.

    ;; Query time: 210 msec
    ;; SERVER: 76.201.116.226#53(76.201.116.226)
    ;; WHEN: Wed May 9 12:17:20 2007
    ;; MSG SIZE rcvd: 144

    Did I create the DNS-Record? Not sure which record you are referring to.

    Fordwrench
     
    Last edited: May 9, 2007
  4. falko

    falko Super Moderator Howtoforge Staff

    If 76.201.116.225 is your own nameserver, then you've sucessfully created DNS records for aol.com (not sure though why you want to do this...).
     
  5. fordwrench

    fordwrench Member HowtoForge Supporter

    I have not created any records for aol.com in my dns.
    I have only created records for my own sites.


    When I dig at a local site it displays the info properly.
    Should I not be able to dig any fqdn and get the proper info from my dns servers? I am just not sure about this.

    I have learned a lot from your site and am continuing to learn. I want to make sure my setup is correct. Most of the howto's are real informative about showing you how to do some particular task or setup although it may not explain why you do something a particular way. That is what helps me learn, to not only know how but why?

    Now from what I gather my nameservers are not authoritive or authoritative, Not sure which is which since I have seen it spelled both ways so many times reading through the forums. How to I make this setup right?


    Thanks
    Fordwrench
     
  6. falko

    falko Super Moderator Howtoforge Staff

    Yes, that's right.

    Normally your domain registrar should have a web interface where you can set your nameservers as the authoritative nameservers for your domains. Take a look here: http://www.howtoforge.com/ispconfig_dns_godaddy
    http://www.howtoforge.com/ispconfig_dns_providerdomain_schlund
     
  7. fordwrench

    fordwrench Member HowtoForge Supporter

    Again, Thanks for the help.
    I followed the Godaddy howto and still I have this problem.

    I ssh into srv1.50hq.com (www-server).

    I type : dig @ns1.50hq.com aol.com and I get:

    srv1:~# dig @ns1.50hq.com aol.com

    ; <<>> DiG 9.3.4 <<>> @ns1.50hq.com aol.com
    ; (1 server found)
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14869
    ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 0

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

    ;; AUTHORITY SECTION:
    . 518400 IN NS J.ROOT-SERVERS.NET.
    . 518400 IN NS K.ROOT-SERVERS.NET.
    . 518400 IN NS L.ROOT-SERVERS.NET.
    . 518400 IN NS M.ROOT-SERVERS.NET.
    . 518400 IN NS A.ROOT-SERVERS.NET.
    . 518400 IN NS B.ROOT-SERVERS.NET.
    . 518400 IN NS C.ROOT-SERVERS.NET.
    . 518400 IN NS D.ROOT-SERVERS.NET.
    . 518400 IN NS E.ROOT-SERVERS.NET.
    . 518400 IN NS F.ROOT-SERVERS.NET.
    . 518400 IN NS G.ROOT-SERVERS.NET.
    . 518400 IN NS H.ROOT-SERVERS.NET.
    . 518400 IN NS I.ROOT-SERVERS.NET.

    ;; Query time: 9 msec
    ;; SERVER: 76.201.116.225#53(76.201.116.225)
    ;; WHEN: Fri May 11 15:04:30 2007
    ;; MSG SIZE rcvd: 236


    Now, If I ssh into ns1.50hq.com and issue the following command:
    dig @ns1.50hq.com aol.com
    I get the following:

    ns1:~# dig @ns1.50hq.com aol.com

    ; <<>> DiG 9.3.4 <<>> @ns1.50hq.com aol.com
    ; (1 server found)
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53637
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 0

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

    ;; ANSWER SECTION:
    aol.com. 60 IN A 64.12.50.151
    aol.com. 60 IN A 205.188.142.182

    ;; AUTHORITY SECTION:
    aol.com. 3600 IN NS dns-01.ns.aol.com.
    aol.com. 3600 IN NS dns-02.ns.aol.com.
    aol.com. 3600 IN NS dns-06.ns.aol.com.
    aol.com. 3600 IN NS dns-07.ns.aol.com.

    ;; Query time: 310 msec
    ;; SERVER: 76.201.116.225#53(76.201.116.225)
    ;; WHEN: Fri May 11 15:06:45 2007
    ;; MSG SIZE rcvd: 144

    Then if I go back to srv1.50hq.com and issue the following command:

    dig @ns1.50hq.com aol.com

    I get the following:

    srv1:~# dig @ns1.50hq.com aol.com

    ; <<>> DiG 9.3.4 <<>> @ns1.50hq.com aol.com
    ; (1 server found)
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 242
    ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 0

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

    ;; AUTHORITY SECTION:
    aol.com. 3532 IN NS dns-07.ns.aol.com.
    aol.com. 3532 IN NS dns-01.ns.aol.com.
    aol.com. 3532 IN NS dns-02.ns.aol.com.
    aol.com. 3532 IN NS dns-06.ns.aol.com.

    ;; Query time: 3 msec
    ;; SERVER: 76.201.116.225#53(76.201.116.225)
    ;; WHEN: Fri May 11 15:07:53 2007
    ;; MSG SIZE rcvd: 112

    What could, or is causing this to happen?
    Is it proper behavior?

    Fordwrench
     
  8. falko

    falko Super Moderator Howtoforge Staff

    Did you open port 53 (TCP and UDP) on ns1.50hq.com?

    What's in /etc/resolv.conf on both servers?
     
  9. fordwrench

    fordwrench Member HowtoForge Supporter

    Port 53 is Open on all servers.


    resolv.conf for ns1.50hq.com

    ns1:/etc# cat resolv.conf
    search 50hq.com
    nameserver 68.94.156.1
    nameserver 68.94.157.1
    #nameserver 208.109.78.91
    #nameserver 208.109.138.91

    resolv.conf for ns2.50hq.com

    ns2:/etc# cat resolv.conf
    search 50hq.com
    nameserver 68.94.156.1
    nameserver 68.94.157.1

    resolv.conf for srv1.50hq.com

    srv1:/etc# cat resolv.conf
    search 50hq.com
    nameserver 68.94.156.1
    nameserver 68.94.157.1

    Fordwrench
     
  10. falko

    falko Super Moderator Howtoforge Staff

    Hm, resolv.conf contains identical nameservers on all servers, so that doesn't seem to be the problem... :confused:
     

Share This Page