DNS won't resolve.

Discussion in 'Installation/Configuration' started by jamesl22, Oct 28, 2011.

  1. jamesl22

    jamesl22 New Member

    I have set up a dns record with ISPConfig that looks like this:

    [​IMG]

    However; if i run "dig jsearched.co.uk" I get this:
    Code:
    root@ns1:~# dig jsearched.co.uk
    
    ; <<>> DiG 9.7.3 <<>> jsearched.co.uk
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 7866
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;jsearched.co.uk.               IN      A
    
    ;; Query time: 98 msec
    ;; SERVER: 8.8.8.8#53(8.8.8.8)
    ;; WHEN: Fri Oct 28 21:36:54 2011
    ;; MSG SIZE  rcvd: 33
    
    
    /var/log/syslog reads:
    Code:
    Oct 28 21:30:15 ns1 named[24516]: lame server resolving 'jsearched.co.uk' (in 'jsearched.co.uk'?): 92.24.6.206#53
    
    What is wrong?

    Regards,

    James
     

    Attached Files:

  2. Toucan

    Toucan New Member

    It looks like it's because your name servers are set to:
    ns2.sitemamba.com. ['92.24.6.206']
    ns1.sitemamba.com. ['92.24.6.206']

    http://www.intodns.com/jsearched.co.uk

    That means the world is looking to those two servers to get DNS records - so you can make what ever DNS records you want on your server but it won't makee any difference if everyone else is looking to those two name servers for the records.

    Have you made name server records for your server to use?
    On your registrar's control panel make ns records for ns1.yourserver.com and ns2.yourserver.com.

    Then again on the registrar;s control panel change the name servers for jsearched.co.uk to the two records you just made previously.

    Leave it to propogate and hopefully problem solved.
     
  3. jamesl22

    jamesl22 New Member

    Thanks for the reply.

    Those are my nameservers and that is the IP of them. But why is the lookup failing?
     
  4. falko

    falko Super Moderator

  5. jamesl22

    jamesl22 New Member

    Netstat -tab gives:
    Code:
    root@ns1:~# netstat -tap
    Active Internet connections (servers and established)
    Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
    tcp        0      0 ns1.lovejoy.loca:domain *:*                     LISTEN      24516/named
    tcp        0      0 localhost:domain        *:*                     LISTEN      24516/named
    tcp        0      0 *:ssh                   *:*                     LISTEN      3992/sshd
    tcp        0      0 localhost:953           *:*                     LISTEN      24516/named
    tcp        0      0 localhost:mysql         *:*                     LISTEN      5483/mysqld
    tcp        0      0 ns1.lovejoy.local:ssh   192.168.1.6:53229       ESTABLISHED 12478/0
    tcp        0      0 ns1.lovejoy.local:47901 web.lovejoy.local:mysql TIME_WAIT   -
    tcp6       0      0 [::]:domain             [::]:*                  LISTEN      24516/named
    tcp6       0      0 [::]:ssh                [::]:*                  LISTEN      3992/sshd
    tcp6       0      0 localhost:953           [::]:*                  LISTEN      24516/named
    tcp6       0      0 localhost:59795         localhost:domain        TIME_WAIT   -
    
    Bind gives no error on restart.
     
  6. falko

    falko Super Moderator

    Is 92.24.6.206 your system's IP address? What are the outputs of
    Code:
    ifconfig 
    and
    Code:
    iptables -L
    ?
     
  7. jamesl22

    jamesl22 New Member

    Yes, that is my IP.

    Code:
    root@ns1:~# ifconfig
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:6676 errors:0 dropped:0 overruns:0 frame:0
              TX packets:6676 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:505129 (493.2 KiB)  TX bytes:505129 (493.2 KiB)
    
    venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
              inet addr:127.0.0.1  P-t-P:127.0.0.1  Bcast:0.0.0.0  Mask:255.255.255.255
              UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
              RX packets:283596 errors:0 dropped:0 overruns:0 frame:0
              TX packets:256780 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:129450746 (123.4 MiB)  TX bytes:37199981 (35.4 MiB)
    
    venet0:0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
              inet addr:192.168.1.105  P-t-P:192.168.1.105  Bcast:0.0.0.0  Mask:255.255.255.255
              UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
    
    
    Code:
    root@ns1:~# iptables -L
    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination
    fail2ban-ssh  tcp  --  anywhere             anywhere            FATAL: Could not load /lib/modules/2.6.32-5-openvz-686/modules.dep: No such file or directory
    multiport dports ssh
    
    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination
    
    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination
    
    Chain fail2ban-ssh (1 references)
    target     prot opt source               destination
    RETURN     all  --  anywhere             anywhere
    
     
  8. falko

    falko Super Moderator

    You're behind a router, right? Does your router forward port 53 (TCP and UDP!) to your server?
     
  9. jamesl22

    jamesl22 New Member

    Both are port forwarded. I can't even get it to resolve @localhost ?
     
  10. edge

    edge HowtoForge Supporter

    Does TalkTalk (your ISP) have port 53 open?
     
  11. jamesl22

    jamesl22 New Member

    Its a business account. Nothing is blocked. But its not that the server cannot be reached from outside. It cannot be reached from localhost.
     
  12. jamesl22

    jamesl22 New Member

    Um... I fixed it... somehow!?! Thanks for the help but the problem seems to have fixed itself. Rebooting the servers and the account then recreating it with the dns zone appears to have fixed it.
     
  13. Toucan

    Toucan New Member

    Guys, would this help if he ran it from his network to help diagnose the problem ?

    Dig thednsrecord@192.168.0.yourip

    Wouldnt that force the query of the local server to see if it's behaving correct and rule in/out port forward problem?
     

Share This Page